Core Web Vitals, Explained (and How to Actually Pass Them)

"Core Web Vitals" is one of those phrases that sounds like it needs an engineer to explain. It doesn't. It's just Google's way of measuring three things every visitor already feels: does the page load quickly, does it respond when I tap, and does it stay still while I read it, or does the button jump away right as I go to click it?

Google uses these three scores as a ranking signal, and, more importantly. They're a direct measure of whether your site frustrates people. Here's what each one means and the practical fixes that actually move them, no code required.

The three vitals, in plain English

1. LCP, Largest Contentful Paint (loading)

LCP measures how long it takes for the biggest thing on screen, usually your main image or headline, to appear. It answers: how fast does this page feel like it loaded?

The target: under 2.5 seconds. Between 2.5 and 4 seconds needs work; over 4 seconds is poor.

2. INP, Interaction to Next Paint (responsiveness)

INP measures how quickly the page reacts when someone interacts with it, a tap, a click, a keypress. A page can look loaded but freeze for a beat when you tap a menu; that lag is what INP catches. (It replaced the older "First Input Delay" metric in 2024.)

The target: under 200 milliseconds. 200 to 500ms needs work; over 500ms is poor.

3. CLS, Cumulative Layout Shift (visual stability)

CLS measures how much the page jumps around as it loads. You've felt this: you go to tap a link, an image or ad loads above it, everything shifts down, and you tap the wrong thing. That's layout shift.

The target: under 0.1. 0.1 to 0.25 needs work; over 0.25 is poor.

Why do Core Web Vitals matter, and how much?

Two reasons. First, Core Web Vitals are part of Google's "page experience" signals, so genuinely poor scores can hold you back, especially when you're competing with a site that's otherwise similar. Second, and bigger: these metrics are the experience. A slow, jumpy, laggy page loses customers before it ever loses rankings. Improving them usually lifts conversions as much as rankings.

Don't over-index on chasing a perfect score, though. Vitals are one factor among many. If your page isn't even indexed or has no clear title, fix that first. We put the whole checklist in order in how to do an SEO audit.

Lab data vs field data (why your score keeps changing)

One confusing thing: you'll see two kinds of numbers. Lab data is a simulated test in a controlled environment, consistent, repeatable, good for debugging. Field data is what real visitors on real devices and connections actually experienced over the past month. Google uses the field data for ranking. So a brand-new or low-traffic page may only show a "lab estimate" until it has enough real visits to report field data. That's normal, not a bug.

How do you actually pass each one?

You don't need to touch code to know what to ask for. Here's what fixes each metric:

To improve LCP (loading):

• Compress and correctly size your images, an oversized hero image is the most common cause of a slow LCP.
• Use modern image formats (like WebP) and lazy-load images below the fold.
• Cut down on heavy themes, plugins and scripts that block the page from rendering.
• Use good hosting or a CDN so files arrive quickly.

To improve INP (responsiveness):

• Reduce heavy JavaScript, the more scripts run on a tap, the longer the page freezes.
• Trim third-party scripts (chat widgets, trackers, pop-up tools); each one competes for the browser's attention.
• On most small-business sites, "install fewer plugins and tools" is 80% of the fix.

To improve CLS (stability):

• Give images and videos fixed width and height so the browser reserves their space before they load.
• Avoid inserting banners or ads that push content down after the page appears.
• Load fonts carefully so text don't visibly re-flow.

Notice a theme: images and too many scripts are behind most Core Web Vitals problems. Fix those two and you've usually fixed the page.

How do you check your own scores?

The free, official tool is Google's PageSpeed Insights, paste any URL and it shows all three vitals plus specific suggestions. Our free SEO scorecard also folds a speed check into the overall audit, so you see your Core Web Vitals alongside the titles, structure and technical issues that matter just as much, all explained in plain English, with what to fix first. Speed is important, but it's one leg of the stool; fix it as part of the whole picture, which we walk through in how to improve your Google ranking.

Frequently asked questions

Do Core Web Vitals actually affect rankings?

They're a genuine ranking signal but a modest one, and they matter most as a tiebreaker between pages of similar relevance. Content and relevance still decide the bulk of it, so a fast page about the wrong thing won't outrank a slower page that answers the question.

What's a good Core Web Vitals score?

Google's thresholds mark each metric as good, needs improvement, or poor, and the target is landing in "good" for the majority of real visits. Chasing a flawless lab score is usually wasted effort, because field data from real users is what counts.

Why does my score change every time I test it?

Because lab tests and field data measure different things. A lab test is one simulated load on one connection, while field data is aggregated from real visits across many devices and networks. Treat the lab number as a debugging aid and the field data as the truth.

What's the single most common cause of failing vitals?

Oversized images, by a wide margin, especially on small business sites where photos go up straight from a phone camera. Resizing and compressing them fixes more failures than any other single change.