What are Core Web Vitals?
Core Web Vitals describe how a page loads, responds to input and holds its layout steady. LCP, INP and CLS assess those experiences separately. They are useful for investigating what visitors encounter, but they do not establish content relevance, accessible interaction or successful completion of a customer’s task.
Start with the experience that is failing. A delayed product photo, an unresponsive filter and a paragraph pushed down by an advertisement require different evidence. One headline “speed score” hides that distinction.
What the measurements mean for search
Google says Core Web Vitals are used by its ranking systems. It also says good measurements do not guarantee top rankings. Its page-experience guidance does not specify a universal ranking lift, an equal weight for each metric or a fixed tiebreaker rule.
Treat performance improvements as changes to the reader’s experience. If you also want to evaluate bookings, purchases or organic traffic, measure those outcomes separately rather than treating a passing threshold as proof of revenue.
Read the measurement scope
Field data describes observed visits; lab data comes from a controlled test. Both are useful. PageSpeed Insights shows CrUX real-user data over a trailing 28-day collection period and separate Lighthouse diagnostics. Its field result can describe the tested URL or the whole origin, depending on available data.
Check the device, period and URL-versus-origin label before comparing results. An origin aggregate is not a direct measurement of every page. If neither scope has enough samples, missing field data should remain unknown; a lab run can still help investigate the page.
Search Console’s Core Web Vitals report groups URLs with similar experiences and does not list every indexed URL. A group warning identifies an investigation scope, not proof that every visit to each member page was equally slow.
Current metric thresholds
The Web Vitals documentation assesses the 75th percentile, with mobile and desktop segmented. The following bands use inclusive good boundaries; CLS is a unitless score, not a duration. These are published thresholds, not observations of theStacc or its customers.
| Metric | Good | Needs improvement | Poor |
|---|---|---|---|
| LCP, seconds | ≤2.5 | >2.5 and ≤4.0 | >4.0 |
| INP, milliseconds | ≤200 | >200 and ≤500 | >500 |
| CLS, unitless score | ≤0.1 | >0.1 and ≤0.25 | >0.25 |
LCP concerns a large visible content element; INP concerns interaction responsiveness; CLS concerns unexpected layout movement. CLS can include shifts after initial load and uses the largest burst of eligible shift scores, rather than simply adding every shift during the whole visit.
An illustrative reporting mismatch
Suppose a developer’s controlled test shows an improved product-page load, while the field report still flags a group of product URLs. That is an illustrative scenario, not a customer case or measured result. The immediate question is whether the two observations cover the same pages, devices and time period.
Record the release time and verify the change on representative pages. A historical field window can include earlier experiences, while the local test describes its current conditions. Keep both observations rather than replacing the field result with a convenient lab score.
Core metrics and supporting diagnostics
First Contentful Paint (FCP), Time to First Byte (TTFB) and Total Blocking Time (TBT) can help diagnose performance. They are not additional Core Web Vitals. Web Vitals distinguishes those supporting metrics from the current set.
A navigation-only Lighthouse run cannot measure INP because it performs no qualifying user input. TBT can suggest responsiveness problems, but it is not interchangeable with observed INP. Interactive lab testing and real-user measurements answer different questions.
Turn a metric into a specific investigation
- Identify the affected metric and reader task.
- Record the URL or group, device and observation period.
- Reproduce a relevant load or interaction under stated conditions.
- Make a targeted change and check that the task still works.
- Retain the before-and-after evidence and monitor available field data.
For loading evidence, see the LCP investigation guide. For slow input, use the INP investigation guide. They explain how to identify the dependency before choosing a fix.
Avoid false certainty
Do not call a missing value zero, an origin value a measured page result or a green lab score a universal pass. Also avoid claiming that a particular image format, hosting change or script attribute will produce a fixed improvement. The relevant dependency and audience still need to be checked.
A report may contain a valid assessment even when INP has insufficient samples. PageSpeed Insights documents this specific exception when LCP and CLS have enough good field data. That exception does not establish an observed INP result; preserve the missing metric explicitly.
Define the scope of technical help
Before buying technical help, agree on access to the measurements, responsibility for implementation and the evidence used to retest. A publishing workflow and an engineering engagement have different requirements. Review theStacc’s Blog SEO workflow when content operations are the task, and confirm any performance work separately.
Additional reporting questions
Can one good metric compensate for another poor metric?
Not in the published all-metric assessment. Where the required field data is sufficient, the good 75th-percentile targets must be met for each applicable Core Web Vital. Keep individual results visible rather than averaging unlike units into a made-up overall score. PageSpeed Insights documents its insufficient-INP exception separately.
Does a Search Console group describe each individual visit?
No. A URL group summarizes similar pages using aggregated real-user measurements. Visits within that group can differ, and a particular URL can be an outlier. Use the group to identify a shared investigation, then verify representative pages and the task affected before assuming that every visit has the same result.
Related terms
Use Largest Contentful Paint for loading measurements, INP score thresholds for responsiveness and render-blocking resources for paint dependencies.
Sources and editorial note
Primary references are linked beside the relevant explanations and were checked on October 12, 2026. AI assisted this revision. Examples are illustrative. No customer measurement, independent performance experiment, private Search Console evidence or named human approval is claimed.
Explore this topic: Core Web Vitals Statistics: 55 Benchmarks for 2026 · How to Improve Core Web Vitals in 8 Steps (2026 Guide).