Overview of RUM Checks & Reports

A RUM report provides real-time data surrounding the average page load time for your website, and the data is provided for various countries, URLs, browsers, and devices.

In order to begin to generate RUM reports, you will need to first add a Real User Monitoring check under Monitoring>Checks. Once you save the check, a RUM code will populate within the check. The HTML snippet that is provided when creating the check will need to be placed before your site's closing </body> tag. This will enable RUM checks on all the pages where the HTML snippet appears. The illustration below provides an example of adding a Real User Monitoring check. The following describes the fields provided when creating a Real User Monitoring check:

Name of Check: Enter the name of your check.

Contacts: Select a contact group for your check.

Check Type: Select “Real User Monitoring” as the check type.

Domain: Enter the domain for your check e.g. google.com.

Max Load Time: An alert will raised if the average load time on your pages exceeds the value that is placed in this field. Furthermore, there must be 10 or more page loads from your pages before this alert can be raised. Once this alert is raised, you will receive a recovery notification once the average page load is less than 1 of the value placed in this field. For example, if your max load time value is set to 5 and alert was raised due to the average load exceeding that value, then a recovery notification will not be sent until the average load time is 3.99 or less.

Note: If you sign-up for the Free monitoring plan, then you will be limited to only (1) Real User Monitoring check.

Managing URL Patterns

Once the aforementioned HTML snippet is placed on your desired web pages, you can create URL patterns and assign them to specific groups so that you can track the various URLs from your site. The average load time and total number of requests for the groups you create will display under the Page/Group section of the RUM report.

Furthermore, you can reach the Manage URL Patterns page once you select the Settings button next to your RUM checks on the Checks page; just select Manage URL Patterns from the Settings drop-down. Once on the page, click the “Add New URL Prefix” button as shown in the illustration below in order to setup prefixes from additional URLs you desire to track.

RUM Reports

The RUM report will provide you with real-time data regarding the average page load from sites where a Real User Monitoring check was created. The report also allows you to export a CSV of your RUM requests in order to further analyze the data within your reports. In order to view a RUM report, go to Reports>RUM Reports, then choose a desired report from the report list as shown in the illustration example below.

RUM Report Data

Once you’ve selected a report, you will be presented with the data for your report based on your selected date range. The following provides a description of the data provided in the report:

Average Load Time: This represents the average load time for all URLs being tracked within your website(s).

Average First Render Time: This marks the point when the DOM is ready, and there are no style sheets blocking the JavaScript execution - meaning the browser can now (potentially) construct the render tree. This is an important metric for most websites because if there is a slow first potential paint time, users might be tempted to abandon the loading of the application.

Total Page Loads: This represents the total number of page loads for all URLs on your site based on your selected date range.>

Unique Pages: This represents the number of unique URLs that were visited during your selected date range.

Average State Breakdown: The eleven gauges that compose this part of the report shows the percentages of time on average that all of your total page loads are spending in three main categories including Network, Backend, and Frontend.

The gauges will animate to provide you a feel for how long the browser could have been loading for your user. Please note that we don’t currently interject any kind of bandwidth calculation which can dramatically skew these results depending on your traffic latency.

The following provides summaries of the sub-gauge breakdown calculations:

  • Redirect: This represents the time it takes for any page redirects.
  • DNS: This represents the time it takes for a DNS to resolve.
  • Connect: This represents the time it takes to make a TCP connection with the server.
  • Server: This represents the time it takes it takes the server to generate the HTML payload.
  • Receive: This represents the time it takes it takes the browser to download the response from the server.
  • DOM Fetch: This represents the time it takes it takes the browser to start parsing the first received bytes of the HTML document and load into DOM.
  • Asset Download/Render: This represents the time it takes for the browser to load images/videos and execute any Javascript code listening for the DOMContentLoaded event.
  • Onload Events: This represents the time it takes it takes the browser to execute Javascript code waiting for the window.load event.

Mobile Devices vs. Desktop Performance: This represents the average page load received between mobile and desktop devices.

United States vs. International: This represents the average page load received between the United States and international countries.

User Locations: This map represents the locations which comprise your page loads. When you click on a country within the map, you will be provided with a breakdown for that country.

Pages: This section provides you with the number of requests and average page loads for each URL prefix and groups that are configured on the Manage URL Patterns Page. When you click on a link for a page/group, you will be provided with a breakdown for that page/group.

  • If there is a listing for “Unmatched URLs”, then this is related to URLs that you’ve not created a specific URL prefix for. Please review the Managing URL Patterns heading in this article for documentation on creating URL prefixes.

Browsers: This section provides you with the number of requests and average page loads per browser.

Powered by Zendesk