ocoza.co.uk website review

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

About 933 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.

amaicdn.com costs a phone 1.4 s of main-thread work and 507 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google Tag Manager costs a phone 1.1 s of main-thread work and 1.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (amaicdn.com, Google Tag Manager and lr-in-prod.com and others), adding 2.6 MB and 2.8 s of main-thread time.

14 long tasks block the main thread while loading, the longest for 1.9 s. During a long task the page ignores taps.

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

Shopify costs a phone 55 ms of main-thread work and 312 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.

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

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

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

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

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

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

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

The first text or image appears after 2.6 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 4.4 MB in 358 requests on a phone: scripts 2.7 MB (137), other files 822 KiB (139) and images 741 KiB (40). Under 2 MB keeps phones on slow connections fast.

desktop_1a3f74a0-2093-412f-9c84-12aa279ce218.jpg 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).

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

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

2 images have no alt text, which hurts accessibility and image search.

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.

Your canonical URL points to coza-home-eu.myshopify.com, not ocoza.co.uk, so Google may credit that host instead.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 120 pages on ocoza.co.uk and 4 external pages.

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

1 error was logged to the browser console while the page loaded, for example “[Weglot] Cannot load Weglot because the project has been deleted”.

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

The homepage carries about 362 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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 17 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 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.