All of the following factors affect the duration that is required to make the complete user impression:
- The binary files are typically on your web application's hosting server, but the text page might ask for binary files from a third-party server.
- When a browser begins to receive an HTML page, it starts to evaluate the page contents, even before the page is fully downloaded from the web server. The browser can spin off threads to handle the binary file requests, which runs concurrently. To see the entire page, each of these binary file requests must finish or timeout.
- Fast computers handle the page rendering quicker than slow computers.
Because Experience Analytics captures the browser-server interactions, these client-side actions are not recorded by Experience Analytics. The UIEvents feature hooks into the Document Object Model of the page and can track these actions, which enable the reporting of this information and factoring it into the duration of a fully rendered page.