Table of Contents
- Accessing the CrUX Report
What Is CrUX
CrUX data is collected by Google, and is accessible via the public CrUX API. This real-user data is from users on Chrome browsers who permit Google Chrome to collect and aggregate their anonymous browsing and performance data.
CrUX data is not collected by Blue Triangle, and is not a Blue Triangle product. This report is meant to give you a useful view of multiple origins’ CrUX data.
Each CrUX data stream is available on a URL-level basis, with a split between desktop and mobile devices, and reports on the 75th percentile of users to that URL. URLs without sufficient visits to report on the 75th percentile revert to the next highest level directory (e.g., https://www.example.com/home/category/product would revert to https://www.example.com/home/category or https://www.example.com/home depending on traffic levels.).
How Does CrUX Work
- Opted-in Chrome visits to a particular URL
- Either mobile or desktop
- Performance measurements at the 75th percentile
- The 28 days prior to the CrUX reporting date
Accessing the CrUX Report
This report is accessible through the left side navigation menu under 'Executive Reports'.
To begin setting up a CrUX report, click the 'Configure New Report' located on the CrUX page, if you do not already have a report configured:
Otherwise this button is available at the top of the page or through the Executive Reports Manager menu accessible by clicking on the wrench icon:
Example Executive Reports Manager:
The first page of the Configuration Menu requires you to input a report name and your desired lookback period, which is 7 days by default.
The second page of the configuration is for 'Sites & Pages'. This is where you decide the display name for the sites you include in the report as well as the page names. You can add up to 5 sites and 5 pages by using the plus or minus buttons.
The final page of the configuration is for the 'CrUX URLs'. For this example, we are only tracking the home page of these sites so only one URL is needed for each site. From here, click 'Save Configuration' to generate the report.
Again, CrUX does not include historical data, therefore as time goes on the report and the lookback data will become more and more robust.
You can toggle this report view between Mobile or Desktop and group by either page or site through the tabs at the top of the page.
Now, let's discuss each of the widgets that make up this report.
Overall CrUX Rank by Site
This is the Overall CrUX Rank by Site widget. The left side cards display the rank of the sites from Best to Worst for All Pages and All metrics. The right side card breaks down the rank by metric. The metrics included in this report are:
- First Input Delay (FID, CrUX data, Google Core Web Vital)
- Cumulative Layout Shift (CLS, CrUX data, Google Core Web Vital)
- Largest Contentful Paint (LCP, CrUX data, Google Core Web Vital)
- First Contentful Paint (FCP, CrUX data)
CrUX Site Ranks by Page
This is the CrUX Site Ranks by Page widget. For this example, we are only tracking the Home page, however if you included more pages there would be more tabs on the left side, including a view All Pages option. This widget breaks down the performance of each metric and ranks each site accordingly.
In the upper right you can toggle the view option to see the data in a table, or click the export button to get the data as a CSV, TSV, JSON or Array:
Bar Graphs by Metric
Below that, there are bar graphs displaying the data for each performance metric (First Input Delay, Cumulative Layout Shift, Largest Contentful Paint, and First Contentful Paint) by site. Using the right side hamburger menu, you can save this graph as a SVG, PNG, JPEG, or PDF.
Like the Site Ranks widget above, you can view these graphs as a table or export the data by using the buttons in the top right:
CrUX Data Trend
Lastly, we have the CrUX Data Trend widget. Again, this data is retrieved from Google's CrUX API, and not collected by Blue Triangle. Each data point in the graph represents the 75th percentile of performance over the previous 28 days. So the trend of this data is a rolling average (over the configured lookback period). The measured population is Chrome browser traffic for users who opted into data collection, and should be considered a subset of each URL's real user traffic. In this widget, you can select the Page and Metric to display using the dropdown menus above the graph.
Like the other widgets above, you can switch to a table view or export the data for further analysis.