Chrome UX Report does not have sufficient real-world speed data

What’s actually happening

PageSpeed Insights skips the green 'Discover what your real users are experiencing' panel and jumps straight to the lab Lighthouse score. This is not a failure or a penalty — it means Chrome collected too few real visits to publish a privacy-safe aggregate for this URL. New pages, low-traffic pages, internal pages, and anything noindex'd or behind auth routinely sit below the cutoff. You still get a full lab report; you just have no field numbers to compare it against.

Common causes

• The page is new or low-traffic and hasn't accumulated enough opted-in Chrome visits to clear CrUX's anonymity threshold
• CrUX only counts Chrome users who opt into usage statistics and browse the public page, so a real but small audience can still fall short
• The page is noindex'd, behind a login, or otherwise rarely loaded by everyday Chrome traffic
• You queried a specific URL that's thin on data even though the broader origin has plenty — URL-level data needs more samples than origin-level
• The site's audience skews to browsers CrUX doesn't measure (Safari, Firefox), shrinking the eligible sample

How to fix it

1. Fall back to origin-level dataIn the PageSpeed UI switch from the URL to the origin, or in the CrUX API request `"origin": "https://yoursite.com"` instead of `"url"`. The whole-site aggregate clears the threshold far more often than a single quiet page.
2. Trust the lab score in the meantimeThe Lighthouse section is still fully valid for finding and fixing problems. Optimize LCP, CLS, and INP against the lab run; field data will start to populate on its own once enough real Chrome users hit the page.
3. Drive real traffic, then wait for the windowCrUX reports a rolling 28-day window. Get the page indexed, linked, and visited, then re-check after a few weeks — there is no way to force data in faster, and no amount of re-running PageSpeed creates samples.
4. Query CrUX directly to see how close you areHit the CrUX API or the BigQuery dataset for both the URL and the origin. If the origin returns data but the URL doesn't, you've confirmed it's purely a sample-size gap, not a tracking or setup problem.