dotvitals

Real-user performance data could not be retrieved

InfoConfirmedperf.crux.query-failed

What this check looks for

The Chrome UX Report API did not answer our request, so we have no real-user data to show. This is a failure on our side or Google's, not on yours.

Why it matters

It is reported rather than hidden so that a missing performance section is visibly a missing measurement, and not read as everything being fine.

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

How the whole score is calculated

Technical detail

The query for ‹scope› failed: ‹reason›. ‹detail›

The common causes, all of which are ours to fix rather than yours:

  • **Quota** — the CrUX API is limited to 150 queries per minute per Google Cloud project, shared across every scan this deployment runs. A burst of scans exhausts it and the API answers 429. We cache field data per URL and per origin specifically to keep well inside that limit.
  • **An unreadable answer** — the API returned something that did not match the documented response shape. We report that rather than guess at what it meant.
  • **A transport failure or timeout** reaching chromeuxreport.googleapis.com.

Retrying the scan in a minute or two usually clears a quota refusal. Nothing about the site's performance is asserted either way.

Standards and references

Test this on your domain

Run the check that produces this finding, on its own, against any domain.

Open the perf crux checker

Other perf crux checks