All articles

Performance

Core Web Vitals: what they are, and why a slow site is losing you customers

Contents · 5 sections

"Core Web Vitals" sounds like a diagnostic term built to be ignored, which is a shame, because what it actually measures is simple: does your website feel fast and stable to an actual visitor. Google factors it into rankings, but the real cost of getting it wrong isn't a ranking penalty — it's the customer who left before your page finished loading and never came back.

The three numbers that matter

Largest Contentful Paint (LCP) — how fast the page feels like it's loaded

LCP measures how long it takes for the largest visible element on the page — usually a hero image or heading — to render. Google's threshold for "good" is 2.5 seconds or under. Beyond that, visitors perceive the site as slow, even if the rest of the page is technically usable. The usual culprits: unoptimised images, no caching, and a hosting setup that was never tuned for speed.

Cumulative Layout Shift (CLS) — how stable the page is while it loads

CLS measures unexpected movement — text jumping down because an image loaded late, a button shifting just as you were about to tap it. Google's threshold is 0.1 or under. High CLS doesn't just annoy visitors; it causes genuine mis-clicks, which is exactly the kind of thing that erodes trust in a business fast.

Interaction to Next Paint (INP) — how responsive the page feels

INP measures the delay between a visitor doing something — tapping a button, opening a menu — and the page visibly responding. Google's threshold is 200 milliseconds or under. Bloated JavaScript is the usual cause: too many scripts competing for the browser's attention at once.

Why this affects revenue, not just rankings

Core Web Vitals is a ranking signal, so slow sites do lose some search visibility. But the bigger, harder-to-see cost is abandonment: visitors who never see your offer because they left during the load. That's not a ranking problem — it's a lost enquiry that never shows up in any report, because it never became a session worth measuring.

The usual fixes

  • Image optimisation — correctly sized, modern formats (WebP), and lazy-loaded below the fold.
  • Caching — so returning visitors, and ideally first-time ones too, aren't rebuilding the page from scratch.
  • Reserving space for dynamic content — images and ads should have their dimensions set in advance, so the page doesn't jump when they load.
  • Trimming JavaScript — removing or deferring scripts that aren't needed for the initial view.
  • Hosting tuned for the job — cheap, generic hosting is a common, invisible bottleneck.

How to check your own scores

Google's free PageSpeed Insights tool (external link) combines available real-user Core Web Vitals data with a Lighthouse lab test for diagnosis. The lab score is not a measurement of all three field metrics, and some sites do not have enough field data. Check your homepage and your most important commercial page — they can behave differently.

For treatment pages, image galleries and online booking tools, see our web performance guide for UK dental practices. It explains which parts of the patient journey to test and how to handle third-party integrations.

Performance is one part of a bigger picture

Speed is also one of the checks in a technical SEO audit. That review looks at crawlability, indexation, internal links and mobile rendering as well, so a performance score is not mistaken for the whole search picture.

A fast site that's insecure, invisible to AI search, or fails basic accessibility checks still has real problems elsewhere. That's why performance is one of five pillars in the free website review, alongside AI readiness, technical SEO, accessibility and security — reviewed by hand, with a plain-English report within 24 hours. If speed turns out to be the priority, that's exactly what Performance Optimisation is built to fix, with real before-and-after numbers, not just a promise.

Further reading

More on Performance