Chrome UX Report: The Decisions That Matter
A public dataset of real-user performance measurements collected from Chrome users who have opted in, reported for origins and popular URLs.
Marcus Adeyemi
What is at stake
CrUX is the source of the field data shown in PageSpeed Insights and Search Console, so it is the closest thing to how Google sees your site's real performance.
The playbook
- Check origin-level data for an overall view
- Query the CrUX API for key URLs
- Track trends monthly rather than daily
- Compare mobile and desktop separately
- Use your own RUM for pages without CrUX data
Where it goes wrong
Avoid:
- Expecting data for low-traffic pages
- Reading a 28-day window as current performance
- Ignoring the difference between phone and desktop data
- Treating CrUX as a debugging tool
The numbers behind it
| Measure | Figure |
|---|---|
| Data source | Chrome users who have opted in to sharing usage statistics |
| Reporting window | a rolling 28-day period |
| Access | PageSpeed Insights, the CrUX API, CrUX Vis and BigQuery |
| Eligibility | pages and origins need enough traffic to appear |
Getting outside help
When to hand it over: Bring in help when a site lacks CrUX data, when trends worsen without an obvious cause, or when building performance dashboards.
Where this comes from
- Chrome for Developers — Chrome UX Report overview
- Chrome for Developers — CrUX API
The figures and practices above come from the sources listed.
Working on something like this?
We take on Performance & Accessibility work for teams who want it done once, properly. Tell us what you are building and we will tell you honestly whether we are the right studio for it. Start a project.
Where to go next
Spotted something wrong? Report an error on this page. We correct on the page and say what changed.
