mlperformance.co.uk website review

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

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

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

18 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

8 third-party services load with your homepage (Facebook, Clarity and Google CDN and others), adding 862 KiB and 574 ms of main-thread time.

Facebook costs a phone 286 ms of main-thread work and 225 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 155 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.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

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

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 17.0 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 18.3 s. Good is under 3.8 s.

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

The layout shifts by 0.248 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

Your homepage downloads 6.8 MB in 307 requests on a phone: images 4.2 MB (83), other files 1.4 MB (121) and scripts 667 KiB (59). Under 2 MB keeps phones on slow connections fast.

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

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

4 buttons have no accessible name, so screen readers announce just “button”.

4 dropdowns have no label.

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

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

3 tap targets are too small or too close together to hit reliably with a finger.

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

Your meta description is 194 characters; Google truncates after about 160, so the end of your pitch is cut.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

1 link has no real href, so search engines can't follow it.

Your <h1> is empty.

The homepage links to 372 pages on mlperformance.co.uk and 16 external pages.

Your homepage links to https://www.mlperformance.co.uk/collections/endless-brake, https://www.mlperformance.co.uk/collections/brembo, https://www.mlperformance.co.uk/collections/ferodo, https://www.mlperformance.co.uk/collections/pagid, https://www.mlperformance.co.uk/collections/eibach and https://www.mlperformance.co.uk/collections/h-r and 5 others, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.mlperformance.co.uk/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.mlperformance.co.uk/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.mlperformance.co.uk/collections/all and https://www.mlperformance.co.uk/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mlperformance.co.uk/collections/all, https://www.mlperformance.co.uk/customer_authentication/redirect, https://www.mlperformance.co.uk/collections/ebc-brakes and https://www.mlperformance.co.uk/collections/bilstein have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 403 (Forbidden)”).

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 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 link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 3,284 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).