Analytics and Tracking

Core Web Vitals Report

Also called CWV report

Search Console's grading of real Chrome visits for loading, responsiveness and layout stability, grouped into sets of similar URLs.

Quick facts: Core Web Vitals Report

Category
Analytics and Tracking
Also called
CWV report
Level
Intermediate
Affects
Page experience, mobile usability, visitor drop-off
Where to see it
Google Search Console (Core Web Vitals), PageSpeed Insights, Chrome UX Report
In this article4
  1. What the Core Web Vitals report measures
  2. Why the Core Web Vitals report matters
  3. Where the Core Web Vitals report goes wrong
  4. How to act on it

What the Core Web Vitals report measures

The report grades your pages on the experience real Chrome users had, not on a test run in a laboratory. It draws on data collected from people who visited your site with reporting enabled, covering the three Core Web Vitals: how quickly the main content appears, how promptly the page responds when someone interacts with it, and how much the layout shifts while it loads.

Two things about the presentation catch people out. Mobile and desktop are reported separately, because they are genuinely different experiences. And URLs are not listed individually; Google clusters addresses that behave alike — usually pages sharing a template — and grades the group. Each group is labelled good, needs improvement, or poor, against thresholds Google publishes for each metric.

Why the Core Web Vitals report matters

It is the closest thing you have to what your visitors actually endure. Testing your own site from a fast office connection on a recent phone flatters it. The people this report measures may be on an older Android device on a mobile connection, which is the majority experience in Nepal and in plenty of the markets my clients sell into.

The grouping is also useful rather than annoying, once you see the point of it. If a group of product pages is poor, the fault is almost always in the template they share, and one fix moves every URL inside it. Chasing individual pages when the report is speaking about templates wastes a lot of effort.

Where the Core Web Vitals report goes wrong

The most frequent confusion is between this report and a speed testing tool. A lab test simulates one visit on one simulated device; this reflects many real visits on real hardware over a recent window. They disagree constantly, and when they do, the field data is the one that describes your customers.

The second is impatience. Because the report reads a rolling window of recent visits, a deployment does not show up the next morning. Improvements appear gradually as older visits age out, which means judging a fix too early makes it look useless.

The third is assuming silence is health. A page with too few visits to measure will not be graded at all. Absence from the report is not a pass; it usually means the page has little traffic.

How to act on it

Start with mobile, since that is where most problems and most visitors are. Take the worst group, open the example URLs, and identify the template behind them. Diagnose with a lab tool if you like, because it points at causes, but confirm success here, because only this reflects reality.

Fix causes rather than symptoms: heavy images and fonts, scripts that block rendering, and elements inserted after load that push content down the screen. Once a group is fixed, use the validation option so Google re-checks it, then wait for the field data to catch up. Sustained work of this kind belongs with wider page speed optimisation rather than a one-off cleanup.

Do and do not

Do

  • Read the mobile tab before the desktop tab
  • Treat each URL group as a template to fix
  • Confirm improvements with field data, not lab scores

Do not

  • Expect the report to move straight after a deployment
  • Read an ungraded page as a healthy one
  • Optimise for a lab score alone

Questions people ask about this

Why does PageSpeed Insights disagree with the Core Web Vitals report?

Because one is a simulation and the other is a record. A lab test loads your page once on a modelled device and connection, which is repeatable and good for finding causes. The report reflects visits by real people on their own phones and networks. When the two disagree, trust the field data for judging the problem's size.

My pages are missing from the report. Is that good?

Not necessarily. Grading needs enough real visits to be meaningful, so pages with light traffic are left out entirely. Being absent tells you nothing about how fast those pages are. If you want an indication for a low-traffic page, run a lab test and compare it with a similar page that does appear in the report.

How long after a fix should the report improve?

Longer than most people expect. The data covers a rolling window of recent visits, so an improvement dilutes into the figures gradually as older visits age out. Deploy the fix, use the validation option so Google re-checks the group, and give it enough time before deciding the work failed. Lab tests confirm the change itself immediately.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.