mPulse system timers
mPulse provides built-in, system timers that are automatically captured and stored in the mPulse beacon.
mPulse system timers are available in the filter bar at the top of the dashboards as shown in this example.
This table lists the mPulse system timers that are common to most dashboards.
|Perceived Performance||First Contentful Paint||The time when the browser displays something that has content for the first time. For example, text, image, canvas, or SVG.||
|First Input Delay||How quickly the page was able to respond to the user’s first interaction.||
|First Paint||The time when the browser first rendered after navigation.
Currently, mPulse collects this value for the following browsers:
|Time to Interactive||The time when the page looks ready to use and is responsive to user input.|
|Time to First Interaction||The time when the user first tries to interact with the page.|
|Time to Visually Ready||The time when the page looks ready to use.|
||Client Round-Trip Time||The round-trip time between the browser and the Akamai edge server (nearest to the end user). This timer can help quantify how well connected your end users are to the nearest Akamai point of presence (PoP).||
|CDN Edge Time||The time between when the first byte of the request is received by the Akamai edge server from the client browser, and just before the first byte of the response is written back. This does not include the time that may or may not have been spent forwarding the request to the origin. It applies to requests delivered by the Akamai network via an mPulse-enabled property configuration. This timer can help quantify the time spent within the Akamai CDN.|
|Origin Time||The round-trip time between the Akamai edge server (nearest to the origin), and the origin. This includes the time the origin spends handling the request. Note that this timer is only relevant when content is served from the origin, and not CDN cache. It applies to requests delivered by the Akamai network via an mPulse-enabled property configuration. This timer can help diagnose whether the origin is the source of slow load times.|
|Standard||Back-End Time||Time from navigation start to first byte. Median is shown on Dashboard.||None|
|DNS Resolution||domainLookupEnd - domainLookupStart from NavigationTiming.|
|DOM Loading||domLoading - navigationStart from NavigationTiming.|
|DOM Ready||domComplete - navigationStart from NavigationTiming. Also known as DOM Complete.|
|Front-End Time||Time from first byte to onload (or whenever the page is considered ready).|
|Page Load||loadEventEnd - navigationStart from NavigationTiming.|
|SSL Handshake||connectEnd - secureConnectionStart from NavigationTiming.|
|TCP Connection||connectEnd - connectStart from NavigationTiming.|