Timing values

  • Release version: Zurich
  • Updated July 31, 2025
  • 1 minute to read
  • Timing values are broken down into several sections.

    Figure 1. Client Transaction Timing
    The variables in this diagram are defined as follows:
    Table 1. Timing Values
    Variable Description
    start_time Date and time the user requests a page (the user clicks on a link). This value is set by hooking into the before unload event of the previous page. WebKit browsers do not properly support the beforeunload event, which is why the client timings are not supported i Safari or Chrome.
    load_time Date and time that the current page starts loading in the browser. An inline javascript that runs as the first script in the HTML body sets this value.
    server_time Time in ms spent by the server processing the transaction. The server reports this value to the client.
    load_completion_time Date and time that the page is fully rendered in the browser. This operation is performed as the last script on the page and identifies the time the page completed loading.
    The following timings are reported at the bottom right of many forms and lists:
    Table 2. Timing Values
    Label Element Description Calculation
    Response Time client_response_time Overall time to deliver the page by subtracting the time the user requests the page from the time the page is fully rendered in the browser. load_completion_time - start_time
    Server Time client_server_time Time the server takes to process the transaction. server_time
    Network Time client_network_time Time the network takes to process the request. Calculated by subtracting the time of the user's request, from the time the page starts loading in the browser, and then subtracting the server processing time. load_time - start_time - server_time
    Browser Time browser_time Time the browser takes to deliver the page by subtracting the time the page is fully rendered from the time the page starts loading in the browser. load_completion_time - load_time