Not enough real-user traffic for field data
What this check looks for
Chrome does not publish real-user performance data for ‹scope›. That almost always means the site does not get enough Chrome visits to reach the reporting threshold — it says nothing about whether the site is fast or slow.
Why it matters
Without field data, the only evidence about real-world speed is the lab measurement, which is one synthetic visit on one connection. Treat the lab numbers as a guide, not as what your visitors see.
What it costs your score
This check never deducts. It reports a fact — or reports that something could not be verified — and is shown on the report without moving the score.
- Severity
- info
- Default confidence
- confirmed
- Status when triggered
- info
- Deduction
- 0 points
- Family cap
- none
- Category
- Performance
- Module
- Perf crux
- Fix owned by
- user
- In the ruleset since
- 2026.09
Technical detail
The Chrome UX Report API answered for ‹scope› with no record. ‹detail›
CrUX only publishes a dataset once a page or origin has **enough real Chrome visits** to be statistically sound and to avoid identifying individual users, and the visitor must additionally be signed in to Chrome with usage statistics reporting enabled and sync turned on. So an absent dataset is overwhelmingly a traffic-volume fact, not a performance fact.
It can also happen for a page that is new, that is behind authentication, that is excluded by robots.txt-style crawl signals, or that redirects — CrUX keys on the URL after redirects, so a dataset may exist under a different URL than the one you entered. We ask for the specific URL first and then for the whole origin; both came back empty here.
**We do not score this.** Awarding a pass would be claiming the site is fast on the strength of no evidence, and failing it would penalise a site for not being popular. Neither is defensible.
Standards and references
Test this on your domain
Run the check that produces this finding, on its own, against any domain.
Other perf crux checks
- The page jumps around while it loads for real visitors
- Real visitors stare at a blank page for too long
- Real-user experience over the last 28 days
- The page is slow to respond when real visitors interact with it
- Real visitors wait too long for the main content to appear
- Real-user performance data was not requested
- Real-user performance data could not be retrieved
- The server takes too long to send the first byte to real visitors