Page details
The CrUX Monitoring detail page shows the full weekly Chrome UX Report history of one tracked page or of the whole site.
The CrUX Monitoring detail page shows everything Google publishes about one tracked page, or about the whole site. Use it to see how a page moved over time and what slows it down.
Before you start
- To open the detail page, select CrUX Monitoring in the domain sidebar. Then click a row in the Pages card. See Pages.
- Everyone in the workspace can open the detail page. Only rows in the Google data tab open it.
The page header
The header of the CrUX Monitoring detail page shows:
- The breadcrumb: CrUX Monitoring > Page (or Whole site).
- The page address as the title. In privacy mode, the title is Page performance or Whole-site performance.
- The subtitle Google data from and the date of Google's newest data in the date range.
- An Old data chip if Google's newest data for the page is more than 60 days old.
- The Open in… menu. It opens the same page in other modules, for example RUM Monitoring or Synthetic Monitoring.
The date range
The filter bar of the CrUX Monitoring detail page has only the date range: Last 90 days, Last 6 months or Last 12 months. The default is Last 6 months. The date range changes the weekly history in the charts. Each weekly figure still covers Google's 28 days up to that week.
The verdict
The verdict at the top of the CrUX Monitoring detail page judges this page. It works like the verdict of the Overview, but it starts with This page. For example: This page does not pass Google's Core Web Vitals on Phone. Next to it, the verdict shows the LCP, INP and CLS of the device that is nearer to failing.
Hover the ? to see the result for Phone and Desktop and the good limit of each measure. If Google Search Console or Web Analytics measure the page, the ? also gives its traffic. For example: This page had 1,200 Google clicks and 3,400 Web Analytics views in this period.
Under the verdict, a banner shows the open CrUX issues from Site Health Monitoring. For example, a page fails Core Web Vitals or a measure slipped out of Good.
Core Web Vitals
The Core Web Vitals card of the CrUX Monitoring detail page has a tab for LCP, INP, CLS and TTFB. Each tab shows the latest Phone and Desktop figures. The chart shows one line for each device, week by week, over Google's Good, Needs improvement and Poor bands. If a measure stays well inside the good range, the chart ends at the good limit.
The chip at the top right, for example 64% Phone, is the share of this page's Chrome visits that come from phones.
Share of visits that are good
The Share of visits that are good card of the CrUX Monitoring detail page shows how the visits split across Google's three bands each week. It has a tab for LCP, INP, CLS and TTFB. Each tab shows a Phone chart and a Desktop chart.
Each chart stacks the share of Good, Needs improvement and Poor visits. A line marks 75%. Google passes a measure when 3 out of 4 page loads are good, so the Good share must stay above this line.
Google and your own visitors
The Google and your own visitors card of the CrUX Monitoring detail page puts Google's figures next to your own visitors. It has three columns:
| Column | What it shows |
|---|---|
| Measure | LCP, INP, CLS and TTFB. |
| Google's figure from Chrome visits only. It covers Google's 28 days up to the latest week in the date range. | |
| Your own visitors | The figure from RUM Monitoring for all your visitors. It always shows the last 28 days. |
The two can differ, because Google counts only Chrome visits. If RUM Monitoring is not installed, the card shows Compare Google's figure with your own visitors with Install the RUM script. If RUM has too few visits, it shows RUM Monitoring has no readings for this page yet.
If Google Search Console is not connected, the card also shows See how many Google clicks this page gets with Connect Google Search Console. After you connect it, the card shows the clicks that depend on the speed of the page.
What slows loading
The What slows loading card of the CrUX Monitoring detail page explains a slow LCP. Each tab shows only when Google publishes its data.
Where the time goes
The Where the time goes tab splits the load time of the main image into four phases, week by week, for Phone and Desktop. Use the picker to show All phases or one phase.
| Phase in the picker | What it means |
|---|---|
| Time to first byte | How fast your server sends the first part of the page. |
| Resource load delay | The gap before the browser starts to download the main image. A large gap often means that the image address is not in the first HTML. |
| Resource load duration | How long the download of the main image takes. File size and network speed change it. |
| Element render delay | The time between the end of the download and the image on screen. Scripts or CSS that block the page can cause it. |
Main content
The Main content tab shows what the largest element of the page is: an Image or Text. It shows the share of each type, week by week.
Server round-trip
The Server round-trip tab shows the round-trip time. This is the network delay for a signal to go from a browser to your server and back. This delay comes before your server sends any content.
Your visitors
The Your visitors card of the CrUX Monitoring detail page shows who visits the page. Each tab shows only when Google publishes its data.
- How visitors arrive: how Chrome loaded the page each week. The types are Navigate, Navigate Cache, Prerender, Back Forward (BF), BF Cache, Reload and Restore.
- Phone and Desktop: the share of Chrome visits that came from Phone and Desktop.
Ad load
The Ad load card shows only for pages with ad data from Google. It has an Experimental chip. Select one measure: Ads in view, Screen covered by ads, Ad CPU time or Ad data transferred. The chart shows the measure week by week for Phone and Desktop.
When the page shows no charts
| Message | Meaning and what to do |
|---|---|
| Fetching Google’s data… | VitalSentinel is asking Google for this page now. It usually takes a minute. |
| Google has no data for this page in this period (or for this site) | Google published data before the date range. The message gives the date. Click Show the last 12 months if it shows. |
| Google has no CrUX data for this page yet | Google has no data, because the page has too few Chrome visits. Use Open RUM Monitoring or Open Synthetic Monitoring instead. |
Troubleshooting
Why does a card or a tab not show on the page details?
The cards What slows loading, Your visitors and Ad load show a tab only when Google publishes that data for the page. If a tab is missing, Google has no data for it. Pages with fewer visits often have fewer breakdowns.
Why do Google and Your own visitors show different figures?
The Google column counts only Chrome visits over Google's 28 days. The Your own visitors column counts all your visitors in RUM Monitoring over the last 28 days. If they differ a lot, check which browsers and devices your visitors use.
Related
- CrUX Monitoring - what CrUX is and how Google judges a page
- Pages - add and remove tracked pages
- RUM Monitoring - the speed of all your own visitors
- LCP in RUM Monitoring - find the cause of a slow LCP
