The CrUX dataset is made available through a variety of tools maintained by Google. Each tool may access CrUX data slightly differently, resulting in varying levels of timeliness and metric support.
| Tool | Frequency | Metrics | Dimensions | Historical Data | Origin / Page-level |
|---|---|---|---|---|---|
| CrUX on BigQuery | Monthly 1 | All metrics | All dimensions | Since 2017 5 | Origin |
| CrUX Dashboard | Monthly 1 | All metrics | No country dimension | Since 2017 5 | Origin |
| CrUX API | 28-day average 2 | Subset of key metrics 4 | sNo effective connection type or country dimension | No | Origin & Page |
| CrUX History API | Weekly 3 | Subset of key metrics 4 | No effective connection type or country dimension | Previous 25 weeks | Origin & Page |
| PageSpeed Insights | 28-day average 2 | Subset of key metrics 4 | No effective connection type or country dimensions | No | Origin & Page |
| PageSpeed Insights API | 28-day average 2 | Subset of key metrics 4 | No effective connection type or country dimensions | No | Origin & Page |
| Google Search Console | 28-day average 2 | Core web vitals | No dimensions | Three months | Page Group 6 |
1 Monthly data is released on the second Tuesday after each monthly collection period. The last 28 days of each month period are included.
2 28-day rolling average data is updated daily, based on the aggregated data from the previous 28 days.
3 Weekly historical data is released every Monday, containing the 25 most recent 28 day collection periods that end on Saturdays.
4 The web vital metrics are available in all tools.
5 Not all metrics are available in all monthly tables, see the release notes for details.
6 Search Console groups URLs that provide similar experiences, Core Web Vitals data are shown aggregated by these page groups.
The following sections briefly summarize each tool and how the data can be used.
CrUX on BigQuery
Origin-level CrUX data is available for public querying via BigQuery.
Chrome UX on BigQuery provides a publicly accessible database of all origin-level data collected by CrUX. It is possible to query any and all origins for which data is collected, analyze any metric that CrUX supports and filter by all available dimensions. Full metric histograms are stored in the BigQuery tables allowing for visualization of performance distributions, including experimental metrics.
The data in BigQuery is updated monthly, with each month's data released on the second Tuesday after the collection period. Page-level data is not available in BigQuery tables, and percentiles are interpreted from coarse histogram data which results in approximate values.
Use CrUX on BigQuery for analysis across any dimension: origins, countries, dates, form factor and connection type. Read more about CrUX on BigQuery.
CrUX Dashboard
The CrUX Dashboard is a Looker Studio dashboard that allows you to query and render CrUX data into an interactive dashboard, as well as exporting PDF reports.
The dashboard provides visualization of all CrUX metrics in monthly trends, with data available back to 2017. Data can be split by form factor to compare mobile / tablet / desktop performance and performance goals are available to create red-amber-green visualizations. Effective connection type can be shown as a distribution.
The CrUX Dashboard does not support the country dimension, so all global data is presented in the reports. Page-level data is not available and percentile values are calculated from coarse histogram data so are approximate.
CrUX API
The CrUX API provides programmatic access to CrUX data by page or origin, and can be further filtered by form factor and metrics.
The API provides Web Vitals metrics both by origin and at page-level and the data is updated daily. The only values provided for metrics are calculated from the previous 28 days as a rolling window. Historical data is available via the separate History API.
The CrUX API returns more quickly than the PageSpeed Insights API but does not include the additional Lighthouse data provided by PageSpeed Insights.
Read more in the API documentation.
CrUX History API
The CrUX History API provides programmatic access to CrUX historical data by page or origin, and can be further filtered by form factor and metrics.
The API provides Web Vitals metrics both by origin and at page-level and the data is updated weekly. The only values provided for metrics are calculated from the past 25 weekly collection periods of 28 days as a rolling window.
Read more in the History API documentation.
PageSpeed Insights
PageSpeed Insights uses CrUX to present real-user performance data alongside performance opportunities powered by Lighthouse.
The PageSpeed Insights report presents a consolidated view of the Core Web Vitals for the given URL or origin, plus additional diagnostic metrics. Data is presented by desktop and mobile form factors and can be compared with the lab test results to give a better understanding of your page performance.
PageSpeed Insights does not provide historical data, and does not include country or effective connection type dimensions.
PageSpeed Insights API
The PageSpeed Insights API offers programmatic access to the data shown in PageSpeed Insights, including Core Web Vitals data from CrUX.
This API integrates well into existing SEO tooling and workflows, allowing CrUX data to be included in automated reports and analyses. The PageSpeed Insights API returns slower than the CrUX API, but includes additional data provided by Lighthouse.
As in the web version, the PageSpeed Insights API has no historical data and is limited to the Core Web Vitals. Country and effective connection type dimensions are not included.
Search Console
Search Console shows how CrUX data influences the page experience ranking factor by URL and URL group.
Search Console presents Core Web Vitals values as aggregates of groups of similar pages. This provides a quick indication of which sections of a site are potentially impacting the page experience ranking factor.
Data is updated daily and is split by mobile and desktop form factors. A maximum sample of 20 pages per group are presented for further analysis.