Core Web Vitals are a set of key user experience metrics that directly influence how your site ranks. The report in Google Search Console is based only on real‑user data, which is why the section can stay empty for a long time even if you have green scores in PageSpeed Insights after optimisation.
How Core Web Vitals appear in Google Search Console
The Core Web Vitals report in Search Console is built exclusively from field data collected from real users — the Chrome User Experience Report (CrUX). In practice this means Google looks at people who visit your pages in Chrome and have not disabled anonymous usage statistics.
The data is aggregated over the last ~28 days and the system uses the 75th percentile: if 75% of visits fall into the green zone for LCP, CLS and INP, the page is considered “good”. Separate samples are built for mobile and desktop traffic, so one device type may already have a report while the other still shows “no data”.
For metrics to appear at all, your site must:
- receive a sufficient volume of traffic to be included in the CrUX sample;
- be public and indexable (not blocked in
robots.txtand withoutnoindexon key pages); - run over HTTPS and not have blocking technical issues;
- have an audience in Chrome that has not disabled telemetry.
If one of these conditions is not met, the system may fail to gather a representative sample and simply choose not to show data, instead of presenting noisy or misleading metrics.
Why the report shows “no data”
In real projects Search Console most often shows “Not enough data” in two cases: when the site or property in GSC is new or when the project simply has too little field data to compute metrics.
For new sites a typical scenario is that 28 days just haven’t passed since the first visits were recorded, so the system hasn’t had time to accumulate a full sample. For low‑traffic projects the problem is different: traffic volume is small and visits are uneven, which makes the sample noisy and unstable, so Google prefers not to show a report at all.
Additional factors that may keep the report empty:
- most of your audience doesn’t use Chrome or has disabled telemetry;
- a portion of traffic goes to subdomains, test environments or mirrors that are not part of the current GSC property;
- some pages are blocked from indexation or suffer from restrictive
robots.txtrules; - there is not enough data for one device category only — for example, desktop data is too scarce while mobile traffic is sufficient.
Example: why the report shows “no data”
How to read this:
- in the first weeks traffic is low — bars are below the threshold line, so the report shows “not enough data”;
- as visitation grows, the sample becomes more stable and the system starts computing metrics;
- the report covers ~28 days, so even when traffic increases you still need to wait until the window fills with fresh data.
In such cases site owners see messages like “Chrome User Experience Report does not have sufficient real‑world speed data for this page” — a direct hint that the issue is not the metrics themselves but the volume and quality of traffic.
How to speed up the appearance of Core Web Vitals
Because the report is based on field data, the only legitimate way to speed up the appearance of metrics is to drive more real users. The more visits you get, the faster CrUX builds a sample and the more stable the metrics look.
Practical steps:
Make sure the site is open for crawling and indexation, with no technical blocks or errors that prevent crawlers from reaching pages.
Remove unneeded staging and test environments from the index so you don’t dilute traffic across multiple versions.
Plan campaigns that bring real, targeted traffic (SEO, paid search, social ads) — especially from Chrome users.
Keep improving performance so that new visits land in the green zone for CWV from day one.
It is important to understand that you cannot manually upload or push CWV metrics to Google — not via API, not via any interface. The system updates data as statistics accumulate and, in practice, a full refresh cycle can take up to 28 days. Even if you fix everything today, the report in Search Console may lag behind reality for several weeks.
What to do while you wait for data
The fact that Search Console shows no data does not mean you can pause optimisation. On the contrary, this is the period when you want to push performance and UX as far as you can, so that once field metrics appear they start out in the green zone.
During this time, focus on laboratory tools such as PageSpeed Insights, Lighthouse and WebPageTest. They show how a page behaves under controlled conditions and highlight bottlenecks that hurt Core Web Vitals.
A useful guideline comes from Google’s Martin Splitt: if you have fixed issues and lab tools show good results, there is no need to panic — you’ve done your part, now the system just needs time to collect data.
To display Core Web Vitals in the report, Google needs enough recent real‑user statistics. That depends on traffic volume, the share of Chrome users, their telemetry settings and the public accessibility of your site. If the project is brand‑new or has very little traffic, or if only a short time has passed since launch or a major release, the report will remain empty.
Your job at this stage is to ensure a stable flow of real users and keep improving speed and usability. Once the site passes the popularity threshold in CrUX and a few update cycles run their course, Google Search Console will start showing Core Web Vitals that reflect actual user experience.
Tags: