User actions web view

The User actions web view displays 100 most recent user actions of the selected System Profile and application in the current time scope.

If you drilled down from the Visits web view, only actions from the particular visits are displayed.

User actions web view
User actions web view

Click the user action to expand it and view detailed information about it. Click Visits details to open the visit, containing this action, click Show waterfall, to display the waterfall chart of the action.

Waterfall chart

The Waterfall chart shows timings for all the resources loaded for a selected user action. This lets you see at a glance exactly how the page loaded, resource loading with respect to performance metrics, and what resources have the biggest impact on page load performance.

The top bar in the page load timeline at the top of the waterfall provides a quick view of contribution to the overall page load time. Click it to see contribution details, a count of the PurePaths in the user action, and a link to analyze all of the action's PurePaths.

You can use the waterfall to easily identify resource loading bottlenecks.

Select the bar of any resource in the waterfall to see the following for that resource:

  • A link to the view the loaded resource.
  • General load time and resource sizing information.
  • Resource timing form performance measures.

Note that detailed W3C resource timing metrics are not available for cross-origin resources.

User action timings

The following measures are used to chart the duration of specific steps in the load action process.

Measure Description Definition in terms of W3C specification
DNS Time spent resolving domain names. window.performance.timing.domainLookupEnd - window.performance.timing.domainLookupStart
TCP Time spent establishing a socket connection from the browser to the web server. window.performance.timing.connectEnd - window.performance.timing.connectStart
SSL Time spent establishing a secure socket connection from the browser to the web server. window.performance.timing.connectEnd - window.performance.timing.secureConnectionStart
Redirect Time spent following HTTP redirects. window.performance.timing.redirectEnd - window.performance.timing.redirectStart
Request Time spent waiting for the first byte of the document response. window.performance.timing.responseStart - window.performance.timing.requestStart
Response Time spent downloading the document response. window.performance.timing.responseEnd - window.performance.timing.responseStart
TTFB Time at which the first byte of response from the server arrives at the client. window.performance.timing.responseStart
Network consumption Time taken to redirect, resolve the DNS, and establish the TCP connection. window.performance.timing.responseEnd - window.performance.timing.fetchStart - (window.performance.timing.responseStart - window.performance.timing.requestStart)
Server consumption Time spent receiving a request and sending the response back to the client. window.performance.timing.responseStart - window.performance.timing.requestStart
Processing time Time between DOM loading and Load event start. window.performance.timing.loadEventEnd - window.performance.timing.domLoading
App cache Time spent on checking relevant application caches. window.performance.timing.domainLookupStart - window.performance.timing.fetchStart
Frontend time Time spent in the browser on executing Javascript and rendering the page. User Action Duration - Server Consumption - Network Consumption
OnDomContentLoaded Time spent on executing OnDomContentLoaded handlers. window.performance.timing.domContentLoaded - window.performance.timing.domLoading
OnLoad Time spent on executing OnLoad handlers. window.performance.timing.loadEventEnd - window.performance.timing.loadEventStart
Callback Time spent on executing XHR callbacks. -
Visually complete Time at which all the content in the browsers visible area has been fully rendered. -
Speed index Time (in average) at which visible parts of the page are displayed. A lower Speed index means that most parts of the page are rendered very quickly. -
User action duration Time between initial user input and complete page load. Also includes load time of XHR requests initiated before loadEventEnd and load time of dynamic resources and script executions triggered by DOM modifications. -

Resource timing landmarks

The following measures chart the total time from a user clicking a link or button until the browser reaches a specific point in the resulting page loading process.

Measure Description Definition in terms of W3C specification
Request Start Time until the document request can be sent. This includes DNS, connect, SSL, and URL redirects. window.performance.requestStart - window.performance.navigationStart
Document Fetch Done In addition to everything until Request Start, this includes the time until the document (HTML) completely downloads from the HTTP server. window.performance.responseEnd - window.performance.navigationStart
Document Interactive Time until the document becomes interactive. This includes all steps completed for Document Fetch Done. window.performance.domInteractive - window.performance.navigationStart

The following example timeline illustrates the Previously described measures.

Visualization of Measures
Visualization of Measures

Analyze PurePaths and drilldown

The waterfall gives you full visibility from end user down to the Purepath.

When analyzing an action, you can either analyze PurePaths for the whole action or the Purepaths for an individual resource. To see all the Purepaths, click the top bar in the waterfall page load timeline, then click Analyze all PurePaths for an overall PurePath summary and to cycle through the list of PurePaths found for that action.

When analyzing a Purepath, you can click on any request in listed for the resource to see down to the method and code level data.

Click Analyze user action to switch back to the waterfall chart.

Click Analyze transaction flow to show the Transaction flow web view for this PurePath.

The menu button provides the following options:

  • Open in Client: Opens the PurePath dashlet in the Client, filtered to the PurePath. For this drilldown to work, the Client should be running at the time of click.
  • Export session: Saves the PurePath as the *.dts file. You can import it lately in the Client.
  • Analyze visit: Opens the Visit details web view, for the visit, containing the PurePath.