This document describes the statistical methods and configurations passed in for page, API, and resource speed tests.
Page Speed Test
Note:
RUM enables the page speed test feature for you by default.
After you successfully install and initialize the SDK, the Aegis instance will report the following metrics by default:
1. DNS query: domainLookupEnd - domainLookupStart;
2. TCP connection: connectEnd - connectStart
3. SSL connection establishment: requestStart - secureConnectionStart
4. Request response: responseStart - requestStart
5. Content transfer: responseEnd - responseStart
6. DOM parsing: domInteractive - domLoading
7. Resource loading: loadEventStart - domInteractive
8. FMP: RUM listens on the first screen DOM changes within 3 seconds after a page is opened and takes the time when the number of DOM changes reaches the highest as the time when the first screen framework rendering is completed. (setTimeout is used to start first screen element collection 3 seconds after SDK initialization. As JavaScript is executed in a single-thread environment, the collection time point may be more than 3 seconds after SDK initialization.)
9. Complete page loading duration: sum of 1–7 (DNS query, TCP connection, SSL connection establishment, request response, content transfer, DOM parsing, and resource loading)
Note:
For more information on how to calculate page open performance metrics 1–7, see PerformanceTiming. You can print aegis.firstScreenInfo to view the corresponding DOM element of firstScreenTime. If a DOM element cannot represent the first screen, you can add the <div AEGIS-FIRST-SCREEN-TIMING></div> attribute to recognize it as the key first screen element, so that the SDK will consider that the first screen is loaded if it is displayed on the first screen. You can also add the <div AEGIS-IGNORE-FIRST-SCREEN-TIMING></div> attribute to add the element to the blocklist. RUM provides the page loading waterfall plot based on the above metrics.
Note:
In server scenarios, the firstScreenTime in the waterfall plot may be longer than the DOM parsing duration, which is caused by incompatibility of mobile devices. As some devices cannot get the durations of DNS query, TCP connection, and SSL connection establishment, the three metrics will have a smaller average value after being aggregated, causing metrics except firstScreenTime to shift to the left.
API Speed Test
Note:
How to enable: pass in reportApiSpeed: true during initialization.
Aegis tests the API speed by hijacking XHR and fetch.
Resource Speed Test
Note:
How to enable: pass in reportAssetSpeed: true during initialization.
Aegis uses PerformanceResourceTiming provided by the browser to test the resource speed.