What Are Core Web Vitals?
Core Web Vitals are three specific metrics — Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) — that Google uses to measure a page's loading speed, responsiveness, and visual stability using real-user field data. Google has described Core Web Vitals as one input into Page Experience, generally acting more as a tiebreaker among otherwise similar-quality content than as a dominant ranking factor on its own. Established
The Three Metrics and Current Thresholds
| Metric | Measures | Good | Needs Improvement | Poor |
|---|---|---|---|---|
| LCP | Loading — time to render the largest content element | ≤ 2.5s | 2.5s – 4.0s | > 4.0s |
| INP | Responsiveness — delay from interaction to visual update | ≤ 200ms | 200ms – 500ms | > 500ms |
| CLS | Visual stability — unexpected layout movement | ≤ 0.1 | 0.1 – 0.25 | > 0.25 |
All three thresholds are assessed at the 75th percentile of real visits, separately for mobile and desktop — meaning a page only passes a given metric if at least 75% of real user experiences meet the "Good" bar. INP replaced First Input Delay (FID) as the responsiveness metric in March 2024, evaluating the worst interaction delay across an entire page visit rather than just the first interaction.
Field Data vs. Lab Data
Field data (also called Real User Monitoring or RUM) comes from actual visits by real Chrome users, aggregated in the Chrome User Experience Report (CrUX) — this is the data Google uses for any Page Experience signal. Lab data comes from a synthetic, controlled test run, typically via Lighthouse, simulating a specific device and network condition. Lab data is reproducible and useful for debugging, but a page can pass in the lab and still fail in the field if real visitors are on slower devices or networks than the simulated test — Search Console's Core Web Vitals report reflects field data, not lab data.
Common Mistakes and Misconceptions
- Chasing a 100/100 Lighthouse score. Lighthouse is lab data; Google's ranking-relevant signal is field data from CrUX, which can differ substantially.
- Treating Core Web Vitals as a major, standalone ranking factor. Google has described it as part of the broader page experience signal, generally most influential as a tiebreaker between pages of otherwise comparable content quality.
- Referencing FID as a current metric. FID was retired in March 2024; INP is the current responsiveness metric.
Where This Fits in NOXEL
NOXEL SEO's Core Web Vitals check reports current field-data status for LCP, INP, and CLS where available and flags pages falling into "Needs Improvement" or "Poor" so they can be prioritized alongside other technical issues.
FAQ
What replaced FID in Core Web Vitals?
Interaction to Next Paint (INP) officially replaced First Input Delay (FID) as a Core Web Vital in March 2024. INP measures the worst interaction delay across an entire visit, not just the first interaction.
Do Core Web Vitals directly determine my ranking?
Google has described Core Web Vitals as part of a broader page experience signal that tends to act as a tiebreaker among pages with otherwise similar content quality, rather than as a dominant ranking factor by itself.
Where do I check my site's real Core Web Vitals?
Google Search Console's Core Web Vitals report and the CrUX (Chrome User Experience Report) dataset reflect real-user field data, which is what Google actually uses — PageSpeed Insights shows both field and lab data side by side.
Do all three metrics need to pass for a page to be considered 'good'?
Yes. A page is only rated as passing Core Web Vitals overall if LCP, INP, and CLS all meet the 'Good' threshold at the 75th percentile for that device type.
Related Concepts
Part of The Complete Guide to AI Search Visibility (2026)
Sources
- Google. web.dev Core Web Vitals documentation. web.dev
- Google Search Central. Understanding Core Web Vitals and Page Experience. developers.google.com