What Are Core Web Vitals?

We can all recall the frustration of a page that takes an age to load, freezes when you tap a button, or shoves the content sideways just as you go to click. These are not vague annoyances — they are measurable, and Google has chosen specific numbers to capture them. Core Web Vitals are that set of numbers: an attempt to score how a page actually feels to use, drawn from real visitors rather than a lab. This guide explains the three metrics, the thresholds that matter, and the steps that move the needle.

What it is

Core Web Vitals are a set of three metrics defined by Google that measure the real-world experience of using a web page: how quickly it loads, how responsive it is to interaction, and how visually stable it is as it loads. They are the headline part of Google's broader page experience signals, and they are deliberately user-centred — each one tries to capture a moment of friction a real person would notice.

The three vitals are Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. Google reviews and occasionally updates this set; Interaction to Next Paint, for instance, replaced an earlier responsiveness metric. Crucially, they are measured on real users — your actual visitors, on their actual phones and connections — not on a perfect test machine. Core Web Vitals sit within the technical side of search engine optimisation, the part concerned with how well a site is built rather than what it says.

The three metrics explained

Each vital targets a different kind of frustration, and each has a clear good, needs improvement and poor band.

Largest Contentful Paint (LCP) — loading

LCP measures loading performance by timing how long it takes for the largest visible element — usually a hero image, video or big block of text — to appear on screen. It answers the question, "How long before this page looks usefully loaded?"

• Good: 2.5 seconds or less
• Needs improvement: up to 4 seconds
• Poor: over 4 seconds

A slow LCP usually points to heavy images, sluggish servers, or scripts and stylesheets blocking the page from rendering.

Interaction to Next Paint (INP) — responsiveness

INP measures responsiveness by timing how quickly the page reacts when a user interacts — tapping a button, opening a menu, ticking a box. It looks across all the interactions during a visit and reports a representative figure, answering, "When I do something, does the page respond promptly?"

• Good: 200 milliseconds or less
• Needs improvement: up to 500 milliseconds
• Poor: over 500 milliseconds

Poor INP is typically caused by heavy JavaScript hogging the browser, so that taps feel laggy or dead for a moment.

Cumulative Layout Shift (CLS) — visual stability

CLS measures visual stability by scoring how much the content jumps around unexpectedly while the page loads. We have all gone to tap a link only for an advert to load above it and push everything down, so we tap the wrong thing. CLS quantifies exactly that.

• Good: 0.1 or less
• Needs improvement: up to 0.25
• Poor: over 0.25

Unlike the others, CLS is a unitless score rather than a time. It is usually caused by images and ads without reserved space, or fonts and content that load late and reflow the layout.

Why Core Web Vitals matter

There are two reasons to care, and the lesser-known one is arguably the more important.

First, ranking. Core Web Vitals are part of Google's page experience signals, which feed into how pages are ranked. But the influence is modest and best understood as a tie-breaker: when two pages are similarly relevant and authoritative, the one offering the better experience may edge ahead. They will never push thin or irrelevant content above genuinely useful pages, so treat them as a polish on good work, not a substitute for it.

Second, and more powerfully, users. A fast, responsive, stable page is simply nicer to use, and the data is consistent: slow and janky pages drive people away. Visitors abandon pages that take too long to load, and an unstable layout erodes trust. Improving your vitals therefore improves real outcomes — people stay longer, read more and convert more — which shows up in metrics like bounce rate and the proportion of visitors who go on to act. In other words, the rankings benefit is the bonus; the experience benefit is the point.

Optimise Core Web Vitals for your visitors first and Google second. A page that feels instant and steady serves the human, and the small search advantage takes care of itself.

Lab data versus field data

When you start measuring, you will meet two kinds of data, and confusing them causes needless worry.

• Lab data comes from testing a page in a simulated, controlled environment. It is repeatable and ideal for debugging, because you can change one thing and see the effect. Tools like Lighthouse provide it.
• Field data, also called real-user monitoring, comes from actual visitors on real devices and networks. This is messier but truer — and it is what Google uses to judge your Core Web Vitals, reported at the 75th percentile so most of your users are accounted for.

A page can score beautifully in the lab yet stumble in the field, where real users have older phones and patchy connections. So check both: field data tells you whether you have a problem, and lab data helps you fix it.

How to measure them

Several free Google tools surface these numbers:

• PageSpeed Insights combines lab and field data for any single URL, with specific recommendations.
• Google Search Console has a Core Web Vitals report covering your whole site, grouped by issue — the best place to spot patterns.
• Lighthouse, built into Chrome's developer tools, runs a lab audit on demand.
• The Chrome User Experience Report is the underlying source of Google's field data.

Start with Search Console to see which pages are flagged, then dig into individual URLs with PageSpeed Insights.

How to improve your scores

The fixes map neatly onto the three metrics. A practical starting list:

1. For LCP (loading): compress and correctly size images, use modern formats, lazy-load anything below the fold, improve server response times, and remove render-blocking scripts and styles.
2. For INP (responsiveness): trim and defer heavy JavaScript, break long tasks into smaller chunks, and remove unnecessary third-party scripts that tie up the browser.
3. For CLS (stability): always specify width and height (or reserved space) for images, videos and ads, avoid inserting content above existing content, and load fonts in a way that does not cause text to reflow.

Underpinning all three is a lighter, leaner site. Much of this overlaps with general performance and secure delivery — serving pages efficiently over HTTPS and keeping page weight down. Many website platforms and plugins handle a good deal of it automatically, but the principles are worth understanding so you know what to ask for.

The bottom line

Core Web Vitals are Google's three metrics for real-world page experience: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness, and Cumulative Layout Shift for visual stability. Aim for LCP at or under 2.5 seconds, INP at or under 200 milliseconds, and CLS at or under 0.1, measured on your actual visitors. They are a real but modest ranking signal, best treated as a tie-breaker rather than a shortcut — the stronger reason to chase good scores is that a fast, responsive, stable page keeps people engaged and converting. Measure with Google's free tools, fix images and heavy scripts, reserve space so nothing jumps, and you will improve both your search standing and, more importantly, the experience of everyone who visits.