Core Web Vitals show up constantly in SEO and performance discussions, but they're often explained in technical language that skips the "why should I care" part. This post has Core Web Vitals explained in plain business terms: what each of the three metrics actually measures, what counts as "good" by Google's own published standards, and why they translate directly into both search rankings and real conversions.
What are Core Web Vitals?
Core Web Vitals are three specific metrics Google uses to measure real-world page experience: Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and Interaction to Next Paint (INP). They're not abstract lab scores — they're built from real visitor data collected across the web (the Chrome UX Report), which is part of why Google treats them as a meaningful ranking signal rather than just a nice-to-have diagnostic. For how much weight that signal really carries, see what Google has said about page speed and SEO.
What does LCP (Largest Contentful Paint) measure?
LCP measures how long it takes for the largest visible element on the screen — usually a hero image, a heading, or a banner — to fully render after a visitor lands on your page. It's effectively answering the question "how long does the user wait before they see the main thing on this page?" Google's published threshold for "good" LCP is 2.5 seconds or less; anything past 4 seconds is considered poor.
A slow LCP is usually caused by large uncompressed images, slow server response time, or render-blocking resources delaying the browser's ability to paint content. It's also the metric most directly tied to the "does this page feel fast" first impression, which is exactly why it correlates so strongly with bounce rate and conversion data — see What Slow Load Times Are Really Costing Your Business for the conversion side of that relationship.
What does CLS (Cumulative Layout Shift) measure?
CLS measures visual stability — specifically, how much content unexpectedly shifts around on the page as it loads. You've experienced this yourself: you go to tap a button, and an ad or image loads in above it at the last second, shifting the layout and making you tap the wrong thing. Google's "good" threshold for CLS is a score of 0.1 or lower.
Common causes include images or ads without reserved space, web fonts that swap in and change text size, and dynamically injected content pushing existing elements down. Beyond the annoyance factor, layout shift directly damages trust — a page that jumps around under a visitor's cursor reads as unpolished, which matters most at exactly the moment a visitor is deciding whether to click "buy" or "submit."
What does INP (Interaction to Next Paint) measure?
INP measures responsiveness: how long it takes for the page to visibly respond after a visitor clicks, taps, or types something. It replaced First Input Delay as an official Core Web Vital because it captures responsiveness across the entire visit, not just the very first interaction. Google's published "good" threshold for INP is 200 milliseconds or less.
Core Web Vitals are three Google-published metrics — Largest Contentful Paint (LCP, target ≤2.5s), Cumulative Layout Shift (CLS, target ≤0.1), and Interaction to Next Paint (INP, target ≤200ms) — that measure how fast a page renders, how visually stable it is, and how responsive it feels to real user interaction, respectively.
A poor INP is usually caused by heavy JavaScript execution blocking the browser's main thread, often from third-party scripts, trackers, or an overloaded event handler. It's the metric most likely to be invisible during casual testing but very noticeable to a real visitor trying to actually use the page — clicking "add to cart" and having nothing happen for half a second is a classic INP problem.
What are Google's official "good" thresholds?
Here's the full picture in one place, since these three numbers are worth having on hand. The thresholds come from Google's own documentation on web.dev, and Google assesses each one at the 75th percentile of real page loads.
| Metric | Measures | Good | Needs Improvement | Poor |
|---|---|---|---|---|
| LCP | Load speed of main content | ≤ 2.5s | 2.5s – 4s | > 4s |
| CLS | Visual stability | ≤ 0.1 | 0.1 – 0.25 | > 0.25 |
| INP | Interaction responsiveness | ≤ 200ms | 200ms – 500ms | > 500ms |
Why do Core Web Vitals matter beyond SEO?
Google factors Core Web Vitals into search ranking, which is reason enough to care — but the deeper reason is that these three metrics are proxies for the same experience that drives conversions. A page with poor LCP is a page visitors wait too long for; a page with poor CLS is one that feels broken; a page with poor INP is one that feels unresponsive. Studies such as Deloitte's "Milliseconds Make Millions" and Portent's site-speed research tie exactly these kinds of delays to lower conversion rates and higher bounce rates. In other words, fixing your Core Web Vitals scores and fixing your conversion rate are largely the same project viewed from two different dashboards.
Do all three metrics matter equally?
Not necessarily for every site — it depends on what's actually broken. A content-heavy blog with large hero images is more likely to struggle with LCP than INP, while an interactive web app with lots of client-side JavaScript is more likely to have INP problems than layout-shift issues. That said, Google's assessment of a page's overall Core Web Vitals status requires all three metrics to be in the "good" range, so a strong LCP score doesn't offset a poor CLS score in terms of the page passing overall.
In practice, most sites have one metric that's clearly the weakest link, and that's usually the highest-leverage place to focus first. An audit that breaks your results into the three individual scores, rather than one blended number, makes it obvious which one to prioritize.
How do Core Web Vitals relate to the load-time-and-revenue research?
The connection is direct, even though they come from different sources. LCP is essentially a precise, standardized way of measuring the same "how long until the page feels loaded" question that the conversion research addresses more broadly — Portent's 2022 data showing B2B lead-generation conversion rates falling from roughly 40% at one second to 29% at three seconds is describing the practical impact of exactly the kind of delay LCP measures. CLS and INP capture two additional dimensions — stability and responsiveness — that a raw load-time number doesn't fully account for, which is part of why Google added them: a page can load quickly by the clock and still feel bad to use if it shifts around or ignores clicks.
How do I check my Core Web Vitals?
The most reliable way is to run an automated audit against your live URL rather than guessing from a general sense of "the site feels okay." A proper check pulls real performance data and breaks it into these exact three metrics, so you know precisely which one — LCP, CLS, or INP — is holding your score back, rather than treating "slow" as one undifferentiated problem.
If this is on your list, see our guides on how website speed affects conversion rates and PageSpeed Insights vs GTmetrix vs Pingdom.
