Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Timing values

Timing values are broken down into several sections.

Image omitted: ClientTransactionTimingDiagram.png
The variables in this diagram are defined as follows:
VariableDescription
start_timeDate 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_timeDate 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_timeTime in ms spent by the server processing the transaction. The server reports this value to the client.
load_completion_timeDate 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:

LabelElementDescriptionCalculation
Response Timeclient_response_timeOverall 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 Timeclient_server_timeTime the server takes to process the transaction.server_time
Network Timeclient_network_timeTime 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 Timebrowser_timeTime 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

Parent Topic:Client transaction timings