One-Line Definition
Core Web Vitals are a set of three standardized, user-centric performance metrics — Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) — that Google uses to quantify how fast, responsive, and visually stable a web page feels to real visitors, and which now feed directly into search ranking signals.
Real-Life Analogy
Think of walking into a physical store. Three things determine whether you stay or walk out:
1. How fast someone acknowledges you — if you stand at the counter for 10 seconds with no service, you leave. That's LCP: how quickly the main content appears.
2. How responsive the staff is when you ask a question — if you tap the bell and nothing happens for three seconds, you get frustrated. That's INP: how quickly the page reacts to your click or tap.
3. Whether the store layout jumps around — if you reach for a product and the shelf suddenly shifts two feet to the left, you grab the wrong thing or knock everything over. That's CLS: how much the layout moves while you're trying to interact.
A store can be beautiful and cheap, but if it fails these three tests, customers leave — and Google's data shows the same happens online.
Core Formula
Each metric has a defined measurement and a three-tier threshold (Good / Needs Improvement / Poor):
| Metric | Full Name | What It Measures | Good | Needs Improvement | Poor |
|---|---|---|---|---|---|
| **LCP** | Largest Contentful Paint | Time until the largest visible element (hero image, headline, video poster) finishes rendering | ≤ 2.5s | 2.5s – 4.0s | > 4.0s |
| **INP** | Interaction to Next Paint | Latency from user input (click, tap, keypress) to the next visual update | ≤ 200ms | 200ms – 500ms | > 500ms |
| **CLS** | Cumulative Layout Shift | Sum of unexpected layout shift scores during the page's lifespan | ≤ 0.1 | 0.1 – 0.25 | > 0.25 |
The composite rule: To "pass" Core Web Vitals at the page level, 75% of real-user page views (measured via the Chrome User Experience Report, or CrUX) must fall in the "Good" range for all three metrics. A page that nails LCP but fails CLS does not pass.
INP replaced First Input Delay (FID) as the official responsiveness metric in March 2024, because FID only measured the *first* interaction's input delay — INP measures *every* interaction (or a high-percentile sample of them) and captures the full duration until the browser paints the response.
Comparison with Related Terms
| Term | Scope | Data Source | Relationship to Core Web Vitals |
|---|---|---|---|
| **Core Web Vitals** | 3 field metrics (LCP, INP, CLS) | Real users (CrUX, RUM) | The headline set — the subset Google elevates |
| **Web Vitals** | Broader program (includes TTFB, FCP, TBT, etc.) | Lab + field | Superset; Core Web Vitals are the three "essential" ones |
| **PageSpeed Insights** | Tool | Lab (Lighthouse) + field (CrUX) | Reports both; lab scores are diagnostic, not ranking inputs |
| **Lighthouse** | Lab audit tool | Synthetic, throttled environment | Useful for debugging CWV, but scores ≠ CWV pass/fail |
| **Google Page Experience** | Ranking framework | Aggregates CWV + HTTPS + mobile-friendliness + no intrusive interstitials | Core Web Vitals are the *performance* component of Page Experience |
| **TTFB / FCP / TBT** | Supporting diagnostics | Lab + field | Not Core Web Vitals themselves, but often root causes of bad LCP or INP |
The critical distinction: Lighthouse scores are not ranking signals. Google ranks on *field data* (real users), not lab scores. A page can score 95 in Lighthouse and still fail CWV in the field, or vice versa.
Use Cases
1. DTC storefront optimization. A Shopify or headless commerce brand notices mobile conversion dropping 12% on product pages. CrUX reveals LCP of 4.3s (poor) driven by an unoptimized hero image and render-blocking third-party scripts. Compressing the hero to WebP, preloading it, and deferring chat widgets brings LCP to 2.1s — often worth 5–15% lift in mobile conversion rate.
2. Cross-border checkout flows. For merchants selling into markets with slower networks (Southeast Asia, LATAM, parts of EMEA), INP frequently exceeds 500ms because payment SDKs and address-validation scripts block the main thread. Moving validation to a web worker and lazy-loading the gateway iframe can cut INP by 200–400ms.
3. Paid + organic landing pages. Google Ads landing page experience and Quality Score correlate with CWV. A landing page with CLS of 0.3 (ads injecting above the fold after paint) wastes ad spend — fixing layout reservation for ad slots is a direct ROAS lever.
4. SEO triage at scale. For a catalog of 10,000+ SKUs, teams use CrUX + Search Console's Core Web Vitals report to segment URLs into "poor," "needs improvement," and "good," then prioritize templates (PDP, PLP, blog) rather than individual pages.
5. Competitive benchmarking. CrUX lets you compare your origin's CWV distribution against competitors' origins — useful for setting realistic targets in a category where everyone ships heavy JavaScript.
Misconceptions
"Core Web Vitals is just an SEO thing." It's a *user experience* framework that happens to be a ranking input. The conversion and retention impact usually dwarfs the ranking impact. Treat it as a CRO program, not an SEO checkbox.
"A 100 Lighthouse score means I pass CWV." No. Lighthouse is a lab simulation on a throttled connection. CWV is field data from real devices, networks, and geographies. They often disagree — especially on INP, which Lighthouse can't measure directly (it uses TBT as a proxy).
"It's a one-time fix." CWV regresses constantly. Every new app, tag manager container, A/B test script, or CMS plugin can break LCP or CLS. Mature teams monitor CWV in RUM continuously and set performance budgets in CI.
"CLS is only about images without dimensions." Images are the most common cause, but web fonts swapping (FOIT/FOUT), dynamically injected banners, cookie notices, and ads without reserved space all cause shifts. Any element that changes position after first paint counts.
"INP is the same as FID." FID measured only input delay before the first interaction. INP measures the full interaction latency — input delay + processing time + presentation delay — across all (or a high percentile of) interactions. INP is strictly harder to pass and more representative of felt responsiveness.
"Mobile and desktop can share one target." They can't realistically. Mobile field data is typically 30–60% slower on LCP and INP due to device and network constraints. Set separate budgets and track them separately in CrUX.
Related Terms
- Largest Contentful Paint (LCP) — loading performance
- Interaction to Next Paint (INP) — responsiveness
- Cumulative Layout Shift (CLS) — visual stability
- First Input Delay (FID) — deprecated predecessor to INP
- Time to First Byte (TTFB) — server response; a root cause of poor LCP
- First Contentful Paint (FCP) — when any content first renders
- Total Blocking Time (TBT) — lab proxy for INP
- Chrome User Experience Report (CrUX) — Google's public field dataset
- Real User Monitoring (RUM) — first-party field measurement
- Google Page Experience — the broader ranking framework containing CWV
- Search Console Core Web Vitals report — URL-group-level CWV status
- Performance budget — engineering constraint to prevent CWV regressions