RUM Metrics

Prev Next

Catchpoint Real User Monitoring (RUM) solution captures the following metrics:

MetricDescription
# BOUNCES# of users who visit site and don’t navigate to other pages on site
# JS ERRORS PER PAGE# of JavaScript errors per page
# PAGE VIEWSOverall # of page views
# PAGES / VISIT# of pages users viewed when visiting site
# REDIRECT# of redirects on the root request.
# VISITS (UNIQUE)# of unique visits (a visit ends after 30 minutes of no activity)
% BOUNCES% of users who visit site and don’t navigate to other pages on site. [#Bounces / #Visits(Unique) * 100]
CONNECT (MS)Time taken to establish a connection with the server for the root request. Does not include connect time for redirects. (not supported by IE9 and IE10 for sites with SSL)
CONTENT LOAD (MS)The time it took to load the entire content of the webpage after connection was established with the server for the root request.
CONVERSION ITEMS# of items sold
CONVERSION RATE# of conversions over unique visits
CONVERSION SALES# of sales
CONVERSIONS# of conversions
DEAD CLICKSUser interactions on a webpage or app where the user clicks or taps an element, but no visible response or expected behavior occurs.
DNS (MS)Time taken for the client to resolve the DNS for the root request. Does not include DNS time for redirects.
DOCUMENT COMPLETE (MS)Time elapsed from sending the request to onload event
DOM INTERACTIVE (MS)Time elapsed from request being issued to immediately before the user agent sets the current document readiness to "interactive".
DOM LOADED (MS)The time it took to load the Document Object Model (DOM).
ENTRY TO ONLOAD(MS)Time elapsed from initiating the request to onload event.
EXIT TO ENTRY (MS)Time elapsed from unload event to starting the rendering of the content from the next page. This is similar to Response.
EXIT TO ONLOAD (MS)Time elapsed from unload event to onload event of the next page. This is close to Document Complete time.
FIRST ENGAGEMENT TIMEThe time it took between a user navigating to a page and the user first interacting with the page content.
FIRST INPUT DELAYThe time from when a user first interacts with the site (i.e. when they click a link, tap on a button, or use a custom, JavaScript-powered control) to the time when the browser responds to that interaction.
FIRST PAINT & FIRST CONTENTFUL PAINTThe point, immediately after navigation, when the browser renders the first bit of content.
FULL CONNECT (MS)Time taken to establish a connection with the server for the root request including SSL. Does not include connect time for redirects.
INSIGHT INDICATORSThe list of indicators and available values associated
INTERACTION TO NEXT PAINTAssesses the time it takes for a browser to respond to a user interaction (like clicking, tapping, or pressing a key) and visually update the page in response. 
LOAD (MS)Time elapsed between loading the first byte to the last byte of the root request. Does not include load time for redirects.
RAGE CLICKSThe multiple rapid clicks on the same area of a webpage or app within a short period, indicating user frustration with unresponsive or confusing elements.
RESPONSE (MS)Time elapsed from the request being issued to the server responding with the last byte for the root request. Includes response time for redirects.
SSL (MS)Time taken to establish the SSL handshake with the primary URL. (not available for IE9 and IE10 for sites with SSL)
THRASHED CURSORA user behavior pattern where the mouse is moved rapidly and erratically across the screen, often signaling frustration or confusion.
TIME ON PAGEThe total time the page remains in focus in the user’s browser or app window during a session.
TIME TO INTERACTIVETime it takes for a page to become interactive
TOTAL ENGAGEMENT TIMEThe total time the user was interacting with the page content.
VISUALLY COMPLETE (MS)Time taken for the content in the viewport to appear complete to an end user. Calculated by listening to viewport elements until the timestamp difference between two elements loading is greater than 500 ms. Any mouse events that happen stop Catchpoint from listening to mutations. When the Mutation Observer API is not available in the browser, we use resource load times to calculate.
WAIT (MS)Time elapsed from sending the request to receiving the first byte of response from the root request. Does not include wait time for redirects.