dotvitals

Loading the list of pages…

↑↓ to moveEnter to openEsc to close

No real-user field data was published for this site

Updated

InfoConfirmedperf.crux.insufficient-data

What this check looks for

Chrome publishes no real-user performance data for this site. Google does not say why, so the absence says nothing about whether the site is fast or slow.

In a report, this finding reads as follows, with each ‹…› filled in from what that scan observed:

Chrome does not publish real-user performance data for ‹scope›. Google does not say why, so this says nothing about whether the site is fast or slow — and nothing certain about how many visitors it has either.

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

How the whole score is calculated

Technical detail

The Chrome UX Report API answered for ‹scope› with no record. ‹detail›

**Google does not publish a reason, so neither do we.** There are several, and this report cannot tell them apart:

  • **Too few visits.** 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 only visits by users signed in to Chrome with usage statistics reporting enabled and sync turned on are counted. This is the most common reason, and for a site with little traffic it is very likely the one.
  • **The key.** CrUX records the exact address, after redirects. A site whose visitors all land on www has no record under the bare name, and the reverse. We ask about the address you entered, its origin, the address this scan was redirected to, and — where this site would not show the scan its page — the www form of each.
  • **The page.** A page that is new, behind authentication, or served only to some visitors may never accumulate a dataset even on a busy site.

For a site you know to be busy, the second reason is worth checking before the first: compare the exact address in this report against the one your visitors use.

**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.

Open the perf crux checker