kaayaessentials.com website review

About 287 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

9 files are served with short cache lifetimes, so returning visitors download them again (332 KiB).

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

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

8 third-party services load with your homepage (shiprocket.in, Google Tag Manager and Facebook and others), adding 1,020 KiB and 1.4 s of main-thread time.

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

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

shiprocket.in costs a phone 512 ms of main-thread work and 76 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.

Google Tag Manager costs a phone 413 ms of main-thread work and 312 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 costs a phone 310 ms of main-thread work and 228 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.

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

The page has 1,743 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Shopify costs a phone 104 ms of main-thread work and 381 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.

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

23 KiB could be saved by minifying JavaScript.

24 images could be 168 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.6 MB in 349 requests on a phone: images 2.2 MB (90), other files 1.2 MB (201) and scripts 1,011 KiB (47). Under 2 MB keeps phones on slow connections fast.

19 images further down the page (570 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

2 dropdowns have no label.

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

<svg> elements with an img or image role must have alternative text: 8 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

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

Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 26 characters: “Kaaya Essentials Pvt. Ltd.”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 3 <h1> headlines (“”, “Cholestro Xpert™: Ayurvedic Medicine to Lower Cho…” and “100% Pure Himalayan Shilajit Resin - 20 Gms | Boo…”). One clear main headline is easier for people and search engines.

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

The homepage links to 60 pages on kaayaessentials.com and 12 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://kaayaessentials.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://kaayaessentials.com/products/plant-based-collagen-builder declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://kaayaessentials.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://kaayaessentials.com/products/plant-based-collagen-builder all use the title “Kaaya Essentials Pvt. Ltd.”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://kaayaessentials.com/collections/himalayan-shilajit, https://kaayaessentials.com/collections/combos, https://kaayaessentials.com/customer_authentication/redirect, https://kaayaessentials.com/products/plant-based-collagen-builder, https://kaayaessentials.com/policies/privacy-policy and https://kaayaessentials.com/policies/terms-of-service and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://kaayaessentials.com/products/pure-himalayan-shilajit-resin and https://kaayaessentials.com/products/pure-himalayan-shilajit-resin-boosts-performance-power-stamina-endurance-strength-and-build-muscle-mass use the same meta description. A description written for each page earns more clicks.

https://kaayaessentials.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

https://kaayaessentials.com/customer_authentication/redirect took over 3 s to send its HTML from our server.

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

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

4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin”.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

The homepage carries about 1,163 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

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

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.

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