Chrome UX Report

This feature is available only on the Essentials or Professional plan.

The Chrome User Experience Report (CrUX) is a public dataset provided by Google that collects real-world user performance data from millions of Chrome users. It measures how actual visitors experience websites across key metrics like Core Web Vitals, page load speed, and interactivity. CrUX provides aggregated, anonymous data for specific website origins, giving you a clear benchmark of how your site performs in the real world.

Request Metrics integrates with the Chrome UX Report and automatically adds comparisons for each Origin in your data. You can also add any public website for comparison, including your search competitors to make sure your site is the fastest.

Interactive Demo

Here’s an interactive demo that walks through how to use the Chrome UX Report integration.

The CrUX Dashboard Page

The CrUX Dashboard in Request Metrics allows you to view and compare real-world performance data from Google’s Chrome User Experience Report (CrUX). It automatically detects origins from your data and displays key performance metrics.

For your websites, use the Compare button to view a comparison with the live data from Request Metrics for up-to-the-minute performance.

The dashboard allows you to add additional origins from the public CrUX data, such as competitors or other benchmark sites, to compare performance metrics side by side.

Keep in mind that CrUX data is aggregated over the course of a month, meaning it offers a broad view of user experience but doesn’t provide real-time insights like Request Metrics’ RUM data.

Origin vs Website

A website in Request Metrics is a group of data that you monitor with a single token. A website allows your data to be aggregated and reported together, but we do not restrict how many domains can be combined.

For example, a website could include data from www.example.com, example.com, and my.example.com if you use the same token on all pages.

The Chrome User Experience Report uses a strict Origin to group data. An origin is a unique protocol, hostname, and port. Each of these is a separate origin:

• http://example.com
• https://example.com
• http://example.com:8000
• https://my.example.com

Google will measure the performance of each of these separately, and may give them different SEO ranking data based on the scores.

UX Metrics

The Chrome UX Report shows the following metrics:

• LCP (Largest Contentful Paint): the time until the largest element on the page is shown to the user.
• CLS (Cumulative Layout Shift): the amount of movement in the layout caused by lazy loaded components.
• INP (Interaction to Next Paint): the delay to user actions such as clicks and inputs.
• Time to First Byte: the time between the user’s navigation and the first response from the web server.
• First Contentful Paint: the time until the first element is show to the user.

The CrUX Report Details Page

The CrUX Origin Details Page provides a detailed breakdown of real-world performance data for a specific website origin, like https://requestmetrics.com. It showcases key performance metrics, comparing historical performance trends for both core and non-core web vitals.

Core vs Non-Core Metrics

At the top, you’ll see a focus on Google’s Core Web Vitals—Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and Interaction to Next Paint (INP). Each metric is displayed with a clear score, a trendline over time, and visual indicators for good, needs improvement, or poor performance.

Core metrics are SEO-impacting and directly influence the pagerank of an origin.

Below the core vitals, additional performance metrics are provided, such as Time to First Byte (TTFB) and First Contentful Paint (FCP). These metrics give you insight into the speed and responsiveness of your site, but aren’t specifically tied to the Core Web Vitals scoring.

Investigating Performance Issues

For any performance issues highlighted on the page, such as slow TTFB or spikes in INP, there are links to “Investigate Real-Time” where you can use Request Metrics’ real-time monitoring to troubleshoot and fix the problem quickly. This ensures that while CrUX provides the big picture, you have the tools to solve issues in the here and now.