Browser RUM Metrics

Key Browser RUM metrics are displayed on the Geo, Page, Iframe, and Ajax 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 basic Browser RUM page and iframe timing metrics.  For key Ajax metrics, see here.  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, begins 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

Time 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 Browsers +	Browsers without NavTiming Support	Available For . . .	Definition
Ajax Callback Execution Time In 3.7 this metric was called Document Processing Time	DPT	responseEnd to domContentLoadedEventStart in the context of the Ajax object	responseEnd to  domContentLoadedEventStart in the context of the Ajax object	Ajax Requests	Time for the browser to process the Ajax response; this typically includes the time to apply the response data to the DOM
Ajax Request Errors per Minute	Based on ARE entries			Ajax Requests, App, Browser, Device and Geo	Total number of Ajax requests that generate an error per minute
Ajax Requests per Minute	Based on PLC entries			App, Browser, Device, and Geo	Total number of Ajax requests per minute
Ajax Response Download Time In 3.7 this metric was called Document Download Time	DDT	responseStart to  responseEnd in the context of the Ajax object	responseStart to  responseEnd in the context of the Ajax object	Ajax Requests	Time for the browser to download the complete Ajax response
Application Server Calls per Minute				Ajax Requests App, Base Pages, Browser, Device, Geo, and iframes	Number of requests that actually hit the application server, rather than a cache
Application Server Time (also called Server Time in the UI)				Ajax Requests,  App, Base Pages, Browser, Device, Geo, and iframe	Processing time for requests on the application server
Browser Queue Time				Ajax, App, Base Pages, Browser, Device, Geo, and iframes
DOM Building Time In 3.7 this metric was called Document Processing Time	DPT	responseEnd to domContentLoadedEventStart	N/A	App, Base Pages, Browser, Device, Geo, and iframes	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	navigationStart to domContentLoadedEventStart	Time between the writing of the starttime cookie on the previous page and an internal handler's onready event, similar to jquery.onready() This metric is not available for iOS or Opera browsers since those platforms don't report this metric accurately.	App, Base Pages, and Geo	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	App, Base Pages, Browser, Device, Geo, and iframes	Time to complete the domain lookup  portion of the server connection time
End User Response Time	PLT	navigationStart to  loadEventEnd	Time between the writing of the starttime cookie on the previous page and the onload event This metric is not available for iOS or Opera browsers since those platforms don't report this metric accurately.	Ajax Requests,  App, Base Pages, Browser, Device, Geo, and iframes	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	navigationStart to responseStart	Time between the writing of the starttime cookie on the previous page and when the page's JavaScript agent begins executing. This metric is not available for iOS or Opera browsers since those platforms don't report this metric accurately.	Ajax Requests, App, Base Pages, Browser, Device, Geo, and iframes	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.	App, Base Pages, Browser, Device, Geo, and iframes	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 In 3.7 this metric was called Document Ready Time	DRT	responseStart to  domContentLoadedEventStart	Time between when the page's JavaScript agent begins executing and an internal handler's onready event, similar to jquery.onready().	App, Base Pages, Browser, Device, Geo, and iframes	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 In 3.7 this metric was called Document Download Time	DDT	responseStart to  responseEnd	N/A	App, Base Pages, Browser, Device, Geo, and iframe	Time for the browser to download the complete HTML document content
Iframe Requests per Minute	Based on PLC entries			App, Browser, Device,  and Geo	Total number of iframe requests per minute
Images Loaded per Pageview				Ajax, App, Base Pages, Browser, Device, Geo, and iframes	Total number of images in a pageview. Calculated after page has completely loaded.
Page Requests per Minute	Based on PLC entries			App, Browser, Device, and Geo	Total number of Page requests per minute. This is the metric displayed across most of the UI.
Page views with JavaScript Errors per minute	Based on EPM entries			App, Base Pages, Browser, Device, Geo, and iframes	Total number of page views that contain JavaScript errors per minute
Requests per Minute	Based on PLC entries			Ajax Requests,  App, Base Pages, Browser,  Device, Geo, and iframes	Total number of requests (Page + Ajax + iframe) per minute
Resource Fetch Time In 3.7 this metric was called Page Render Time.	PRT	domContentLoadedEventStart to  loadEventEnd	Time between an internal handler's onready event, similar to jquery.onready(), and onload.	App, Base Pages, Browser, Device, Geo, and iframes	Time for the browser to complete the download of remaining resources, including images, and finish rendering the page
Resources Loaded per Pageview				Ajax, App, Base Pages, Browser, Device, Geo, and iframes	Total number of resources in a pageview. Calculated after page has completely loaded.
Response Available Time	RAT	requestStart to  responseStart	N/A	App, Base Pages, Browser, Device, Geo, and iframes	Interval between the beginning of the processing of the request on the browser to the time that the browser receives the response. Includes time in the network from the user's browser to the server.
Scripts Loaded per Pageview				Ajax, App, Base Pages, Browser, Device, Geo, and iframes	Total number of scripts in a pageview. Calculated after page has completely loaded.
Server Connection Time	SCT	navigationStart to  requestStart	N/A	App, Base Pages, Browser, Device, Geo, and iframes	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	secureConnectionStart to  connectEnd	N/A	App, Base Pages, Browser, Device, Geo, and iframes	Time taken to complete the SSL handshake 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.
TCP Connect Time	TCP	connectStart to  connectEnd.	N/A	App, Base Pages, Browser, Device, Geo, and iframes	Time to complete the TCP connect portion of the server connection time, the equivalent of one network round trip of latency
Total Resource Redirect Time				Ajax, App, Base Pages, Browser, Geo, and iframes	Time for all redirects associated with fetching resources. Calculated after page has completely loaded.

+ NavTiming capable browsers support the W3C Navigation Timing API.

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 web site.

Resource Timing Metrics

For browsers that support the Resource Timing API, the following additional metrics are available based on resources that are loaded during Resource Fetch Time: