zanducare.com website review

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

Your mobile performance score is 80. Pages that score under 90 lose visitors before the first paint.

24 images could be 735 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

gokwik.co costs a phone 70 ms of main-thread work and 479 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.

8 third-party services load with your homepage (Google Tag Manager, gokwik.co and Shopify and others), adding 891 KiB and 305 ms of main-thread time.

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

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

About 121 KiB of JavaScript is downloaded but never used on this page.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.

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

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.

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.

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

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

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

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

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

Your homepage downloads 2.9 MB in 114 requests on a phone: images 1.8 MB (72), scripts 845 KiB (26) and HTML 134 KiB (1). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

[aria-*] attributes do not have valid values (1 element).

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

Your title is 69 characters, so Google will cut it off around 60: “ZanduCare - Shop Authentic Ayurvedic Products Online | Official Zandu”.

Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 225 pages on zanducare.com and 5 external pages.

https://zanducare.com/collections/double-the-josh-double-the-power is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://zanducare.com/collections/all-products has no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 46 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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 22 cookies, 1 of them by other companies (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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.