Chrome User Experience report

CrUX stands for Chrome User Experience report. It provides data on experience of real users for how real-world Chrome users experience popular destinations on the web. This database of data is also feeding:

Limitations of CrUX data

There are limitations to what becomes part of CrUX. These limitations aren't commonly known, despite being published at

Google Chrome only
CrUX and Google Chrome being part of the Google ecosystem, only pageviews via the Google Chrome browser will become part of CrUX and Core Web Vitals. Do note that Google Chrome on iOS is not considered a real Google Chrome here, meaning iOS users are automatically excluded, just like FireFox, Edge, Opera experiences.

Logged in users
Users that are logged into Google services with their browser will automatically be logged into the browser itself as well. Only those experiences of users that have usage statistic reporting enabled will become part of the CrUX dataset.

Only publicly discoverable pages could be included in the CrUX dataset.
This means that pages need to have the same indexability criteria as search engines. It should return a 200 HTTP status code and should not have a robots setting that is preventing the page from being indexed.

Sufficient amount of pageviews
Pages should receive a sufficient amount of pageviews. If they do not, its pagehits might become part of origin data, but likely won't get page-level data. As of around 300 pagehits per month per device with the above conditions will give your pages a chances of individually collecting data and getting its own Core Web Vitals data.

When either of the above will change, pages and origins will be automatically included or removed from the dataset over time.

Who can use CrUX API's?

The CrUX API is exposing CrUX data in fixed ways to give low-latency access to aggregated data of real-user experiences at page and origin granularity. Google is offering multiple API's around their CrUX data.

Getting started with these API's is free of cost (to a certain usage). However, similar to building on top of Google Maps, users will need to re-use or generate a Google API key to be able to communicate with these API's. Meaning a developer is required here to make it work.

There are tools out there that are taking away such hassle and are publicly available. Our free tools are an example here:

An example of visualization that one can achieve with the data from the historic CrUX API is illustrated in the screenshot below, based on mobile origin data from

Get your website's data with our free tool

Continue reading about CrUX

Continue reading over at Google pages to learn more about CrUX and CrUX API's: