ozo.design website review

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

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

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

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

azurefd.net costs a phone 77 ms of main-thread work and 321 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 (Clarity, azurefd.net and Shopify and others), adding 499 KiB and 248 ms of main-thread time.

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

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

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

About 43 KiB of CSS is downloaded but never applied on this page.

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

14 KiB JavaScript is shipped twice across bundles.

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 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “slider image 1621243260e1af0c20-0”.

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

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

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

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 3.4 MB in 384 requests on a phone: images 1.5 MB (74), other files 1.0 MB (202) and scripts 613 KiB (77). Under 2 MB keeps phones on slow connections fast.

Labradorite-HematiteCubeBraceletII_4-6mm_-solo-productshot_9 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

4 images are downloaded at several times the size a phone draws them, for example B2.jpg at 600 px wide, shown at 163 px. Resized copies would save about 87 KiB.

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

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

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 10 characters: “ozo.design”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your <h1> is empty.

The homepage links to 284 pages on ozo.design and 1 external page.

There is no https://ozo.design/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.

https://ozo.design/collections/newest-collection, https://ozo.design/collections/new-arrivals, https://ozo.design/collections/jade-collection, https://ozo.design/collections/keystone-collection, https://ozo.design/collections/earth-browns-beige and https://ozo.design/collections/warm-reds-orange and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://ozo.design/collections/newest-collection, https://ozo.design/collections/new-arrivals, https://ozo.design/collections/jade-collection, https://ozo.design/collections/keystone-collection, https://ozo.design/collections/earth-browns-beige and https://ozo.design/collections/warm-reds-orange 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 128 found) and read each the way a search engine does.

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

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

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

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

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 1,506 words of visible text.

Before a visitor clicks anything, the page loads 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 10 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.