Definition
Core Web Vitals are three field-measured metrics Google uses to grade the real-world experience of a web page: how quickly the main content loads, how fast the page responds to input, and how much the layout jumps around while it settles. The three are Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness, and Cumulative Layout Shift (CLS) for visual stability. They’re a subset of Google’s broader “Web Vitals” program, and they’re scored from actual Chrome users rather than a lab test.
The scores come from the Chrome User Experience Report (CrUX), and Google judges a page at the 75th percentile of visits over a rolling 28-day window. In plain terms: at least 75% of real page views have to hit the “good” mark before the page passes. A metric can sit in one of three bands — good, needs improvement, or poor.
Disambiguation: “Core Web Vitals” is a Google-specific standard, not a neutral industry term. The metric names, thresholds, and the 75th-percentile rule are all defined and periodically revised by Google’s Chrome team. Other performance metrics (Time to First Byte, First Contentful Paint, Total Blocking Time) are useful for diagnosis but sit outside the Core Web Vitals set because they aren’t field-measurable or user-centric in the way Google requires. Treat CWV as one vendor’s operational definition of page experience that happens to carry ranking weight, not as the whole of web performance.
Why it matters for marketing
Core Web Vitals became part of Google’s page experience ranking signals in June 2021, which is the moment site speed stopped being purely an engineering concern and landed on the marketing team’s desk. The catch worth being honest about: CWV is a tiebreaker, not a trump card. Google has repeatedly said page experience won’t rescue thin content or override a far more relevant result. Where it earns its keep is in competitive SERPs, when two pages are close on relevance and one simply feels faster.
The bigger commercial argument is conversion, not ranking. A hero image that shifts under someone’s thumb as they reach to tap, a checkout button that lags half a second on submit, a mobile page that stalls before anything’s readable — these are quiet revenue leaks, and they show up in bounce and abandonment long before they show up in rankings. Google and web.dev publish case studies tying CWV improvements to measurable lifts in conversions and sales, which is why the metric belongs in growth conversations and not just in a developer’s backlog.
See also: Largest Contentful Paint (LCP) · Interaction to Next Paint (INP) · Cumulative Layout Shift (CLS) · AI Overviews
How it works
Each of the three metrics captures a different slice of the loading experience, and a page has to pass all three to earn an overall “good” assessment.
- LCP marks the moment the largest visible element in the viewport — usually a hero image, a heading, or a big text block — finishes rendering. Good is 2.5 seconds or less.
- INP watches every eligible interaction across the whole visit (clicks, taps, key presses) and reports roughly the worst response time, from input to the next visual update. Good is 200 milliseconds or less. INP replaced First Input Delay on March 12, 2024; FID only measured the delay before the first interaction, which meant a page could pass FID and still feel sluggish afterward.
- CLS sums up the unexpected layout shifts that happen as the page loads. It’s a unitless score. Good is 0.1 or less.
The scoring runs on field data from CrUX, so a spotless Lighthouse run on your own laptop means little if a quarter of your visitors are on mid-range phones over a patchy connection. Google evaluates at the page level where it has enough data, and falls back to a group of pages or the whole origin when a single URL is too sparse.
The thresholds
| Metric | What it measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| Largest Contentful Paint (LCP) | Loading | ≤ 2.5 s | 2.5 s – 4.0 s | > 4.0 s |
| Interaction to Next Paint (INP) | Responsiveness | ≤ 200 ms | 200 ms – 500 ms | > 500 ms |
| Cumulative Layout Shift (CLS) | Visual stability | ≤ 0.1 | 0.1 – 0.25 | > 0.25 |
All three are assessed at the 75th percentile of page views, segmented across mobile and desktop. Source: Google Search Central and web.dev (see Sources).
How to utilize Core Web Vitals
Start where the data is real. Open the Core Web Vitals report in Google Search Console to see which URLs (or URL groups) land in poor, needs-improvement, or good — this is field data, so it reflects your actual audience. Then run individual problem pages through PageSpeed Insights, which pairs field data with a Lighthouse lab diagnosis and tells you why a metric is slow.
Common use cases:
- Prioritizing an engineering backlog by business impact. Rank fixes by the traffic and revenue behind the failing pages, not by whichever number looks ugliest. A poor CLS on a low-traffic help article matters less than a mediocre LCP on your top landing page.
- Pre-launch and template QA. Because layout and script decisions in a template propagate to every page built on it, catching a CLS or INP problem at the design-system level fixes it everywhere at once.
- Vendor and plugin evaluation. Third-party tags — chat widgets, analytics, ad libraries — are frequent culprits behind bad INP and CLS. CWV gives you a concrete number to hold a vendor to.
- Reporting page experience to non-technical stakeholders. The three-band good/needs-improvement/poor framing travels well in an executive deck.
A practical rhythm: fix, publish, wait. CrUX updates on roughly a 28-day cycle, so field scores won’t move the instant you ship. Change one thing, let the data catch up, then measure again.
Best practices
- Design for the 75th-percentile user, not your own device. The whole point of field data is that it exposes the fourth-slowest visitor out of every four. Test on a throttled mid-range phone.
- Reserve space for anything that loads late. Set explicit width and height on images and video, and hold room for ads and embeds before they arrive. That’s most of CLS solved.
- Ship less JavaScript, and break up the long tasks that remain. Heavy main-thread work is the usual reason INP drifts past 200 ms. Defer non-essential scripts and yield to the main thread during expensive loops.
- Make the LCP element appear sooner. Find the single largest above-the-fold element, then prioritize it — preload it, compress it, and clear anything blocking it.
- Don’t chase green as an end in itself. A passing CWV report is necessary, not sufficient. If the content underneath is thin, a perfect CLS won’t rank it. Treat CWV as the technical floor beneath good content, not a substitute for it.
- Watch it continuously. New plugins, fresh content, and platform updates all move the numbers. Scores drift; a one-time fix isn’t a permanent one.
Future trends
Core Web Vitals aren’t static — Google has stated plainly that stable metrics can be retired and replaced, which is exactly what happened when INP took over from FID. Expect the set to keep evolving even when the headline thresholds hold steady. The Chrome team’s web.dev and Google Search Central blogs remain the authoritative place to watch, and Google has historically given site owners six to twelve months’ notice before a metric change lands.
There’s also an AI-search angle that’s grown sharper through 2026. Fast, stable, well-structured pages are easier for crawlers and answer engines to render and parse, which ties technical performance to visibility in AI Overviews and other generative surfaces, not just the classic ten blue links. The through-line is the same one it’s always been: a page that renders cleanly and quickly is easier for both people and machines to use.
FAQs
What are the three Core Web Vitals? Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness), and Cumulative Layout Shift (visual stability). A page has to pass all three to be rated “good” overall.
What are the passing thresholds? LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less — each measured at the 75th percentile of real visits across mobile and desktop.
Did INP really replace FID? Yes. Interaction to Next Paint became the responsiveness Core Web Vital on March 12, 2024, and First Input Delay was retired. INP is stricter because it looks at every interaction during a visit, not just the delay on the first one. Any guide still listing FID as a Core Web Vital is out of date.
Are Core Web Vitals a Google ranking factor? Yes, since June 2021, as part of the page experience signals. In practice they act as a tiebreaker between pages of comparable relevance rather than something that outranks stronger content.
What’s the difference between field data and lab data? Field data (from CrUX) is what real Chrome users experienced. Lab data (from Lighthouse) is a controlled test on a simulated device. Google grades you on field data; lab data is for diagnosis. A great lab score with a failing field score is common and means your real audience is slower than your test rig.
Why does my page pass on my laptop but fail in Search Console? Because Search Console reports field data at the 75th percentile — the experience of your slower real-world visitors, often on mid-range phones. Your fast device and connection aren’t representative.
How long until a fix shows up in my scores? CrUX updates on roughly a 28-day rolling window, so field scores lag your deployment. Ship the change, wait, then re-measure.
Do Core Web Vitals apply to mobile and desktop separately? Yes. The thresholds are the same, but scores are reported separately for mobile and desktop. Mobile is usually the weaker report because the thresholds were calibrated around mid-range mobile hardware.
Which tools should I use to measure them? Google Search Console for the site-wide field report, PageSpeed Insights for page-level field-plus-lab diagnosis, and Chrome DevTools or Lighthouse for debugging changes before they go live.
If I pass Core Web Vitals, is my page experience “done”? No. CWV doesn’t cover mobile-friendliness of layout, HTTPS security, or intrusive interstitials — those are separate page-experience considerations. A green CWV report is a floor, not the finish line.
Related Terms
- Largest Contentful Paint (LCP)
- Interaction to Next Paint (INP)
- Cumulative Layout Shift (CLS)
- Domain Authority (DA)
- AI Overviews
- Citation Optimization
- First Input Delay (FID)
- Time to First Byte (TTFB)
- First Contentful Paint (FCP)
- Page Experience
Freshness note: Core Web Vitals metrics and thresholds are set by Google and revised periodically (INP replaced FID in March 2024). Thresholds and the metric set current as of July 2026;
Sources
- Google Search Central — Understanding Core Web Vitals and Google search results: https://developers.google.com/search/docs/appearance/core-web-vitals
- web.dev — Web Vitals: https://web.dev/articles/vitals
- web.dev — How the Core Web Vitals metrics thresholds were defined: https://web.dev/articles/defining-core-web-vitals-thresholds