The Chrome User Experience Report: aggregated real-world experience data from eligible Chrome users for qualifying pages and origins.
The Chrome User Experience Report, usually shortened to CrUX, provides aggregated field data about real-world Chrome browsing experiences. It differs from a one-off laboratory test: the observations come from eligible users and destinations rather than a single controlled run of your page.
Coverage is not universal. Google applies eligibility and sample requirements, so a small or recently published page may not have its own available data. Missing data does not mean the page is fast, slow or unused. Check whether a report refers to the specific page or a broader origin before drawing a conclusion about an individual URL.
Field data and laboratory diagnostics answer complementary questions. Field data can describe what a population experienced during a reporting window. A controlled test can help investigate a suspected cause or evaluate a code change before enough new field observations exist. Neither should be silently substituted for the other in a before-and-after claim.
Takeaway: Use CrUX to understand available real-user performance evidence, while stating the page or origin scope and reporting period. Pair it with diagnostics that can explain what to fix.
Example
A small company improves its contact page but finds only origin-level field data available. It reports that limitation, tests the page directly and waits for relevant later observations. It does not label the entire origin’s result as a measurement of the contact page alone.
What to check
Check the metric, device category, scope and collection window shown by the tool. Allow for the reporting period when interpreting recent changes, and avoid assuming the dataset represents every browser or every customer.
For more detail, see Chrome UX Report overview.