What is Core Web Vitals? In plain terms, it is Google's set of three measurements that score how a page feels to a real visitor: how quickly the main content appears, how fast the page reacts when someone taps or clicks, and how much the layout jumps around whilst it loads. The scores come from real users, they feed into rankings, and your customers feel them on every single visit. Here is what each metric means, what counts as a pass, and how to lift a failing score.
What is Core Web Vitals measuring?
Core Web Vitals boils the fuzzy idea of page speed down to three numbers, each capturing a different moment of a visit.
- LCP (Largest Contentful Paint) measures loading. It is the time until the largest visible element, usually a hero image or headline, has rendered on screen. It answers the visitor's first question: is anything happening?
- INP (Interaction to Next Paint) measures responsiveness. It tracks how long the page takes to visibly react after a tap, click or keypress. A high INP is the "I tapped the menu and nothing happened" feeling.
- CLS (Cumulative Layout Shift) measures visual stability. It scores how much content moves around as the page loads. Bad CLS is the button that jumps just as you press it.
The thresholds are official and public: LCP of 2.5 seconds or under, INP of 200 milliseconds or under, and CLS of 0.1 or under. A page passes when it meets all three for most real visits.
That phrase "real visits" matters. The scores Google uses are field data, gathered from actual Chrome users over the previous 28 days, on real phones and real connections. A quick lab test on your office computer can look fine whilst customers on the train are having a very different experience.
What is Core Web Vitals worth for rankings?
The honest answer: it is a genuine ranking signal, but a modest one. Content and relevance still decide most results, and a fast page with a weak answer will not outrank a slower page with a better one. Where the metrics bite is at the margins, in competitive markets where the top contenders are all strong and speed becomes a tiebreaker.
The bigger commercial impact is on people, not algorithms. Visitors abandon pages that feel slow, and a sluggish, jumpy contact form or checkout costs enquiries that your analytics quietly records as bounces. Treat page speed as a conversion project with a ranking bonus, and the investment case makes itself: the same work that satisfies Google also stops paying customers giving up.
It also helps to know where the name comes from. Google groups these measurements under the wider banner of page experience, and Core Web Vitals is the measurable core of it: the part with published numbers rather than vague advice. That makes the answer to what is Core Web Vitals unusually practical by SEO standards. You rarely get told the pass mark for anything in search, but here Google states the thresholds openly and reports your scores back to you for free, which turns speed from a vague worry into a checklist: measure, compare, fix, then measure again.
How to check your scores
You do not need paid tools to answer what is Core Web Vitals doing on your own site. PageSpeed Insights is free: paste in a URL and it shows the real-user scores for that page alongside lab diagnostics that point at causes. For a whole-site view, Google Search Console has a dedicated Core Web Vitals report that groups every page into Good, Needs improvement or Poor. If you have not set that up yet, our beginner's guide to Google Search Console walks through it.
Plenty of owners only search what is Core Web Vitals after one of those Search Console warnings lands in their inbox, and that is a perfectly good prompt. When you check, look at mobile first: most local traffic is on phones, and phone hardware is far less forgiving than a desktop on office wi-fi.
How to fix a failing score
Once you can answer what is Core Web Vitals, the next question is how to pass it, and the good news is that most failures trace back to a shortlist of causes.
- Slow LCP usually means oversized images, cheap hosting or scripts that block rendering. Compress and correctly size images, upgrade the hosting, and defer whatever does not need to load first.
- Poor INP typically comes from heavy JavaScript: bloated page builders, stacked tracking tags and plugins all doing work on every interaction. Removing what you do not need often beats clever optimisation.
- Bad CLS is usually images without set dimensions, injected banners and late-loading fonts. Reserve space for everything that arrives late and the jumping stops.
These fixes sit squarely inside technical SEO, and sometimes the honest recommendation is that a lightweight rebuild costs less than endlessly patching a heavy theme. It is why our web design projects treat the thresholds as a launch requirement rather than an afterthought.
The question hiding behind what is Core Web Vitals is really "does my site feel fast to the people trying to pay me". Measure it, fix the biggest offender first, then re-check after the 28-day window refreshes. And if you want the wider picture of where site health fits into growing organic traffic, start with our plain-English guide to SEO.
Failing and not sure why? We run Core Web Vitals diagnostics as part of every technical audit, with fixes ranked by impact. Ask us for a look, it is a quick job to diagnose. The wider technical SEO checklist covers the rest of the checks worth running alongside speed.
