TruClient performance metrics

The following performance metrics can be recorded for TruClient scripts:

Metric Description
End to end transaction response time This includes the client time, such as browser rendering time.
Web page component breakdown Load times can be broken down by Web page and resource.
HAR TruClient can generate a standard HAR file in some configurations. If you have Network Virtualization installed and you replay a script in VuGen load mode, a HAR file is created. The pathname is <result path>/<group name>_<vuser ID>/<group name>_<vuser ID>.har.
Throughput

Number of bytes transferred between the browser and the server.
Hits

Number of HTTP requests sent from the client.
Connections

Number of connections opened by the browser to the server.

Note: Support for the Connections measurement will be discontinued in upcoming versions of TruClient.
DOM Interactive

Displays the average time per document, in milliseconds, from when the user agent starts establishing the connection to the server until the user agent sets the readiness of the current document to "interactive".
DOMContentLoaded Event duration

Displays the average time per document, in milliseconds, it takes to handle the DOM Content Loaded event (that is the time from when the event is sent to the page until all JS handlers complete handling the event).
Page Load Event duration

Displays the average time per document, in milliseconds, it takes to handle the Page Load event (that is the time from when the event is sent to the page until all JS handlers complete handling the event).
Client-Side Measurement Breakdown

Displays the average time per document, in seconds, it takes from Request Start to the following events:

  • First Buffer. Indicates the time immediately after the user agent receives the first byte of the response from the server, or from relevant application caches or from local resources.

  • First Paint. Indicates the time between navigation and when the browser renders the first pixels to the screen, rendering anything that is visually different from what was on the screen prior to navigation.

  • First Contentful Paint. Indicates when the browser renders the first bit of content from the DOM, providing the first feedback to the user that the page is actually loading.

  • Largest Contentful Paint. Indicates the render time of the largest image or text block visible within the viewport, relative to when the page first started loading.

  • Dom Interactive. Indicates the time immediately before the user agent sets the current document readiness to "interactive".

  • Dom Content Loaded Event Start. Indicates the time immediately before the user agent fires the DOMContentLoaded event at the document.

  • Dom Content Loaded Event End. Indicates the time immediately after the document's DOMContentLoaded event completes.

  • Dom Complete. Indicates the time immediately before the user agent sets the current document readiness to "complete".

  • Load Event Start. Indicates the time immediately before the load event of the current document is fired. It must return zero when the load event is not fired yet.

  • Load Event End. Indicates the time when the load event of the current document is completed. It must return zero when the load event is not fired or is not completed.

For details, see the LoadRunner Professional help.

Tip: You can identify a single activity in a business process in a script by using start and end transaction markers. Some metrics are only generated per transaction. In addition, most metrics are more meaningful when you know what action they are measuring.

Back to top

See also: