On this page:
Related pages:
Key Browser RUM metrics are displayed on the Geo, Pages & AJAX Requests, and Usage Stats dashboards. They can also be seen on the All Pages and Top Pages lists and in the Metric Browser.
In addition, the Metric Browser gives you the ability to view these metrics in the context of Ajax requests, iframes, applications, base pages, browsers, devices, and geographic locations.
You can build custom health rules based on Browser RUM Page, Ajax, and iframe metrics in the health rule builder. Use these rules to automatically monitor key metrics in your installation. For more information, see Health Rules.
Browser RUM Timing Metrics Overview
The following provides an overview of the primary Browser RUM page and iframe timing metrics. For key Ajax metrics, see Ajax Metrics Availability. Metrics in black are available from both modern browsers that support the Navigation Timing API and older browsers. Metrics in blue are available only from NavTime browsers. You may see a value of unknown for some metrics taken using older browsers.
When users begin to load the first instrumented page, a timer is started by the JavaScript Agent. The timer or the NavTime responseStart starts the first-page timing.
For all subsequent pages, a cookie is set by the agent when the Prompt for unload event happens on the current page. This cookie or the NavTime navigationStart initializes a fuller picture of the entire page loading sequence.
Because a NavTime browser always sets navigationStart, you can get this information from it even on the first page a user loads from your site.
Navigation Timing capable browsers also provide highly granular information on connection details.
Browser RUM Metrics Defined
Timing metrics are the average times, in milliseconds, over the time range selected in the Controller UI or REST API call. The three-letter abbreviation is the short name as it is recorded in the web beacon.
| Name (Short Name) | NavTiming Capable Browsers1 | Browsers without NavTiming Support | Available For . . . | Definition |
|---|---|---|---|---|
| Ajax Callback Execution Time (DPT) |
| responseEnd to domContentLoadedEventStart (context of the Ajax object) | Ajax Requests | Time for the browser to process the Ajax response. |
| Ajax Response Download Time (DDT) | responseStart to responseEnd(context of the Ajax object) |
| Ajax Requests | Time for the browser to download the complete Ajax response. |
Ajax Request Errors per Minute (Short name based on |
| Total number of Ajax requests that generate an error per minute. | ||
Ajax Requests per Minute (Short name based on |
| Total number of Ajax requests per minute. | ||
| Application Server Calls per Minute |
| Number of requests that actually hit the application server, rather than a cache. | ||
| Application Server Time (also called Server Time in the UI) |
| Processing time for requests on the application server. | ||
| Browser Queue Time |
| |||
| DOM Building Time (DPT) | responseEnd to domContentLoadedEventStart | N/A |
| Time for the browser to build the Document Object Model (DOM) and make it available for JavaScript to apply rendering logic. |
| DOM Ready Time (DOM)2 | navigationStart to domContentLoadedEventStart | Time between the writing of the
|
| Interval between the time that a user initiates a request and the time that the DOMContentLoaded event (or the internal handler's onready event) occurs. |
| Domain Lookup Time (DNS) | domainLookupStart to domainLookupEnd | N/A |
| Time to complete the domain lookup portion of the server connection time. |
| End User Response Time (PLT)2 | navigationStartto loadEventEnd | Time between the writing of the
|
| Average interval between the time that a user initiates a request and the completion of the page load of the response in the user's browser. In the context of an Ajax request, it ends when the response has been completely processed. |
| First Byte Time (FBT)2 | navigationStart to responseStart | Time between the writing of the
|
| Interval between the time that a user initiates a request and the time that the browser receives the first response byte. In the context of an Ajax request, First Byte Time is the interval between the Ajax request dispatch and the time that the browser receives the first response byte. |
| Front End Time (FET) | responseStart to loadEventEnd | Time between when the page's JavaScript Agent begins executing and the onload event. |
| Interval between the arrival of the first byte of text response and the completion of the response page rendering by the browser. Includes HTML Download, DOM Building Time, and Resource Fetch Time. |
| HTML Download and DOM Building Time (DRT) | responseStart to domContentLoadedEventStart | Time between when the page's |
| Time to make the complete HTML document (DOM) available for JavaScript to apply rendering logic. Includes the HTML Download and the DOM Building Time. |
| HTML Download Time (DDT) | responseStart to responseEnd | N/A |
| Time for the browser to download the complete HTML document content. |
Iframe Requests per Minute (Short name based on |
| Total number of iframe requests per minute. | ||
| Images Loaded per Pageview |
| Total number of images in a Calculated after page has completely loaded. | ||
Page Requests per Minute (Short name based on |
| Total number of Page requests per minute. This is the metric displayed across most of the UI. | ||
Page views with JavaScript Errors per minute (Short name based on |
| Total number of page views that contain JavaScript errors per minute. | ||
| Resource Fetch Time | domContentLoadedEventStartto loadEventEnd | Time between an internal handler's onready event, similar to jquery.onready(), and onload. |
| Time for the browser to complete the download of remaining resources, including images, and finish rendering the page. |
| Resources Loaded per Pageview |
| Total number of resources in a Calculated after the page has completely loaded. | ||
Requests per Minute (Short name based on |
| Total number of requests (Page + Ajax + iframe) per minute. | ||
| Scripts Loaded per Pageview |
| Total number of scripts in a Calculated after the page has completely loaded. | ||
| Server Connection Time (SCT) | navigationStart to requestStart | N/A |
| Interval between the time that a user initiates a request and the start of fetching the response document from the server or application task. Includes the time spent on redirects, domain lookups, TCP connects and SSL handshakes. |
| SSL Handshake Time (SSL)3 | secureConnectionStart to connectEnd | N/A |
| Time taken to complete the SSL handshake.
|
| TCP Connect Time (TCP) | connectStart to connectEnd | N/A |
| Time to complete the TCP connect portion of the server connection time, the equivalent of one network roundtrip of latency. |
| Total Resource Redirect Time |
| Time for all redirects associated with fetching resources. Calculated after the page has completely loaded. |
1 NavTiming capable browsers support the W3C Navigation Timing API.
2 This metric is not available for iOS or Opera browsers since those platforms don't report this metric accurately.
3 The most recent versions of Firefox and IE do not currently report this metric, despite the fact that it is part of the W3C spec.
Ajax Metrics Availability
Because Ajax requests occur in the context of the larger page, these four core metrics are always available, regardless of the browser type.
For more information on which browsers support the Navigation Timing API, see the Can I Use website.
Beacon dispatch times:
- There is a wait of 1000 ms from the time
adrum-ext.jsis loaded and before beacons are sent. This is to capture the any Ajax requests fired atonload.
Note that thePage End User Responsetime does not include the Ajax load time.
- For Angular v1.x apps auto-instrumented with the JavaScript Agent v4.1.3, the beacon dispatch was delayed up to 10,000 ms to include load time for all Resources as a component of
Virtual Page End User Responsetime. Starting in 4.1.4, this behavior has changed, and beacons are dispatched after 5000 ms. As a result, VP EUR now includes Ajax timings but no longer includes Resource Timings. For manually instrumented SPAs, however, beacons are dispatched immediately whenADRUM.reportis called.
Resource Timing Metrics
Resource timing metrics are the median times, in milliseconds, over the time range selected in the Charts tab of the Resources page. The resource timing metrics shown in the Records tab of the Resources page are raw data. For a visual representation of the resource timing, see the Resource Timing Overview diagram from www.w3.org.
| Metric Name | How It's Calculated | Description |
|---|---|---|
| Browser Wait | startTime or redirectEnd to fetchStart | Time from the redirection or request start until the browser begins to fetch the resource. |
| Redirect Time | redirectStart to redirectEnd | Time for all redirects associated with fetching resources. This time is calculated after the page has completely loaded. |
| DNS Wait Time | fetchStart to domainLookupStart | Time from when the browser starts to fetch the resource until the browser starts the domain name lookup for the resource. |
| DNS Time (DNS Lookup) | Time to complete the domain lookup portion of the server connection time. | |
| TCP Wait Time | domainLookupEnd to connectStart | Time for the browser to find the domain name for the resource before a connection is made. |
| Connection Time (TCP Connection) | connectStart to connectEnd | Time to complete the establish the TCP connection for a resource: the equivalent of one network roundtrip of latency. |
| SSL Time |
(if | Time to retrieve a resource over a secure connection |
| Request Wait Time (Request and Wait) | Time for the request is made for a resource from the server, cache, or local resource before the connection is closed. | |
| Request Time | requestStart to responseStart | Time for the browser to complete the request for a resource from the server, cache, or local resource. |
| Response Time (Response) | responseStart to responseEnd | Time for the browser to download the complete HTML document content. In the context of an Ajax request, the time for the browser to download the complete Ajax response. |
| First Byte Time | startTime to responseStart | The time from when the request is made until the first byte of the resource is received by the browser. |
| Resource Load Time | startTime to responseEnd | Time for the browser to start a request and receive a response for a resource. |
The metric names given in parentheses are used in the Resource Waterfall of the Resource Details dialog. See Resource Waterfall for more information.
The following additional metrics are available based on resources loaded during Resource Fetch Time:
Name | Definition |
|---|---|
| Bytes per Pageview | Number of bytes downloaded with this pageview. |
| Scripts Loaded per Pageview | Number of JavaScript files (*.js) downloaded with this pageview. |
| Images Loaded per Pageview | Number of image files (*.bmp, *.gif, *.jpeg, *.jpg, *.png, *.webp) files downloaded with this pageview. |
| Resources Loaded per Pageview | Number of all resource files (the above plus *.css, *.svg, *.htm, *.html, *.ttf, *.woff, *.otf, *.eot) files downloaded with this pageview. |