zooki.com website review

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

8 third-party services load with your homepage (Yotpo, iovation and Klaviyo and others), adding 930 KiB and 927 ms of main-thread time.

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

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

Yotpo costs a phone 464 ms of main-thread work and 498 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 338 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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

Polyfills for old browsers add 48 KiB JavaScript that modern phones do not need.

23 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

Your homepage downloads 3.3 MB in 312 requests on a phone: other files 1.1 MB (185), scripts 1.0 MB (78) and images 847 KiB (25). Under 2 MB keeps phones on slow connections fast.

7 images further down the page (246 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 0.94 g of CO₂e: 112.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

There are 4 <h1> headlines (“Zooki”, “The home of innovative health and wellness” and “"By far the best turmeric supplement I've used. Z…”). One clear main headline is easier for people and search engines.

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

The homepage links to 133 pages on zooki.com and 10 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://zooki.com/en-us/collections/powders and https://zooki.com/en-us/collections/accessories have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://zooki.com/products/marine-collagen-liquid-5000mg, whose canonical is https://zooki.com/en-us/products/marine-collagen-liquid-5000mg. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://zooki.com/en-us/pages/become-a-stockist, https://zooki.com/en-us/collections/all, https://zooki.com/en-us/collections/liquid-sachets, https://zooki.com/en-us/collections/powders, https://zooki.com/en-us/collections/capsules and https://zooki.com/en-us/collections/accessories and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “initLoopBundle is not defined”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

The homepage carries about 663 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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