Page Views
The Page Views page of RUM Monitoring lists each real visit with its speed numbers, and opens one visit with its timeline, metrics, files and environment.
The Page Views page of RUM Monitoring lists each real visit with its five speed numbers. Open one visit to see in detail what loaded, how long it took and what the visitor used.
When to use the Page Views page
The other RUM Monitoring pages show totals and typical values. The Page Views page shows single visits. Use it to look at one slow visit in detail, for example after a visitor complained. You can also use it to check a page right after a release.
Before you start
- RUM Monitoring needs the RUM script on your pages. See Install the RUM script.
- In the sidebar, open Web performance > RUM Monitoring > Page Views.
- Select Phone or Desktop in the filter dock. The list shows the visits of the selected device only.
Filters on the Page Views page
The Page Views page has these controls in the filter dock:
- Date range and Device. The Page Views page has no compare, because it lists single visits.
- URL Path, Country, Browser and Operating system filters.
- With an LCP: shows only visits that measured LCP.
- Slow only: shows only visits with at least one Poor metric.
For how the filter dock works, see Using the app.
The Visits list
The Visits card lists the visits, newest first. It shows 50 visits on each page of results.
| Column | What it shows |
|---|---|
| When | The date and time of the visit |
| Page | The page address, without its query string |
| LCP, INP, CLS, FCP, TTFB | The value of each metric in this visit |
Each metric value has the color of its band: green for Good, orange for Needs improvement and red for Poor. A dash means that the visit did not measure that metric. For example, a visit without a tap or click has no INP. On a narrow screen, the list hides some metric columns.
Hover the "i" next to a page to see the visitor: Country, Device, Browser and Operating system.
Sort by the slowest LCP
Click the LCP header to show the slowest LCP first. Visits without an LCP come last. Click the header again to go back to the newest visits first.
Open a visit
Click a row to open the visit in a side panel. The header shows the page address and a link that opens the page in a new tab. Below it, you see the device, "Visited on" with the date and time, and the country.
Use the arrows in the header to move to the next or the previous visit in the list. The side panel has up to five tabs: Summary, Metrics, Waterfall, Environment and Traffic. A visit always opens on Summary.
Summary tab
The Summary tab has two parts.
Timeline lists the moments of the visit in time order, from the start of the navigation:
- Navigation, with how the visitor arrived or the site they came from.
- Time to First Byte, First Contentful Paint and Largest Contentful Paint.
- Last blocking request, DOMContentLoaded and Load event: moments of the page load in the browser.
- INP Interaction, Main layout shift and Scrolled with the scroll depth.
- Active time: the end of the active time on the page.
- RUM Data Sent: when the script sent the data, with the state of the page.
The visit shows the Page title, the full Address and Came from (the site the visitor came from).
Metrics tab
The Metrics tab shows a card for each metric that the visit measured: LCP, INP, CLS and TTFB. Each card shows the value and its band. The tab shows only when the visit measured at least one of these metrics.
Largest Contentful Paint in one visit
The Largest Contentful Paint card has a Timing breakdown with four bars: Time to first byte, Resource load delay, Resource load duration and Element render delay. Each bar shows its time and its share of LCP. If the phases do not add up to LCP, a Not measured bar shows the rest.
Below the bars, the card can show Script execution (with the script address), Rendering time and Element. Element is the largest element of the page. See LCP.
Interaction to Next Paint in one visit
The Interaction to Next Paint card has a Timing breakdown with Input delay, Processing time and Presentation delay. Element shows the element that the visitor tapped or clicked. See INP.
Cumulative Layout Shift in one visit
The Cumulative Layout Shift card has Layout shift details about the largest shift:
- Main shift: the CLS value of the visit.
- Main shift time: when the shift happened.
- Page scroll position: where the visitor was on the page.
- Horizontal shift and Vertical shift: the direction and distance of the move, in pixels.
- Width change and Height change: the change in size of the element.
- Element: the element that moved.
See CLS.
Time to First Byte in one visit
The Time to First Byte card has a Timing breakdown with Redirects & Cache, DNS Lookup, Connection and Server response. If the phases do not add up to TTFB, a Not measured bar shows the rest. SSL/TLS handshake, within connection shows the secure handshake, which is part of Connection. See TTFB.
Waterfall tab
The Waterfall tab shows the Resources card: every file this visit loaded, with when it started and how long it took. Each file is one bar on a time line.
A bar has colored parts for each phase of the download: Waiting in queue, DNS lookup, Connecting, Secure connection, Server response and Download. Work in the browser shows as Main thread execution.
Vertical lines mark the moments of the visit: TTFB, FCP, LCP, DCL (DOMContentLoaded) and Load. Files that end before the LCP line can delay the main content.
If the visit has no file data, the tab says "No resource timing data".
Environment tab
The Environment tab shows what the visitor used:
| Group | Values |
|---|---|
| Location | Country |
| Device | Type, Screen, Pixel ratio |
| Browser & OS | Browser, OS |
| Hardware | Memory, CPU Cores |
| Network & protocol | Connection type, Effective type, Downlink, RTT, HTTP Version |
A group shows only the values that the browser reported. RTT is the round-trip time of the network. Downlink is the speed of the connection.
Traffic tab
The Traffic tab shows where the visit came from, in Traffic source & navigation. It shows only when the visit has a campaign, a referrer or a navigation type.
The values are UTM Source, UTM Campaign, UTM Medium, UTM Term, UTM Content, Referrer, Navigation type and HTTP Version.
Navigation types
Navigation type tells you how the visitor arrived at the page:
| Type | What it means |
|---|---|
| Navigation | A fresh visit: the visitor typed the address or clicked a link |
| Reload | The visitor refreshed the page |
| Back or forward | The visitor used the back or forward button of the browser |
| Prerendered | The browser loaded the page in the background before the visitor opened it |
| In-app navigation | A page change inside a single-page app |
Hover the type to see the value that the script recorded (Recorded as), for example back_forward or push.
Find a slow visit
To look at one slow visit in detail:
- In the filter dock, turn on Slow only.
- Add a URL Path filter for the page, if you know it.
- Click the LCP header to show the slowest LCP first.
- Click a visit to open it.
- Open the Metrics tab to find the slow phase.
- Open the Waterfall tab to find the slow files.
Troubleshooting
Why does the Page Views page say "No visits match the filters in this period"?
No visit on the selected device matches the dates, filters and switches. Turn off Slow only or With an LCP, select a longer date range, or remove a filter.
Why does a visit have a dash instead of a value?
The visit did not measure that metric. For example, INP needs a tap, click or key press.
Why does the Waterfall tab say "No resource timing data"?
The browser of the visitor did not report file data for this visit. Open another visit of the same page.
Why do addresses show :id?
RUM Monitoring replaces parts of an address that look like a code or a token before it stores the address. For example, a UUID shows as :uuid and a long token shows as :id. A normal record number, such as /orders/44172, stays as it is. A URL Path filter matches this stored form.
Related
- Overview - filters, devices and page-view limits
- LCP - LCP phases and the largest element for all visits
- Errors - the errors that visitors hit
- Synthetic Monitoring - a lab waterfall of the same page
Errors
The Errors page of RUM Monitoring shows the JavaScript errors and failed file loads that real visitors hit, grouped into problems you can mark as fixed.
Overview
CrUX Monitoring shows the Core Web Vitals that Google publishes for your site and pages, from real Chrome visits, on Phone and Desktop.
