Navigating Waterfall Charts for Page Load and Transaction Tests
Last updated
Last updated
ThousandEyes Page Load and Transaction tests provide a waterfall chart for insight into how a browser interacts with web page objects. This article explains how data is presented within waterfall charts.
ThousandEyes relies on Chromium, which prefers IPv6 if available, and otherwise falls back to IPv4. If you run browser synthetics tests on agents with “force IPv6” set as a policy, make sure that the target URL supports IPv6.
If the agent is set to force IPv6, but the target URL does not, you might see inconsistent DNS errors in the test view, where the “Transaction” or “Page Load” view layer looks successful, but the “HTTP Server” layer shows a DNS error.
This article contains screenshot views and instructions that reference “Classic” test views. ThousandEyes is in the process of introducing multi-service views that combine multiple test views into one multi-service view. See Multi-Service Views for more information.
A waterfall chart is a time-based representation of data that displays the relationship between events.
BrowserBot, the application that performs Page Load and Transaction tests, generates a .har file upon completion of each test. The .har file contains metrics about each object downloaded during the test. This information is then represented in the form of a waterfall chart.
Properly understanding results requires familiarity with the test types, the Document Object Model, and the ThousandEyes user interface. An introduction to each is provided below.
Page Load tests are navigated using a timeline pane and an informational pane. Selecting a single agent, from the agent drop-down menu, enables a waterfall chart that documents each object loaded by the agent's browser.
An explanation of how to navigate page load test results is available here.
An explanation of ThousandEyes test results is available here.
Transaction tests are navigated using a timeline pane and an informational pane. Selecting a single agent, from the agent drop-down menu, enables a waterfall chart that documents each object loaded by the agent's browser.
An explanation of ThousandEyes test results is available here.
Understanding waterfall charts requires familiarity with the Document Object Model.
Upon receiving a browser request for a web page, an HTTP server locates the site "Directory Index" file and provides an HTML formatted document to the requesting browser. HTML (HyperText Markup Language) instructs the browser regarding how information should be displayed.
The Document Object Model describes HTML structure as a series of objects called nodes. A diagrammed HTML document resembles an ancestral tree; hence the terms "parents" and "children" are used to describe the relationship between nodes. While some nodes, such as text and scripts, may be included within the root HTML document, others must include links to resources which a browser downloads separately.
Downloaded objects, such as javascript and css files, may in turn reference other objects that the browser must download to prior to page load completion.
These objects are often sourced from multiple domains.
Each Page Load Object requires an independently completed HTTP transaction.
Waterfall Charts provide metrics for the following HTTP transaction activities:
BLOCKED: The time that a browser waits for an already established connection to become available. Web browsers are designed to allow a maximum number of concurrent connections per domain. Blocking time means that the browser is waiting for other requests to complete and represents the time that is spent before a request is sent because other requests are being handled.
DNS: The duration to resolve a domain record to an IP address. By default, Browserbot does not cache DNS records at startup.
CONNECT: The time to establish a TCP handshake with the Target Server.
SSL: The duration of SSL/TLS negotiation.
SEND: The duration in which the browser successfully sends a request to the server.
WAIT: The duration between the completion of a browser's SEND request and receipt of the first byte of a server's response.
RECEIVE: The time between the first byte of the server response to the last byte of the data payload.
Aggregate Metrics include:
DOM LOAD TIME: Transaction time from the beginning of the first object load to the end of the final object load.
PAGE LOAD TIME: The time from the initial request to when the page is fully rendered. Redirect time is taken into account when determining total page load time.
The transaction test waterfall chart displays DOM load metrics for a target web page.
By default, the waterfall chart displays objects in chronological order. Selecting table headers will reorder rows by either Object Name, Domain, Response Code, Provider, Size, or Waterfall Chronology.
Hovering over a multi-colored download bar will display object and load metrics.
Hovering over the blue and red load completion markers will display aggregate load metrics.
If "save object headers" was selected under the test's advanced settings, a link to view headers will be included within the Waterfall "Response Code" column.
Selecting a header link opens a light-box which includes both the Request and Response Headers.
The transaction test waterfall chart displays DOM load metrics for each page loaded during a transaction test.
By default, the waterfall chart displays objects in chronological order. Selecting table headers will reorder rows by either Object Name, Domain, Response Code, Provider, Size, or Waterfall Chronology.
The Transaction test waterfall traverses multiple pages. A chronological view selector is used to focus on specific portions of the DOM load history.
Hovering over a multi-colored download bar will display object and load metrics.
Hovering over the blue and red load completion markers will display aggregate load metrics.
If "save object headers" was selected under the test's advanced settings, a link to view headers will be included within the Waterfall "Response Code" column.
Selecting the headers icon will open a light-box that includes both the Request and Response Headers.
In some cases, objects will not have Response Headers. One example of this is an object with the Cancelled designation. If there is no Response Code for an object, the word "Cancelled" is shown for an incomplete object. In the size field of the waterfall, a triangular logo with an exclamation point will appear and "Object Incomplete (cancelled)" will appear in the hover menu for that logo. Selecting the Header link will only show a Request Header. The Response Header section will not show information since there is none.
