Skip to content
CWV Checker

Why you're seeing "no field data"

Google only reports field data for sites with enough real visitors. Here's what that means, what it doesn't mean, and what to do instead.

This is the most confusing result in the whole field, and it is not an error

“No field data” means Google does not have enough real-visitor measurements for this page to report a number. It does not mean your site is broken, blocked, deindexed, or failing anything. It is the ordinary state of affairs for most of the web.

Where field data comes from

The Chrome UX Report is built from real Chrome users who have opted in to usage reporting. Google aggregates their measurements over a rolling 28-day window and publishes the 75th percentile — but only where the sample is big enough to be statistically meaningful and to stay anonymous.

There are two levels. URL-level data covers one specific page. Origin-level data covers your whole site averaged together. A URL needs far more traffic to qualify than an origin does, which is why a site can have origin data and no page data. When that happens, this checker uses the origin data and tells you it has done so, rather than silently presenting site-wide numbers as if they were about the page you tested.

What it means for you

  • Nothing is wrong. There is no penalty for missing data, and no signal is applied where there is no data to apply it from.
  • Your lab results are unaffected. They come from an actual test run against your actual page, and they are where the fix suggestions come from anyway.
  • You cannot make it appear faster. The only input is traffic. It will show up when enough people visit, and there is no setting, tag or plugin that changes that.

What to do instead

Trust the lab data for prioritising work

The lab test names specific files and gives you an estimated saving for each. That is directly actionable in a way a percentile never is. Start at the top of the list and work down — see the guides on LCP, layout shift and server response.

Collect your own field data

You do not need Google’s sample to measure real visitors — you can measure your own, from every browser, with no minimum traffic. The web-vitals library reports the same metrics from your own pages:

import { onLCP, onCLS, onINP } from "web-vitals";

const send = (metric) => navigator.sendBeacon(
  "/vitals",
  JSON.stringify({ name: metric.name, value: metric.value, id: metric.id })
);

onLCP(send); onCLS(send); onINP(send);

A few hundred visits is enough to see a distribution, and unlike CrUX it updates today rather than on a 28-day lag. Most analytics platforms will also collect these if you would rather not build the endpoint.

Check Search Console anyway

The Core Web Vitals report there groups similar URLs together, so it sometimes has something to say about pages that PageSpeed Insights reports as having no data.

One thing worth knowing about the 28-day window

When field data does appear, it lags. Ship a fix today and the reported number will keep moving for a month as the old measurements age out of the window. That is normal, and it is the reason to verify improvements with a lab test and your own real-user measurements rather than waiting on CrUX to confirm what you already did.

Common questions

How much traffic do I need before field data appears?
Google does not publish a threshold, and it is not a simple visitor count — the sample has to be large enough to report without identifying anyone, over a rolling 28-day window, from Chrome users who have opted in to reporting. In practice small sites often see origin-level data appear long before any individual URL does, and many perfectly healthy sites never get URL-level data at all.
Does having no field data hurt my rankings?
No. Google has said that where field data is missing it does not apply a Core Web Vitals signal at all, rather than assuming the worst. Missing data is neutral, not a penalty.
Why does my homepage have data but my product pages do not?
Because the threshold is per URL. Your homepage collects most of your traffic; a product page seen a few hundred times a month will not qualify on its own. When URL-level data is unavailable we fall back to origin-level data, which covers your whole site, and we label which one you are looking at.
Is the lab result still worth anything?
Yes — it is the only one of the two that tells you what to change. Field data tells you whether you have a problem; lab data tells you which file is causing it. For deciding what to fix on a Tuesday afternoon, lab data is the more useful of the two.

Check a page against this

Free, no signup, no ads. We keep nothing except the shareable result, for 30 days.

Enter any public URL. You’ll get the one change that recovers the most load time, what it’s worth, and the measurements underneath.

Other guides