oziva.com website review

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

6 third-party services load with your homepage (Shopify, Facebook and Google Tag Manager and others), adding 40.9 MB and 760 ms of main-thread time.

Shopify costs a phone 465 ms of main-thread work and 40.5 MB 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.

33 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

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

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

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

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 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner_Daily Fat Metabolism”.

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

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

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

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

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

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

Your homepage downloads 40.9 MB in 181 requests on a phone: media 35.9 MB (5), images 3.8 MB (83) and scripts 932 KiB (58). Under 2 MB keeps phones on slow connections fast.

Twinkle.gif weighs 518 KiB. On a phone connection a single image that size takes seconds.

10 images are downloaded at several times the size a phone draws them, for example Twinkle.gif at 500 px wide, shown at 24 px. Resized copies would save about 916 KiB.

2 images (767 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

Elements must only use permitted ARIA attributes: 29 elements on the page fail this check, rated serious by axe-core.

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

Some list items are not inside a list.

<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 2 elements on the page fail this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 image has no alt text, which hurts accessibility and image search.

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

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

Google's crawler is blocked from indexing this page.

Your title is 70 characters, so Google will cut it off around 60: “OZiva | No.1 Choice for Clean, Plant based Nutrition & Beauty Products”.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://www.oziva.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 13 pages on oziva.com and 6 external pages.

A phone browser shows 448 words, but the HTML your server sends has only 59. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

https://www.oziva.com/products/daily-fat-metabolism, https://www.oziva.com/collections/new-launches, https://www.oziva.com/pages/order-history, https://www.oziva.com/collections/build-your-own-box, https://www.oziva.com/pages/my-oziva-cash and https://www.oziva.com/pages/contact-us are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.oziva.com/products/daily-fat-metabolism has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.oziva.com/pages/order-history, https://www.oziva.com/pages/my-oziva-cash and https://www.oziva.com/pages/contact-us use the same meta description. A description written for each page earns more clicks.

https://www.oziva.com/products/daily-fat-metabolism, https://www.oziva.com/collections/new-launches, https://www.oziva.com/pages/order-history, https://www.oziva.com/collections/build-your-own-box, https://www.oziva.com/pages/my-oziva-cash and https://www.oziva.com/pages/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://pulse.prod.oziva.com/session/send' violates the following Content Security Policy directive: "co…”.

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

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

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.

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 shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

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.

The homepage carries about 448 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 5 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.