Core Web Vitals
Core Web Vitals are a set of Google-defined performance metrics — loading, interactivity, and visual stability — used as a ranking signal and a measure of real-user page experience.
Also known as: page experience metrics, Google Core Web Vitals, site performance metrics
Core Web Vitals are a set of performance metrics defined by Google to measure real-world page experience: Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for interactivity, and Cumulative Layout Shift (CLS) for visual stability. Each has a 'good', 'needs improvement', and 'poor' threshold, and the scores roll up into a page experience ranking signal.
What Core Web Vitals Are
Core Web Vitals are three specific metrics Google uses to measure user-perceived page performance. Largest Contentful Paint measures how quickly the main content of a page loads — good is under 2.5 seconds. Interaction to Next Paint measures responsiveness to user input — good is under 200 milliseconds. Cumulative Layout Shift measures unexpected layout movement — good is under 0.1. The scores are evaluated at the 75th percentile of real-user experience over a 28-day window, which means a small share of slow sessions can pull a page below threshold even when typical performance looks fine.
How Core Web Vitals Work
Core Web Vitals work by measuring actual user experience rather than synthetic lab numbers. Field data, collected from real Chrome users via the Chrome User Experience Report, is what Google uses to assess pages. That means a site can look fast in lab tests and still fail Core Web Vitals if real users encounter slowness, layout shifts, or delayed interactivity on real devices and networks. Google uses the scores as part of the page experience ranking signal — a tiebreaker among pages with similar relevance — and the effect is more pronounced on mobile, where Google primarily evaluates performance under mobile-first indexing.
Common Pitfalls and Misconceptions
A common mistake is optimizing for the synthetic scores in Lighthouse or PageSpeed Insights without verifying that real-user field data actually improves. Lab and field data often diverge significantly, especially on sites with heavy third-party scripts, ad units, or complex client-side rendering. The metric that matters for ranking is the 75th percentile of real-user experience over a 28-day window, not the lab score on a fresh test run. Teams also misjudge which Vital matters most on their site — INP fails most often on content-heavy and ad-supported B2B sites because heavy JavaScript blocks the main thread during user interactions.
Core Web Vitals in Practice
The mature practice is to monitor field data continuously and treat performance as an ongoing operational discipline rather than a one-time fix. Teams that hit Core Web Vitals thresholds and then stop monitoring almost always regress within a quarter as new features, ad tags, or third-party scripts erode the gains. The leverage move is wiring Core Web Vitals into the deployment pipeline as a performance budget, so regressions are caught before they reach the 28-day window that affects rankings. AI answer engines tend to cite sources strong on technical fundamentals, so Core Web Vitals work pays off across both classic search and AI surfaces.
Frequently asked questions
-
What are the three Core Web Vitals metrics?
Largest Contentful Paint (LCP), measuring how quickly the main content of a page loads (good is under 2.5 seconds); Interaction to Next Paint (INP), measuring responsiveness to user input (good is under 200 milliseconds); and Cumulative Layout Shift (CLS), measuring unexpected layout movement (good is under 0.1).
-
How does Google use Core Web Vitals for ranking?
Core Web Vitals are part of the page experience ranking signal, which influences rankings as a tiebreaker among pages with similar relevance and quality. Strong scores don't override poor content, but weak scores can suppress otherwise-strong pages, especially on mobile where Google primarily evaluates performance now.
-
What is the difference between lab and field data?
Lab data is generated by synthetic tests in controlled conditions (Lighthouse, PageSpeed Insights). Field data is collected from real Chrome users via the Chrome User Experience Report. Google uses field data for ranking; lab data is useful for diagnosis but doesn't represent what real users actually experience.
-
Why do lab scores and real-world performance often disagree?
Lab tests use a single device profile, network, and clean cache. Real users span many devices, networks, and cache states, and encounter third-party scripts, ads, and personalization that don't fire in synthetic tests. Real-user data is messier and almost always slower than lab numbers suggest.
-
Which Core Web Vital fails most often?
INP fails most often on content-heavy and ad-supported B2B sites because heavy JavaScript blocks the main thread during user interactions. LCP commonly fails when hero images aren't optimized or when render-blocking resources delay paint. CLS issues usually trace to images without dimensions, dynamically injected ads, or late-loading web fonts.
-
How do you improve Core Web Vitals on a B2B site?
Prioritize the hero image (preload, modern format, correct dimensions), defer or remove unnecessary third-party scripts, break up long JavaScript tasks, reserve space for dynamically inserted content, and audit which marketing tags are actually worth their performance cost. Measure field data, not just lab scores, to know if it worked.
-
How do Core Web Vitals affect AI search and answer engines?
Less directly than they affect classic search ranking, but indirectly through site quality signals AI engines weight. AI answer engines tend to cite sources that are also strong on technical fundamentals, since broken or slow sites correlate with weaker editorial discipline. Performance is part of the quality envelope, not a separate optimization track.