Core Web Vitals (CWV)
Core Web Vitals are Google's three primary user-experience metrics: Largest Contentful Paint (LCP) measuring loading performance, Interaction to Next Paint (INP) measuring responsiveness (replaced FID in March 2024), and Cumulative Layout Shift (CLS) measuring visual stability. Combined, they form the Page Experience signal Google uses for ranking.
Also called: CWV, Page Experience signals · Last updated: May 27, 2026 · By Joseph W. Anady
Why it matters.
Core Web Vitals became a Google ranking factor in June 2021 and have been refined every year since. The 2026-current thresholds: LCP <= 2.5 seconds, INP <= 200 milliseconds, CLS <= 0.1. Pages need to hit all three at the 75th percentile of real user traffic (measured via CrUX field data) to qualify as 'Good.' Failing one is enough to lose the Page Experience boost.
How it works.
Google measures CWV from real users via the Chrome User Experience Report (CrUX), aggregated to the 75th percentile per URL. Lighthouse provides lab-test approximations but is debug-only — CrUX field data is what Google ranks on. Each metric has Good (green) / Needs Improvement (yellow) / Poor (red) thresholds. Page Experience signal influences ranking in ways Google has confirmed but doesn't quantify publicly.
2026 reality check.
INP failures are the most common Page Experience problem in 2026. Approximately 43% of sites fail INP at the 75th percentile (industry data 2025-2026), vs ~30% failing LCP and ~17% failing CLS. INP failures often stem from large JavaScript bundles, blocking third-party scripts, or unoptimized event handlers. The fix is usually: code-split aggressively, defer non-critical JS, audit third-party tag bloat.
Data points
- Three metrics: LCP <=2.5s, INP <=200ms, CLS <=0.1 at 75th percentile of real users (CrUX field data)
- INP replaced FID in March 2024 (stricter, harder to pass)
- Approximately 43% of sites fail INP at p75 vs 30% LCP, 17% CLS (industry data 2025-2026)
- Page Experience confirmed ranking signal since June 2021
- TDG standard build hits 95+ Lighthouse across all 4 scores routinely
First-hand insight from ThatDeveloperGuy.
ThatDeveloperGuy targets Lighthouse 95+ on every site we ship as a debug-time check, with CrUX field data the production gating signal. Our standard build configuration (hand-coded HTML+CSS+vanilla-JS, AVIF+WebP images, no third-party CDN abuse, no Cloudflare, brotli compression, server-side caching) routinely produces 95+ across all 4 Lighthouse scores and Good CrUX status on all 3 CWV metrics. The biggest 2025-2026 INP improvement: replacing third-party Lottie animations with CSS animations.
How TDG approaches it
TDG's CWV stack: AVIF + WebP images via picture element with appropriate sizes, server-side rendering or static HTML (no client-side rendering for content), Brotli compression at nginx level, HTTP/3 enabled, no Cloudflare or third-party CDN (eliminates handoff latency), minimal JS (vanilla where possible, no jQuery, no Lottie), passive event listeners, no layout shifts during load.
Common mistakes.
- Optimizing for Lighthouse score instead of CrUX field data (lab vs real-world divergence)
- Ignoring INP because it 'used to be FID' (INP is stricter and harder to hit)
- Loading Google Tag Manager + Facebook Pixel + Hotjar + chat widget without measuring impact
- Using large client-side framework bundles (React/Vue/Angular) for content sites
- Skipping image optimization (LCP element is usually an image)
FAQ.
What's the difference between Lighthouse and CrUX?
Lighthouse is a lab test running in your browser — synthetic, isolated, no real-user variance. CrUX is the Chrome User Experience Report, aggregating real user data from Chrome users. Google ranks on CrUX, not Lighthouse. Use Lighthouse for debug, CrUX for production status.
Why did Google replace FID with INP?
FID measured only the first input delay. INP measures responsiveness throughout the page session, which better reflects user experience. INP is harder to pass — many sites that passed FID fail INP.
How do I check my CrUX data?
PageSpeed Insights at pagespeed.web.dev shows your URL's CrUX field data + Lighthouse lab data side by side. Search Console > Core Web Vitals report shows site-wide aggregated CrUX status.
Does CWV affect ranking?
Yes — Page Experience is a confirmed ranking signal. Google won't quantify the weight publicly, but failing CWV typically costs 5-15 percent of organic ranking on competitive queries.
Can I exempt specific URLs from CWV measurement?
No. CrUX measures all sufficiently-trafficked URLs. The only way to avoid measurement is to have insufficient traffic, which is its own problem.
Maintained by Joseph W. Anady at ThatDeveloperGuy. Back to glossary · Suggest a term