Chrome User Experience Report
A public dataset of real-world performance metrics collected from Chrome users, used to measure how sites are experienced in the field.
Definition
The Chrome User Experience Report (CrUX) is a public dataset that records how real-world Chrome users experience popular destinations on the web. It is the official source of field data for Google's Web Vitals programme.
CrUX aggregates anonymised performance measurements from Chrome users who have opted in, organised by dimensions such as device type and country. Not every origin or page appears in the dataset, because a site must be publicly discoverable and receive enough traffic to produce statistically significant results. The data can be accessed through PageSpeed Insights, the CrUX API and History API, and BigQuery, and it informs the field data used in Google's page experience signals.
Examples
Field data source
When PageSpeed Insights shows a 28-day Largest Contentful Paint distribution for a URL, that field data is drawn from the Chrome User Experience Report.
Large-scale analysis
An analyst queries the CrUX BigQuery dataset to compare Core Web Vitals across thousands of origins in a sector.
Sources
Related terms
- Core Web VitalsA set of three Google metrics that measure real-world page experience: loading speed, interactivity and visual stability.
- PageSpeed InsightsA Google tool that reports a web page's performance on mobile and desktop using both real-user field data and simulated lab data.
- Page ExperienceGoogle's umbrella term for signals describing how users perceive a page — Core Web Vitals, HTTPS, mobile usability, and absence of intrusive interstitials.
- Largest Contentful PaintA Core Web Vitals metric measuring how long the largest visible content element on a page takes to render after loading begins.
- Interaction to Next PaintA Core Web Vitals metric measuring how long a page takes to visually respond to a user interaction, sampled across the page's lifetime.
- Cumulative Layout ShiftA Core Web Vitals metric measuring how much visible content unexpectedly shifts position during the lifetime of a page.
Where QueryCatch uses this
Last updated: 16/05/2026