Filtering RUM reports


On this page

Every RUM report can be filtered from the bar at the top of the page. These filters are shared across the Dashboard, Pages, Metric Detail and Audience reports, and the report updates instantly as you change them. Clear a filter by pressing the x button next to its name.

Filter by device#

RUM reports shows all devices in aggregate (All option) or separately for Desktop, Tablet, or Mobile. Filtering by device is especially helpful in surfacing often large differences in speed experience observed between Desktop and Mobile sessions.

Filter by dimension#

RUM reports can be filtered by various dimensions:

DimensionDescription and examples
Page PathFilter by specific page URLs. Example: /pricing, /cart
Page GroupingFilter by custom page groupings. Example: /blog/*, /products/*
Navigation TypeFilter by how the user navigated to the page. Example: Navigate, Reload, Back/forward, Back/forward cache, Prerender, Restore, Soft navigation
Attributed ElementFilter by specific elements using attribution. Example: hero-image, start-new-search-button
BrowserFilter by browser name. Example: Chrome, Safari
Browser VersionFilter by specific browser versions. Example: 144, 16
Device VendorFilter by device vendor. Example: Apple, Samsung
Device ModelFilter by specific device models. Example: iPhone, Moto G
Operating SystemFilter by operating system name. Example: iOS, Windows
Operating System Version ("OS Version")Filter by specific operating system versions. Example: 10.15
CountryFilter by the country from which the user is accessing the site. Example: Australia, Germany, United Kingdom, Poland
CityFilter by the city from which the user is accessing the site. Example: Melbourne, Berlin, Liverpool, Krakow

The Navigation Type dimension describes how a user navigated to your page:

ValueDescription
NavigateA standard page load, such as following a link, entering a URL, or submitting a form.
ReloadThe page was reloaded, for example with the browser's refresh button or location.reload().
Back/forwardThe page was loaded through the browser's history, using the back or forward buttons.
Back/forward cacheThe page was restored instantly from the browser's back/forward cache (bfcache).
PrerenderThe page was loaded ahead of time, before the user navigated to it.
RestoreThe page was restored after the browser restarted, such as reopening a tab from a previous session.
Soft navigationA client-side route change in a single-page app, where JavaScript updates the page and URL without a full page load.

"Soft navigations" are supported from Chrome 151+, other browsers don’t support soft navigations at the moment.

Filter by URL#

The Real User Monitoring → Pages report can be filtered by URL type (singular or grouped):

OptionDescription
PathURL of a single page.
Page groupingGroup of pages matching a defined URL pattern.

While filtering by path helps find the best or worst performing pages, filtering by page grouping brings attention to specific groups, such as landing pages, cart pages, blog posts, documentation pages, and so on.

Filter by aggregation#

OptionDescription
P50 (median)50% of session metric measurements fall below the P50 value, and 50% above.
P7575% of session metric measurements fall below the P75 value, and 25% above.
P9595% of session metric measurements fall below the P95 value, and 5% above.
P9898% of session metric measurements fall below the P98 value, and 2% above.
MinimumMinimum collected metric values for selected time period.
MaximumMaximum collected metric values for selected time period.

P75 aggregation is a good starting point for evaluating how a site is performing. It's often used as a monitoring baseline, including Chrome User Experience Report (CrUX) data. If your site passes the Core Web Vitals assessment at P75, we recommend moving the target to P95. At P95, the vast majority of the visitors have a positive user experience (for example: 95 visitors in 100 have a good user experience, while only 5 don’t).

Filter by time period#

RUM reports can be displayed for the following time periods:

OptionDisplay
TodayHourly
Last 7 daysDaily
Last monthDaily
Last 3 monthsWeekly
Last 6 monthsMonthly
All timeYearly

The longer the time period, the easier it is to spot persisting performance trends that might need to be addressed. Shorter time frames can help find newly emerging changes, like after a new release.

To attribute a change to a particular release, segment by deployment on the Metric Detail report.