Real User Monitoring
These are users who do not have a user account for your site/app. Anonymous users are included by default. You can choose to exclude these users in tables when there is an ‘Include anonymous users’ checkbox on the upper left corner. Alternatively, you can exclude anonymous users by default in these tables by changing them in your Real User Monitoring settings.
Load Time on Live Tab
The Load Time is the average page load time for the 100 most recent requests that your site had received. This is updated frequently and uses only live requests, not historic data. The load times are added up and divided by the number of load times collected.
Load Time on Performance Tab
The Performance tables with load times include color-coded segements to clarify how long each part of the page load takes.
Load time details:
- DNS: Time it takes for the nameserver lookup to resolve
- Latency: Time it takes for the host server to receive and process a request for an asset
- SSL: Time to complete an SSL handshake
- Server: Time it takes for the server to compute your code
- Transfer: Time the page has to wait for assets to load from the server
- Children: Time for asynchronous assets to process - this refers to all requests loaded by the page up until onLoad (includes scripts, stylesheets, images and XHR requests)
Most Recent Requests and Latest Crashes
These are the newest 10 instances of each.
Page Speed and Satisfaction
These score is a bucketed measure of page load time (i.e. when the load event handler terminates).
- Excellent is under 1000ms
- Needs work is between 1000ms and 4000ms
- Poor is over 4000ms.
Page URL display settings
This setting will take effect where Page URLs are displayed. If ‘show the protocol + domain’ is enabled, pages will display ‘https://foo.com', and if ‘show the path’ is enabled, URLs will display their path component: ‘/foo/bar.html’. The suggested setting is ‘path’ unless you have a multi-domain configuration.
A session is defined as a set of activity by a user within a half hour block. If a user performs an action after half an hour has elapsed since their previous one, a new session will be recorded.
If a user is active (clicking around your website) for hours, it will count as one session. Unless they became inactive (did not engage with your website) by longer than 30 minutes. After 31 minutes of inactivity, if they’ve re-engaged with your website again, it will be counted as new session.
If a user is not logged into your site/app, Real User Monitoring identifies them by using GUID (global unique identifier). We define these as anonymous users. These are users who do not have a user account for your site/app. You can choose to include these users in tables when there is an ‘Include anonymous users’ checkbox on the upper left corner. Alternatively, you can include anonymous users by default in these tables by changing your Real User Monitoring settings.
Site Health Score
This score is bucketed metric for the current (live) site load time and is updated in real time.
- Excellent is under 500ms
- Good is from between 500ms and 1000ms
- Needs work is from between 1000ms and 4000ms
- Poor is at or over 4000ms
A route or view that is loaded from within a client-side Single Page Application (SPA). A virtual page view is an event that occurs during the lifecycle of an SPA. This route view action is usually taken by the user, and occurs some time after the inital static page load. Its own data contains its viewing duration (defined as the time from one view event to the next). If configured to track these view events, Real User Monitoring will display these separately from static page loads, and they will contain child data that occured during the view (for instance XHR and CSS/image requests).
Describes the difficulty of resolving a rule. The difficulty scores are represented by wrenches - one for easy, two for moderate and three for difficult.
The name given to a rule and all the issues that fail, pass and are ignored under that specific rule.
A page on your site that has been scanned by Real User Monitoring - Insights
The number of times an issue group has been
Real User Monitoring Insights runs a weekly scan over all your pages once a week. The check looks at a set of rules to measure your site against. Your site is scored depending on the number of rules passed.
The scan time depends on how many pages and assets a site has. The time can vary from a few minutes to an hour.
Real User Monitoring Insights checks your site’s pages and assets depending on the rule being checked.
Page: This is a page of your site, for example: https://mysite/about
The rules were developed by checking industry best-practices. The rules have a set of standards that your site is measured against. If your site fails on a rule, you will be shown the exact page or asset that caused the rule to fail and the steps you can take for the rule to pass.
The rules highlight areas where your site can improve. A failing rule does not equal software crashes - Crash Reporting will help you detect and diagnose these. The rules, instead, look at issues that are known to slow down a site. A scan shows you areas of your site that may contribute to slow load times that affect the performance of your site.
Failed: This status means a rule has failed the Real User Monitoring Insights check.
Passed: This status means a rule that previously failed the Real User Monitoring Insights check is now passing or has been marked as ‘Passed’ by you. If you mark a failing rule as ‘Passed’ and the issue is not resolved, then the rule will be returned to the ‘Failed’ status on the next scan.
Ignored: You can change the status of a rule as ‘Ignored’ if you do not want Real User Monitoring Insights to scan and score your site using a particular rule. Any new instances of a failing page or asset based on an ignored rule will be ignored and you will not be notified. This status is equivalent to the Crash Reporting error group status ‘Permanently ignored’.
The resource type a rule is checking.
The number of times a page has been viewed by site visitors.