zenbodi.com website review

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

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

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

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

ContentSquare costs a phone 260 ms of main-thread work and 185 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.

5 third-party services load with your homepage (ContentSquare, Shopify and sealsubscriptions.com and others), adding 507 KiB and 302 ms of main-thread time.

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

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

26 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.

Your largest element takes 5.2 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 5.2 s. Good is under 3.8 s.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 116 ms to 120 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 1.3 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.5 MB in 160 requests on a phone: media 5.5 MB (1), images 1.6 MB (24) and other files 736 KiB (86). Under 2 MB keeps phones on slow connections fast.

10 images are downloaded at several times the size a phone draws them, for example zenhome-home-v2-images-family-kids-cafe.jpg at 1,200 px wide, shown at 167 px. Resized copies would save about 717 KiB.

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

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

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Elements with visible text labels do not have matching accessible names. (4 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 17 characters: “Zenbodi | Zenbodi”. 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.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

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

The homepage links to 29 pages on zenbodi.com and 2 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.

There is no https://zenbodi.com/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.

Your homepage links to https://zenbodi.com/pages/accessibility and https://zenbodi.com/pages/do-not-sell, which answer with an error. Visitors hit a dead end and search engines drop them.

https://zenbodi.com/pages/kids-cafe-v3 and https://zenbodi.com/pages/kids-cafe all use the title “Kids Cafe | Zenbodi”, 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://zenbodi.com/pages/contact has no meta description, so Google writes the search snippet from whatever text it finds.

https://zenbodi.com/pages/kids-cafe-v3 and https://zenbodi.com/pages/kids-cafe use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://zenbodi.com/pages/about, whose canonical is https://zenbodi.com/pages/about-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://zenbodi.com/products/plant-based-vegan-protein-vanilla, https://zenbodi.com/products/zenbodi-creatine and https://zenbodi.com/pages/shop have no <h1> headline, so visitors and search engines get no clear main topic.

https://zenbodi.com/pages/science has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://zenbodi.com/pages/kids-cafe-v3 took over 3 s to send its HTML from our server.

We fetched 14 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

The homepage carries about 686 words of visible text.

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