Website review, no card needed

kaya.in logo

kaya.in website review

Visit site (opens in a new tab)Reviewed 28 October 202642 issues · 82 checks

This review found 42 issues worth fixing on kaya.in, 19 of them high impact, across 82 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.6 s2.6 sMay 9Oct 242.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.4 s
May 16, 20263.4 s
May 23, 20263.4 s
May 30, 20263.4 s
Jun 6, 20263.4 s
Jun 13, 20263.5 s
Jun 20, 20263.5 s
Jun 27, 20263.5 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.4 s
Jul 25, 20263.3 s
Aug 1, 20263.3 s
Aug 8, 20263.3 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.2 s
Sep 12, 20263.0 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.7 s
Oct 24, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
249 ms213 msMay 9Oct 24226 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026218 ms
May 16, 2026217 ms
May 23, 2026222 ms
May 30, 2026231 ms
Jun 6, 2026235 ms
Jun 13, 2026233 ms
Jun 20, 2026229 ms
Jun 27, 2026223 ms
Jul 4, 2026221 ms
Jul 11, 2026220 ms
Jul 18, 2026227 ms
Jul 25, 2026229 ms
Aug 1, 2026236 ms
Aug 8, 2026242 ms
Aug 15, 2026245 ms
Aug 22, 2026244 ms
Aug 29, 2026240 ms
Sep 5, 2026240 ms
Sep 12, 2026239 ms
Sep 19, 2026241 ms
Sep 26, 2026242 ms
Oct 3, 2026238 ms
Oct 10, 2026230 ms
Oct 17, 2026226 ms
Oct 24, 2026226 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of kaya.in (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kaya.in at 1.2 s1.2 s
  2. kaya.in at 2.5 s2.5 s
  3. kaya.in at 3.7 s3.7 s
  4. kaya.in at 4.9 s4.9 s
  5. kaya.in at 6.2 s6.2 s
  6. kaya.in at 7.4 s7.4 s
  7. kaya.in at 8.6 s8.6 s
  8. kaya.in at 9.9 s9.9 s

Speed

13 to fix24
  • Render-blocking requests

    10.3 s

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 10.3 s.

  • Improve image delivery

    3.4 s · 1.3 MB

    19 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.4 s faster on a phone.

  • Google Tag Manager adds 1.8 s

    1.8 s

    Google Tag Manager costs a phone 1.8 s of main-thread work and 1.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 24

    24/100

    Your mobile performance score is 24 (desktop: 26). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 9.0 s

    A phone's processor spends 9.0 s on main-thread work while loading, 4.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, botframework.com and Facebook and others), adding 2.6 MB and 3.3 s of main-thread time.

  • Reduce unused JavaScript

    600 ms · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Use efficient cache lifetimes

    1.2 MB

    18 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

  • Reduce unused CSS

    900 ms · 183 KiB

    About 183 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 896 ms. During a long task the page ignores taps.

  • botframework.com adds 723 ms

    723 ms

    botframework.com costs a phone 723 ms of main-thread work and 945 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Facebook adds 412 ms

    412 ms

    Facebook costs a phone 412 ms of main-thread work and 297 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Font display

    300 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

  • Legacy JavaScript

    150 ms · 18 KiB

    Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 15 ms

    15 ms

    Your server sent the HTML in 15 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix33
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • First Contentful Paint: 9.9 s

    9.9 s

    The first text or image appears after 9.9 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 20.6 s

    20.6 s

    Your largest element takes 20.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 30.1 s

    30.1 s

    The page becomes fully interactive after 30.1 s. Good is under 3.8 s.

  • Total Blocking Time: 3.5 s

    3.5 s

    Scripts block taps and scrolling for 3.5 s in total while the page loads. Good is under 200 ms.

  • Speed Index: 12.4 s

    12.4 s

    Visually, the page fills in at 12.4 s (Speed Index). Good is under 3.4 s.

  • Real-user LCP: 2.9 s

    2.9 s

    Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.18

    0.18

    For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.

  • Real-user FCP: 2.4 s

    2.4 s

    Real visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.2 s

    1.2 s

    Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

  • 8 images without width and height

    8 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +4%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 218 ms to 226 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user INP: 163 ms

    163 ms

    Real visitors wait 163 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Largest content (LCP) got 19% faster for real visitors

    -19%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.4 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.086

    0.086

    The layout barely moves while loading (CLS 0.086, good is under 0.1).

Images and page weight

2 to fix50
  • Page weight: 6.6 MB in 144 requests

    6.6 MB

    Your homepage downloads 6.6 MB in 144 requests on a phone: scripts 3.7 MB (31), images 2.1 MB (48) and fonts 488 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 8 images far larger than shown

    832 KiB

    8 images are downloaded at several times the size a phone draws them, for example Category_Banners_-_Mobile-04.jpg at 1,562 px wide, shown at 190 px. Resized copies would save about 832 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (103 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.9 g of CO₂ per visit

    1.86 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.86 g of CO₂e: 223.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

8 to fixGoogle 7589
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Orphan list items

    Some list items are not inside a list.

  • 4 images without alt text

    4 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (4 elements)

    All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 16 form fields without a label

    16 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 11 links without text

    11 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8588
  • Title is long (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “Kaya Clinic: Best Beauty Clinic for Skin, Hair & Weight Loss Treatments”.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 9 links crawlers can't follow

    9 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 134 internal links, 4 external

    The homepage links to 134 pages on kaya.in and 4 external pages.

6 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Discover Kaya Clinic, India’s best skin and beauty clinic for expert skin, hair, and weight loss treatments. Get radian…”.

  • One H1 headline

    Your main headline reads: “Kaya skin & hair care solutions”.

  • Canonical URL set

    The canonical URL is https://www.kaya.in/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.kaya.in/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.kaya.in/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,214 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 91 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

3 to fixGoogle 9271
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97061101&Ver=2&mid=7801ea12-2817-4cf6-b6e7-b8a4f7b8017d&bo=1&sid=6954af70d29711f19b2df9158b79b313&vid=6954bf70d29711f197cfe9a8c8bc4783&vids=1&msclkid=N&pi=918639831&lg.

  • 7 small tap targets

    7 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'fn')”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 803 words of copy

    The homepage carries about 803 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book Now”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Book Now”, “Contact Us” and “Track Order”.

  • 15 short forms

    15 short forms (7 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 email links.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 34 other companies contacted

    Loading the homepage contacts 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at kaya.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Magento
Analytics
Google Analytics | Google Tag Manager
Hosting
Fastly

Company

Founded
2003
Headquarters
Mumbai

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on kaya.in, including 24 speed issues, 3 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25