The Core Web Vitals report in Search Console is the one that counts, because it uses field data from real visitors rather than a simulated page load. It is also the report people find most confusing, largely because of how its grouping and timing work.
What the report actually shows
- Field data, collected from real Chrome users over a rolling 28-day window.
- Separate mobile and desktop assessments. Mobile is the harder one and usually the one to fix.
- URLs grouped by similarity, not listed individually.
- Three states — good, needs improvement, poor.
The two things that confuse people
URL groups, not URLs
The report groups similar pages and reports on the group. A handful of example URLs is shown, and the assessment covers everything in that group — usually a template.
This is why fixing the example URLs is the wrong instinct. The finding is about the template they share, so the fix belongs in the template.
The 28-day lag
Because the window is rolling, a fix deployed today takes weeks to be fully reflected. Improvement appears gradually as old data ages out, not as a step change.
Teams frequently conclude a fix did not work when it simply has not aged in yet. Verify with lab tools immediately after deploying, then wait for the field data to confirm.
Not enough data
Groups with too little traffic are excluded entirely. Smaller sites often see very few URLs covered, or the report empty.
That is not a problem to solve. It means too few real visitors for a reliable measurement, and lab tools are your only option there.
Using it properly
- Start with mobile.
- Identify which metric is failing for each group — the three have almost no remedies in common. See failing Core Web Vitals.
- Fix at template level.
- Confirm the change with a lab tool right away.
- Use Validate Fix to request re-evaluation.
- Expect several weeks before the field data agrees with you.
Where it disagrees with PageSpeed Insights
PageSpeed Insights runs a simulated load on a fixed connection and device. Search Console reports what your actual visitors experienced. A site can score well in the simulation and fail here, because real visitors are on slower connections and older phones.
When they disagree, the field data is what is assessed.
Frequently asked questions
Why is my URL not in the report?
Insufficient traffic for a reliable measurement, or it is grouped with similar pages under a different example URL.
How long after Validate Fix?
Validation runs over days, and the underlying window is still 28 days. Expect weeks for a full picture.
Does failing mean I will drop?
Page experience is a modest signal. It separates closely matched pages rather than overriding relevance.
Mobile or desktop first?
Mobile, almost always — harder to pass and where most visitors are.
Consulting CTA
For help interpreting what the report is telling you, book an SEO consultation. See also Core Web Vitals.