Google has been hinting for years that user experience matters for rankings. In 2021, it stopped hinting. Core Web Vitals — three specific measurements of how a page feels to a real visitor — became an official ranking signal. They measure loading, interactivity, and visual stability: in plain terms, how fast the page shows up, how quickly it responds when you touch it, and whether it jumps around while you're trying to read.
The annoying part is that most site owners have never heard of them, let alone measured theirs. This guide fixes that. You'll learn what each metric means, what "good" looks like, how to check your scores, and what actually moves the needle when you need to fix them.
Search engines have a simple motivation: keep searchers happy so they keep searching. A page that answers the query but takes eight seconds to load, freezes when you tap a button, and shifts its layout mid-scroll doesn't make anyone happy — even if the content is great.
The vitals made experience concrete: three standardized numbers collected from real Chrome users via the Chrome User Experience Report. That last point matters — your page might load in 1.2 seconds on your fiber connection and 6 seconds on a visitor's phone. Google scores you on the visitor's experience, not yours.
LCP measures how long it takes for the largest visible element on the page to render — usually the hero image, a big headline block, or a video thumbnail. It's Google's way of asking: "when does the user feel like the page has actually arrived?"
What "good" looks like: under 2.5 seconds. Between 2.5 and 4 seconds needs improvement. Over 4 seconds is poor.
LCP is the metric most sites fail, and the culprits are almost always the same: slow server response (better hosting, caching, and a CDN are the fixes — see our article on why page speed matters for SEO); oversized hero images (compress, use modern formats, size for the screen); render-blocking scripts and styles (defer non-critical scripts, inline critical CSS); and client-side rendering (pages built entirely in JavaScript show a blank screen until the framework boots — server-render critical pages).
The fastest way to find your worst offender is to run your key pages through a PageSpeed Insights checker — it breaks down your LCP and tells you exactly which element is the "largest contentful" one, so you're not guessing.
INP replaced the older First Input Delay metric. Where FID only measured the first interaction, INP measures responsiveness across the whole visit — every tap, click, and keystroke — and reports the worst one. It's Google asking: "does this page feel alive, or does it feel stuck?"
What "good" looks like: under 200 milliseconds. Between 200 and 500ms needs improvement. Over 500ms is poor.
Poor INP almost always comes from JavaScript hogging the browser's main thread — the browser can't respond to your tap while it's busy executing a giant script bundle. The fixes: split your JavaScript and remove unused libraries, defer non-critical scripts (analytics, chat widgets, social embeds) until after the page is interactive, debounce long-running event handlers, and audit third-party scripts ruthlessly — each one competes for the main thread and should justify its existence.
INP is harder to diagnose than LCP because it depends on real interactions, not just loading. A page speed checker gives you the lab-side picture, but pay attention to your field data in Search Console's Core Web Vitals report — that's what Google actually grades.
CLS is the metric for everyone's least favorite experience: you're about to tap a link and the page jumps, so you tap an ad instead. It measures how much visible content shifts around unexpectedly during loading.
What "good" looks like: a CLS score below 0.1. Between 0.1 and 0.25 needs improvement. Above 0.25 is poor.
Unlike LCP and INP, CLS has nothing to do with speed — it's about reserving space. The fixes are almost embarrassingly simple: give images and embeds explicit dimensions (width/height attributes or CSS aspect-ratio) so the browser reserves space before they load; set minimum heights on ad containers instead of letting them pop open from zero; never inject banners or notices above existing content mid-read; and preload critical web fonts so text doesn't reflow when they arrive late.
CLS is often the easiest vital to fix — most sites can get it under 0.1 in an afternoon. It's also the one that most directly affects how professional your site feels.
You have three layers of data, and you should use all of them:
1. Lab data (instant). Run any URL through a PageSpeed Insights checker for an immediate breakdown of all three vitals with prioritized recommendations.
2. Field data (real users). Search Console's Core Web Vitals report shows how your pages perform for actual visitors — this is the data Google grades, so lab scores are diagnostics; field data is the verdict.
One more thing to check: page weight. Bloated pages fail all three vitals more often, so run your worst pages through a page size checker — a 5MB page will almost never have good vitals, no matter how well it's built.
If your scores are red across the board, fix in this order: CLS first — usually a few hours of work (image dimensions, ad container heights) with permanent results. LCP second — compress the hero image, fix server response time, defer render-blocking scripts; this is where most ranking-relevant gains live. INP third — the most technical (JavaScript optimization), but it affects engaged visitors, so it pays off in conversions too.
And be honest about priorities: a page ranking #30 because its content is thin won't be saved by perfect vitals. Core Web Vitals are a tiebreaker and a multiplier, not a substitute for good content.
Core Web Vitals turned "user experience" from a vague aspiration into three concrete numbers: LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1. They're measured on real users, they affect rankings, and — just as importantly — they describe exactly the frustrations that drive your visitors away.
Start by measuring. Check your key pages, fix layout shift first, then attack loading and interactivity. Your visitors will feel the difference immediately, and Google will notice too.
Check your scores now with our free PageSpeed Insights checker — see your LCP, INP, and CLS with specific recommendations for every page.
Yes. They're part of Google's page experience signals. They're not the dominant factor — content relevance and links matter more — but they act as a tiebreaker between otherwise similar pages, and poor vitals can hold back an otherwise strong page.
Lab data is measured in a simulated environment (a single test run under controlled conditions). Field data comes from real Chrome users visiting your site over the past 28 days. Google uses field data for ranking; lab data is for diagnosis. A page can score well in the lab and poorly in the field if real users are on slower devices.
Check lab scores whenever you publish or redesign a page. Monitor field data monthly in Search Console — it updates on a rolling 28-day window, so changes take weeks to fully reflect. After a major fix, give it a full month before judging the result.
Absolutely — most failures come from fixable issues: unoptimized images, too many plugins loading scripts, no caching. The usual recipe is a caching plugin, image optimization, and removing or deferring unnecessary scripts. Many WordPress sites go from red to green with just those three changes.
Yes. The vitals are measured separately for mobile and desktop, and Google considers the relevant one for each search. Since most searches happen on mobile, your mobile scores matter more — but don't ignore desktop, especially for B2B or SaaS sites with desktop-heavy audiences.
