Performance glossaryThe Chrome UX Report (CrUX) is Google's public dataset of how real Chrome users experience websites, including their Core Web Vitals. PageSpeed Insights shows it as field data.
The Chrome UX Report, usually called CrUX, is the dataset behind most of the real-user performance numbers Google shows. Chrome collects anonymized timings from page loads by eligible users, Google aggregates them by site and by page, and the results are published for anyone to use. It is field data, from real visits on real devices and connections, unlike the lab data of a Lighthouse test run on one simulated device.
Where the data comes from
CrUX includes Chrome users on desktop and Android who have opted in to syncing their browsing history and sending usage statistics. Chrome on iOS is not included, and neither are other browsers. Pages and sites only appear if they are publicly discoverable and get enough traffic, so smaller sites may have data for the whole origin but not for individual URLs, or no data at all.
What it measures
- The three Core Web Vitals: Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift.
- Diagnostic metrics such as First Contentful Paint and Time to First Byte.
- Breakdowns by device type (phone, desktop, and tablet) and, in some sources, by country and connection type.
Each metric is reported as a distribution: the share of experiences rated good, needs improvement, and poor. Google assesses a page at the 75th percentile, so a metric passes when at least 75 percent of visits meet the "good" threshold.
How to access CrUX data
- PageSpeed Insights shows CrUX data for a URL and its origin at the top of each report, covering the previous 28 days.
- Google Search Console builds its Core Web Vitals report on CrUX data, grouping similar URLs across the site.
- The CrUX API returns the same 28-day data for any origin or URL, and the CrUX History API returns weekly trends.
- BigQuery holds the full public dataset, updated monthly, for querying many origins at once or comparing competitors.
Why it matters
CrUX is how Google sees a site's page experience: the Core Web Vitals used in Search come from this field data, not from lab scores. That has two practical consequences. A fix shows up gradually, as the 28-day window rolls forward, not on the day it ships. And a perfect lab score does not guarantee passing field data, because real visitors use slower phones and networks and interact with pages in ways a lab test does not.
Sites without enough traffic to appear in CrUX can collect the same metrics from their own visitors with real user monitoring, for example with Google's open-source web-vitals JavaScript library.
Source: Chrome UX Report documentation.