Real-user performance data was not requested
What this check looks for
We did not look up how real visitors experience this site, because this deployment has no Chrome UX Report API key. Nothing about your performance is being claimed here, good or bad.
Why it matters
This is a gap in our report, not a problem with your site. It is stated so that an empty performance section is never mistaken for a clean one.
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
- third party
- In the ruleset since
- 2026.09
Technical detail
The Chrome UX Report API requires an API key on every request (‹reason›). This deployment does not have one configured, so no query was made and no field data was retrieved.
Nothing follows from this about the site. In particular it is **not** the same as perf.crux.insufficient-data, which means we asked and Chrome has no dataset for this site. If you are running dotvitals yourself, set CRUX_API_KEY in the environment; the API is offered without charge at 150 queries per minute per Google Cloud project.
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
- Not enough real-user traffic for field data
- Real visitors wait too long for the main content to appear
- Real-user performance data could not be retrieved
- The server takes too long to send the first byte to real visitors