Sebastian Gomez

Jun 24, 2026

Updated: Jun 25, 2026

The complete guide to the CrUX Dashboard: what it was, how to use it, and why to migrate to CrUX Vis

If you work in SEO, web development, or digital marketing, you know that understanding how real users experience a site is essential. Core Web Vitals have become the gold standard for measuring that experience, and for years one of the most accessible tools for visualizing that data was the CrUX Dashboard.

This panel, built on Looker Studio (formerly Data Studio), let anyone access Chrome UX Report (CrUX) data without writing a single line of SQL. Its time, however, has already come to an end, so let's look at what it was, how it worked, and how to make the jump to its replacement.

Historical note: the CrUX Dashboard was retired

The Chrome team announced that the CrUX Dashboard would be retired, and so it was, after November 2025. The official recommendation was to migrate to its successor, CrUX Vis, a faster, more modern tool with more features.

In this guide we review everything worth knowing about the CrUX Dashboard: what it was, how it worked, and most importantly, how to make the transition to its replacement today.

What the CrUX Dashboard was

The CrUX Dashboard was an interactive panel that connected directly to the raw, origin level data of the CrUX report in BigQuery. Its main advantage was simplicity:

• No SQL queries: it removed the technical barrier of BigQuery.
• Automatic visualization: it generated charts and tables automatically.
• Easy to use: you only needed to enter the origin (domain) of a website to get a complete report.

You just entered a URL like https://developers.google.com and the panel was generated instantly, ready to analyze, share, or bookmark.

### Did it work for every website?

No. Only sites with enough traffic to be included in the CrUX dataset (which contains more than 15 million origins) showed data. Common mistakes like using http:// instead of https://, or not including the correct subdomain (www.), could prevent the data from being found.

A tour of the CrUX Dashboard

Every report generated in the panel was organized into three types of pages, with data updated on the second Tuesday of each month.

1. Core Web Vitals overview

The main page offered a general view of the monthly performance of Core Web Vitals: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). There you could filter by month and quickly see the overall health of your site for desktop and mobile users.

2. Detailed performance by metric

Each individual metric had its own page. The main visualization was a stacked bar chart that showed the monthly distribution of experiences categorized as "Good", "Needs improvement", and "Poor". It also highlighted:

• The percentages for the most recent month.
• The percentage difference compared to the previous month.
• The 75th percentile (P75) value, which indicates that 75% of user experiences are better than that value.

Technical note on the percentiles: it was important to know that these percentiles had limited granularity (for example, 100 ms for LCP) because of how the data is stored in BigQuery, unlike the millisecond level precision of tools like PageSpeed Insights.

3. User demographics

This section showed the distribution of page visits across two dimensions:

• Devices: the breakdown of users between mobile, desktop, and tablet.
• Effective Connection Types (ECT): a distribution of 4G, 3G, 2G, and similar connections, based on measured bandwidth rather than network technology.

The future is here: the deprecation of the CrUX Dashboard

Although it was a very useful tool, the CrUX Dashboard had scalability problems. It suffered frequent outages, especially on data update days, due to high demand. That's why the Chrome team decided to build a better solution.

### Why was it discontinued?

The infrastructure it was built on was not ready for massive use and its maintenance became unsustainable. In its place, more robust and reliable alternatives were developed.

The superior alternative: CrUX Vis and the CrUX History API

In 2023 the CrUX History API launched, a real time API that is faster and more scalable. On that foundation, CrUX Vis was born in 2024, the new official tool. Its advantages over the old panel are clear:

• Weekly updates: instead of monthly data, you get data updated every week.
• Fast load times: it is much snappier and does not suffer the outages of the old panel.
• URL level data: beyond origin data, you can query data for specific URLs, as long as they have enough traffic.
• More scalable: built on modern, reliable technology.

According to the Chrome team, since its launch CrUX Vis adoption has far surpassed that of the old panel, with several times as many users.

For advanced users: how to keep using the dashboard format

If for some reason you need to keep using the old panel format, it is still possible, but with an important caveat: you will have to connect it to your own BigQuery project, it is no longer maintained by the Chrome team, and you could incur costs.

Let's walk through the steps to set up your own copy.

Set up a BigQuery project

1. Create a Google Cloud account and a new project.
2. Optionally, set up billing. As of publication, BigQuery offers a free tier of 1 TB of queries per month. Each load of the panel consumes roughly 13 GB, which would give you about 80 free loads (1 TB / 13 GB is close to 80). It's worth confirming these figures in the Google Cloud documentation, since quotas and pricing can change.

Create a data source in Looker Studio

1. In Looker Studio, create a new data source and select BigQuery.
2. Choose CUSTOM QUERY and enter your billing project ID. Paste the following SQL query:

SELECT * EXCEPT (date, yyyymm)
FROM
  `chrome-ux-report.materialized.device_summary`
WHERE
  origin = COALESCE(NULLIF(@origin, ''), 'developer.chrome.com') OR
  origin = 'https://' || COALESCE(NULLIF(@origin, ''), 'developer.chrome.com')
ORDER BY date DESC
LIMIT 40

1. Add a parameter named origin (ID: origin, Type: Text).
2. Connect the data source and set the numeric field types to Numeric, Percent, except for the p75_, rank, and Record Count fields.

Copy and reconfigure the dashboard

1. Open the latest version of the CrUX Dashboard and make a copy.
2. In the copy dialog, assign your new BigQuery data source to the existing data sources.
3. Once copied, go to Resource, Manage variables (parameters), edit the origin parameter to remove the prefix (for example ds117.), and check the "Allow to be modified in reports URL" box.

With that you'll have your own working version of the panel. Remember that every time someone views it, it will consume quota from your BigQuery project.

Frequently asked questions (FAQ)

Q: Will the CrUX dataset in BigQuery also be discontinued?

A: No. The Chrome team plans to keep updating and maintaining the public dataset in BigQuery for long term analysis.

Q: Why not simply keep the free connector?

A: The infrastructure behind the connector was unreliable and required constant maintenance. The new solutions, like the CrUX History API and CrUX Vis, are much more stable and designed for large scale use.

Q: What were the limitations of the CrUX Dashboard?

A: It was restricted to origin level data, with monthly granularity and only at a global level, whereas in BigQuery you can filter data by country.

Suggested exercises

1. Open CrUX Vis and enter the origin of a site with good traffic (your own, for example). Compare the P75 values of LCP, INP, and CLS between desktop and mobile.
2. Query the URL level data for a specific page of that site and compare it with the origin level data. Note the differences you find.
3. If you're up for some BigQuery, set up your own copy of the panel following the steps in this guide and run the SQL query against the origin you want to analyze.

3-point summary

1. The CrUX Dashboard was retired after November 2025; its official successor is CrUX Vis, built on the CrUX History API.
2. CrUX Vis is faster and more scalable, offers weekly updates, and lets you query URL level data, not just origin level.
3. If you need the old format, you can recreate it with your own BigQuery project and Looker Studio, taking on the maintenance and possible quota costs.

Verify before migrating: the official link for the tool as of publication is https://cruxvis.withgoogle.com/. Confirm the domain is still live, since Google sometimes consolidates these tools under developer.chrome.com.

That's all. I hope this post is useful to you and helps you leave the old panel behind to start exploring what its successor can do, which is an improvement in every sense: faster, more up to date, and with more data.

Leave me a comment if it helped, if you want to add an opinion, or if you have any questions. And remember, if you liked it, you can also share it using the social links below. Good luck with the migration!