UEM provides several timing measures that can be used in charting, Business Transactions, and more. This page describes the timings a User Action PurePath provides.
This example shows the load action of a page
index.html, which loads several synchronous and asynchronous scripts, partially from third party providers.
- The script
async.jsis detected on the server side and has started during the onload action, but ended afterwards. Therefore it only counts partially to the action's server contribution.
- Third party resource timings are never part of server or network contribution, but their load times can be used using the Third Party Content Load measure.
- Overlapping requests like
async.jsdo not increase server contribution, but are addressed by network contribution calculation.
- Network contribution is only available if the PurePath visit possesses a bandwidth value.
- The network contribution is the sum of the file size of all requests divided by the bandwidth value (bytes per second).
- Dom Load Time is the time from page initialization to the DomContentLoaded event or, for older Internet Explorer versions, to the time the DOM is interactive.
- See Perceived Render Time for detailed information about this measure. The first image contributes, the last one is not visible from the beginning on and therefore does not contribute to the perceived render time.
LastImage.pngloads asynchronously, thus does not lock the load handler.
- The onload event handler completion ends the action.
There are several ways to trigger a redirect to another page. For example, clicking an anchor tag, or an XMLHttpRequest callback could rewrite the