Core Web Vitals in 2026: What Changed and What Matters
Core Web Vitals (CWV) have been a Google ranking factor since 2021. But if you last checked your metrics a year ago, the rules have changed. The biggest shift: FID is gone, INP is in, and Google is paying closer attention to real-user performance data than ever before.
What Are Core Web Vitals in 2026
Core Web Vitals are three metrics that measure real-user experience on your website:
| Metric | What It Measures | Good Threshold |
|---|---|---|
| LCP (Largest Contentful Paint) | How fast the main content loads | ≤ 2.5 seconds |
| INP (Interaction to Next Paint) | How fast the page responds to user actions | ≤ 200 ms |
| CLS (Cumulative Layout Shift) | How much the layout shifts unexpectedly | ≤ 0.1 |
These thresholds are based on the 75th percentile of real user data collected through the Chrome User Experience Report (CrUX). That means 75% of your visitors need to have a "good" experience — not just the average.
What Changed: INP Replaced FID
The most significant change happened in March 2024: Interaction to Next Paint (INP) officially replaced First Input Delay (FID) as a Core Web Vital.
Why did Google make the switch?
- FID only measured the first interaction. A user clicks a button immediately after page load — FID measured that delay. But what about the tenth click? The scroll? The form submission?
- INP measures all interactions. Every click, tap, and keyboard input throughout the entire page session is tracked. INP reports the worst interaction (at the 98th percentile), giving a much more accurate picture of responsiveness.
- Most sites passed FID easily. According to CrUX data, over 90% of origins had good FID scores. INP is harder — many sites that passed FID fail INP.
If your site had "good" Core Web Vitals a year ago but you haven't checked since, there's a real chance your INP score is failing.
How Core Web Vitals Affect Rankings
Google confirmed that page experience signals, including Core Web Vitals, are a ranking factor. Here's what we know:
- CWV is a tiebreaker, not a dominant factor. Content relevance still matters most. But between two equally relevant pages, the faster one wins.
- Bad CWV can hurt you in competitive niches. If your competitors have good CWV and you don't, you're at a disadvantage.
- CWV affects visibility in Top Stories, Discover, and AI Overviews. Google's newer features tend to favor pages with good user experience signals.
The practical takeaway: CWV alone won't get you to page one, but poor CWV can keep you off it.
How to Measure Your Core Web Vitals
Field Data (Real Users)
Field data comes from actual visitors using Chrome. This is what Google uses for ranking:
- Google Search Console → Core Web Vitals report (requires site verification)
- Chrome UX Report (CrUX) → Public dataset of real-user metrics for millions of origins
- PageSpeed Insights → Shows both field and lab data for any URL
Lab Data (Simulated)
Lab data simulates a page load in controlled conditions. Useful for debugging but not used for ranking:
- Lighthouse (built into Chrome DevTools)
- WebPageTest for advanced waterfall analysis
Important: Lab and field data often disagree. A page might score 95 in Lighthouse but fail CWV in the field because real users have slower devices and networks. Always prioritize field data.
How to Fix Each Metric
Fix LCP (Largest Contentful Paint)
LCP measures how fast your main content appears. Common culprits:
- Unoptimized images — Use WebP/AVIF, set explicit width/height, lazy-load below-the-fold images
- Render-blocking resources — Defer non-critical CSS and JavaScript
- Slow server response (TTFB) — Use a CDN, enable caching, optimize your backend
- Client-side rendering — If your framework renders on the client, consider SSR or static generation
<!-- Preload your LCP image -->
<link rel="preload" as="image" href="/hero.webp" fetchpriority="high" />
<!-- Use responsive images -->
<img
src="/hero.webp"
width="1200"
height="630"
srcset="/hero-400.webp 400w, /hero-800.webp 800w, /hero.webp 1200w"
sizes="(max-width: 800px) 100vw, 1200px"
alt="Description"
fetchpriority="high"
/>
Fix INP (Interaction to Next Paint)
INP is the newest metric and the hardest to optimize. It measures the delay between a user action and the visual response:
- Break up long tasks — JavaScript tasks over 50ms block the main thread. Use
requestIdleCallbackorscheduler.yield()to break them up - Reduce JavaScript — Audit your bundles. Remove unused libraries. Defer third-party scripts
- Avoid layout thrashing — Don't read and write DOM properties in tight loops
- Optimize event handlers — Keep click/scroll handlers lightweight
// Bad: long-running handler blocks the thread
button.addEventListener("click", () => {
processData(); // 200ms
updateDOM(); // 100ms
sendAnalytics(); // 50ms
});
// Better: yield between tasks
button.addEventListener("click", async () => {
updateDOM(); // Visual feedback first
await scheduler.yield(); // Let browser paint
processData(); // Heavy work after
await scheduler.yield();
sendAnalytics(); // Non-critical last
});
Fix CLS (Cumulative Layout Shift)
CLS measures unexpected visual movement. Fixes are usually straightforward:
- Set dimensions on images and videos — Always include
widthandheightattributes - Reserve space for ads and embeds — Use
min-heighton containers - Avoid inserting content above existing content — Banners, cookie notices, and dynamically loaded elements are common offenders
- Use
font-display: swapcarefully — Web fonts can cause layout shifts when they load
Quick Audit: Check All Three Metrics at Once
Instead of running multiple tools, you can check all Core Web Vitals alongside 23 other SEO checks in a single scan with CheckSEO. The audit takes 30 seconds and covers performance, meta tags, structured data, security, and AI Readiness — categories that tools like Ahrefs and SEMrush don't check.
For a complete technical audit approach, see our Technical SEO Checklist.
Run a free SEO audit on checkseo.site
References
- web.dev — Core Web Vitals
- web.dev — Interaction to Next Paint (INP)
- web.dev — INP is now a Core Web Vital
- web.dev — Largest Contentful Paint (LCP)
- web.dev — Cumulative Layout Shift (CLS)
- web.dev — Optimize INP
- web.dev — Optimize LCP
- web.dev — Defining Core Web Vitals Thresholds
- Google — Page Experience Documentation
- Google — Core Web Vitals Report
- Google — Chrome UX Report
- Search Engine Land — Core Web Vitals Ranking Factor Guide