No Core Web Vitals Field Data: What It Means and What to Do

What this check flags

This fires when PageSpeed Insights or Search Console has no CrUX field data for your URL, meaning too few real Chrome users have visited it to build a statistically valid sample. It's not an error and it doesn't hurt rankings on its own, but it does mean you're flying blind: you can't see the Core Web Vitals Google would actually rank with, so you're stuck reasoning from lab data alone.

Field data vs lab data, and why the gap matters

Two completely different measurements share the same metric names. Lab data comes from Lighthouse running one simulated load on a fixed device and network, deterministic and repeatable. Field data comes from CrUX, which is real Chrome users on real devices over the trailing 28 days, aggregated at the 75th percentile. Google's ranking signal uses field data, full stop. When a URL has no field data, it's usually because it hasn't crossed the CrUX traffic threshold, the sample is too small to publish. New pages, deep long-tail URLs, and low-traffic sites hit this constantly. The field vs lab data breakdown is worth a read if the distinction is fuzzy.

Origin fallback: the fix that isn't really a fix

When a specific URL has no field data, Google falls back to origin-level CrUX, the aggregate across your whole domain. That's why PSI sometimes shows an assessment for a brand-new page: it's borrowing your site's overall reputation, not measuring that page. This cuts both ways. A fast site lends a decent baseline to its new URLs, but a slow origin will paint a fresh, well-built page as failing before a single real visitor loads it. You can see which one you're getting: PSI labels it. If the field-data card reads "This URL" you have URL-level data; if it reads something closer to origin, you're on the fallback.

Reading which data you actually have

How to detect it

1. PageSpeed Insights. Run the URL. If you see "No Real-User Experience Data" or the tool jumps straight to the Lighthouse lab section with no field card, there's no CrUX for this page. Check whether the label says URL or origin, per the PageSpeed Insights reference.
2. CrUX Dashboard or BigQuery. Query the public CrUX dataset in BigQuery for your origin and URL. If the row doesn't exist, you've confirmed there genuinely is no sample, not a display quirk. This is the authoritative check.
3. Search Console. A URL with no field data simply won't appear in the Core Web Vitals report, since that report is built entirely from CrUX. Absence there is itself the signal, cross-check in Search Console.
4. RUM (Real User Monitoring). To get field-grade data before CrUX ever populates, drop in the open-source web-vitals JS library and log LCP, INP, and CLS from your own visitors to your analytics.

How to fix it

You can't force CrUX to publish, it's gated on traffic you don't control directly. What you can do:

1. Make the page fast on lab data anyway. A clean Lighthouse pass is the best proxy you have. Nail LCP, keep JavaScript light for INP, and reserve space for CLS, so that when field data does arrive it's already good.
2. Fix your origin baseline. Since new URLs inherit origin-level CrUX, a fast site-wide baseline means fresh pages start life passing instead of failing on the fallback.
3. Instrument your own RUM. The web-vitals library gives you per-page field data in days, not the weeks CrUX needs, and it works on pages CrUX will never cover.
4. Drive real traffic. Sometimes the honest answer is that the page just needs visitors. Once it clears the CrUX threshold, the data appears on its own.

What to do while you wait

The trap with a "no field data" page is treating it as broken and either ignoring it or over-engineering it. Neither is right. Set up RUM so you're measuring your own users from day one, get the lab score genuinely clean rather than gaming a single metric, and keep an eye on your origin-level CrUX because that's the number your fresh pages inherit until they earn their own. If the page matters commercially and you need field-grade proof of speed before CrUX ever populates, RUM is the only honest route, everything else is an estimate. And resist the urge to conclude the page is fine just because the lab score is green; lab data has never once bounced a request off a congested cell tower.

FAQ

Does "no field data" hurt my rankings?

No. The absence of data is neutral. Google falls back to origin-level CrUX or, failing that, doesn't apply a page-specific vitals signal. It's a visibility gap for you, not a penalty.

How much traffic does a URL need before CrUX shows up?

Google doesn't publish an exact number, and it's not a simple visit count, it's about having a large enough sample to be statistically meaningful over the 28-day window. Low-traffic pages can go indefinitely without ever appearing.

Should I trust the lab score if there's no field data?

Treat it as a well-informed estimate, not the verdict. Lab data is repeatable and great for catching regressions, but it runs on one device profile and won't capture the range of real users. Build to a clean lab score and verify with RUM.

Why does PSI show a passing assessment for a page I just published?

That's origin-level fallback. PSI is showing your domain's aggregate CrUX, not that specific page. It's borrowing the site's reputation until the page earns its own sample.