Search results and measurement
Chrome User Experience Report: meaning, examples and practical use
The Chrome User Experience Report, or CrUX, is Google’s public aggregate dataset of web performance observed during eligible Chrome users’ real visits. It can provide page- or origin-level experience metrics where enough qualifying data exists; it does not contain every visitor to every website.
Also known as: Chrome User Experience Report
At a glance
- CrUX contains real observations but not every visitor or URL.
- URL-level and origin-level results answer different questions.
- Missing data establishes neither a pass nor a failure.
On this page

Where do the observations come from?
The CrUX documentation describes aggregation from Chrome visits meeting defined eligibility requirements. This is field data, not a synthetic speed test run by Google on every URL. Aggregate access does not expose individual visitor journeys.
What is an origin?
An origin combines protocol, hostname and port. An origin-level result can summarize experiences across multiple pages. If a tool substitutes origin data when URL data is unavailable, that does not establish the exact performance of the individual article.
Example: a new glossary page
Imagine a recently published definition without enough public CrUX observations. Its publisher can test it in a lab and use their own measurement. The missing report does not mean the page failed, nor does it prove the page is perfect.
How should the time window be handled?
Check the period identified by the reporting interface. The field view in PageSpeed Insights summarizes earlier visits, so a fix made today becomes visible gradually. A fresh lab result and a rolling real-user aggregate should not be described as the same measurement.