What Core Web Vitals measure
Core Web Vitals are a short list of speed and stability metrics that Google picked because each one describes something a visitor actually feels and can be measured in real browsers. The current set covers three things:
- Loading: LCP (Largest Contentful Paint), when the main image or text block appears.
- Responsiveness: INP (Interaction to Next Paint), how quickly the page visibly reacts to clicks, taps and key presses.
- Visual stability: CLS (Cumulative Layout Shift), how much content jumps around while the page is open.
Google says the set will evolve. It already has: INP replaced First Input Delay (FID) as the responsiveness metric in March 2024.
Core Web Vitals thresholds
| Metric | Good | Needs improvement | Poor |
|---|---|---|---|
| LCP | 2.5 s or less | Over 2.5 s, up to 4 s | Over 4 s |
| INP | 200 ms or less | Over 200 ms, up to 500 ms | Over 500 ms |
| CLS | 0.1 or less | Over 0.1, up to 0.25 | Over 0.25 |
Each metric is judged at the 75th percentile of page loads, with mobile and desktop counted separately. A page passes the assessment only when it meets the good target for all three at the 75th percentile. The slowest quarter of loads doesn't count against you; the rest must be good.
How a page passes
Pass = p75 LCP ≤ 2.5 s AND p75 INP ≤ 200 ms AND p75 CLS ≤ 0.1
The 75th percentile (p75) is the value that three in four page loads beat. Sort all loads of a page from best to worst; the one at the 75% mark is its p75. One bad metric fails the page, even if the other two are excellent.
The other web performance metrics
Several related metrics aren't Core Web Vitals but help explain them:
| Metric | Kind | What it tells you |
|---|---|---|
| FCP | Field and lab | When the first text or image appears. A slow FCP usually means a slow LCP. |
| TTFB | Field and lab | How long the server took to start answering. Every other loading metric waits on it. |
| TBT | Lab only | How long the main thread was blocked during load. Lighthouse's stand-in for INP. |
| Speed Index | Lab only | How quickly the visible page fills in during a test run. |
| FID | Retired | The delay before the first interaction was handled. Replaced by INP in 2024. |
Field metrics can be measured for real visitors; lab metrics only exist inside a test tool. See real user monitoring for why that difference matters.
Example
A pricing page has these mobile p75 values for the last month: LCP 2.1 s, INP 340 ms, CLS 0.04. LCP and CLS are good, but INP needs improvement, so the page fails on mobile. On desktop it scores LCP 1.2 s, INP 90 ms and CLS 0.02 and passes. The fix belongs on mobile: probably a heavy script that runs when people tap the plan toggle.
Do Core Web Vitals affect SEO?
Google says Core Web Vitals are used by its ranking systems and recommends reaching good scores. It also says good scores don't guarantee top rankings, and that chasing a perfect score only for SEO may not be the best use of your time. Relevant content still comes first. Google's own field data comes from the Chrome UX Report (CrUX), a dataset of real Chrome users' experiences that Google Search uses for page experience. Smaller sites and pages often have too few visits to appear in it.
The stronger reason to care is money. A page that loads slowly or jumps under the visitor's thumb can lose buyers whatever its ranking. That is something you can check against your own conversion rate.
How to measure Core Web Vitals
- Field data from your own visitors: a real user monitoring tool or Google's open-source web-vitals library. This covers every page, including ones too small for CrUX.
- CrUX: PageSpeed Insights and Search Console show Google's field data for pages and origins with enough Chrome traffic.
- Lab tests: Lighthouse and PageSpeed Insights' lab section, for debugging one load in a controlled setup. They report TBT instead of INP, because a test run has no real user clicking.
Common Core Web Vitals mistakes
- Treating a Lighthouse score as the assessment. The pass or fail comes from field data at the 75th percentile, not a lab run.
- Mixing mobile and desktop. They are judged separately, and phones are usually the ones that fail.
- Fixing the homepage only. Landing and checkout pages carry the buyers; measure them per page.
- Reading speed as the cause of every lost sale. Slow loads come with older devices and weaker networks, which change buying behavior too. Compare like with like.
How MetricRaven measures Core Web Vitals
With Page speed turned on in Settings (it's off by default, on every plan), the tracker loads a small add-on built on Google's web-vitals library. For each page load it sends one snapshot with LCP, INP, CLS, FCP and TTFB from the real visitor. Nothing is stored in the browser.
- Pages and entry pages: LCP and INP columns at the 75th percentile with a green, amber or red dot, next to each page's purchase rate. Hover for CLS, FCP, TTFB and the number of loads. A page needs 10 loads in the period first.
- Slow pages that lose buyers: in Traffic → Pages → Details (and through the API, CLI and MCP), a list that compares visitors with a slow load (LCP over 4 s or INP over 500 ms) to visitors with a fast one (LCP 2.5 s or less and INP 200 ms or less) and estimates the buyers the gap cost.
- Retention: snapshots are kept 90 days.
MetricRaven doesn't report the lab-only metrics, TBT and Speed Index, or the retired FID. See Page speed vs conversion.
Questions
- What are the three Core Web Vitals?
- Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness and Cumulative Layout Shift (CLS) for visual stability.
- What are good Core Web Vitals scores?
- LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, each at the 75th percentile of page loads, measured separately for mobile and desktop.
- Are Core Web Vitals a ranking factor?
- Google says Core Web Vitals are used by its ranking systems, but that good scores don't guarantee top rankings and that relevant content matters more. Their bigger effect is often on whether visitors stay and buy.
- What is the Chrome UX Report?
- The Chrome UX Report (CrUX) is Google's public dataset of how real Chrome users experience websites, including the Core Web Vitals. PageSpeed Insights and Search Console read it. Pages without enough Chrome traffic aren't in it.
- Is FID still a Core Web Vital?
- No. INP replaced First Input Delay as the responsiveness Core Web Vital in March 2024. See First Input Delay.