Core Web Vitals Explained: What It Really Measures

Core Web Vitals is one of those terms that gets thrown around in SEO reports without anyone quite explaining what it means. Clients see it flagged in a Google Search Console email or a website audit and assume it's something urgent and technical that needs a developer fixing it immediately. Mostly, it isn't. It's just Google's way of measuring how a real visitor experiences your site once they land on it, and understanding it properly takes about five minutes.

What the three scores actually measure

Core Web Vitals is made up of three separate metrics with some funky names!

Largest Contentful Paint looks at how long it takes for the main bit of content on a page, usually a hero image or a headline, to actually show up on screen.

Interaction to Next Paint measures how quickly the page responds once someone clicks a button or taps a menu, rather than leaving them tapping away at something that isn't doing anything yet.

Cumulative Layout Shift tracks how much the page jumps around while it's loading, which is the reason you sometimes go to tap a link and end up hitting an ad instead, because something shifted underneath your thumb at the last second.

Each one has a rough bar for "good": around two and a half seconds for the main content to load, about 200 milliseconds for the page to respond to an interaction, and barely any visible movement once the page settles. Anything comfortably inside those numbers is fine.

Where the score comes from

This is the part most explanations skip. Your Core Web Vitals score isn't generated by running your site through a speed test once and getting a grade back. Google builds it from real visits to your actual site over the past few weeks, and it scores you on the slower end of those visits rather than the average. So if a decent chunk of your visitors are on an older phone or a weak signal, their slower experience drags your score down even though your own test, run on a fast laptop with fibre broadband, comes back green. It isn't a flaw in the system. It's just the system doing exactly what it's meant to which is measuring the people who are actually struggling rather than the people who aren't.

What it does to your Google ranking

Core Web Vitals is a ranking signal, Google has confirmed that much, but it's quite a small one, and it sits well behind relevance (relevance is key these days). Google's own guidance is blunt about it: if your site is faster than a competitor's but theirs answers the search better, theirs still outranks yours. Moving a genuinely slow, clunky site up to "good" can help. Squeezing an already decent site from good to slightly better almost certainly won't move anything, so it isn't worth losing sleep over - there's probably something better you can spend your time on (hint: relevancy...)

What it means for AI search

Where this has started to matter more lately is AI search. Tools like ChatGPT, AI Overviews and Perplexity fetch and read pages in real time to work out what to cite, and a fast, cleanly built page is easier for them to grab and quote than a slow one loaded with heavy scripts. A page that takes too long to load, or leans too hard on JavaScript to render its content, risks being skipped over entirely rather than just ranked lower. 

What to do about it

For most small business sites, this isn't something that needs monitoring weekly or panicking over every time a report flags it amber. A check twice a year, alongside a general look at how the site's performing, catches the genuine problems without turning it into a part-time job.