Web Page Diagnostics graphs

This graph enables you to determine at what point during scenario execution a network or server problem occurred, that may have affected access to the web page.

Elapsed time from the beginning of the scenario run.

The download time (in seconds) for each web page in the download process.

• Choose a page in the Select Page to Break Down drop-down box.
• To isolate the most problematic components, you can sort the legend window according to the average number of seconds taken to download a component. To sort the legend by average, double-click the Average column heading.

You can choose one of the following options to drill down on the results. For sample graphs, see below.

• Download Time - as a bar graph
• Component (Over Time) - as a line graph
• Download Time (Over Time) - as an area graph
• Time to First Buffer (Over Time) - as an area graph

Show the average response time for each web page and sub component per second for each transaction. Using this graph, you can track which sub components were most problematic, and at which point during the scenario the problem occurred.

The elapsed time from the beginning of the scenario run.

The average response time (in seconds) for each component.

• To isolate the most problematic components, it may be helpful to sort the legend window according to the average number of seconds taken to download a component. To sort the legend by average, double-click the Average column heading.

• To identify a component in the graph, you can select it. The corresponding line in the legend window is selected.

Shows whether slow response times are being caused by network or server errors during web page download.

Using this graph, you can demonstrate how much the receive time, connection time, or first buffer time account for the time taken to download the main page of your website.

If you break down the results, you can isolate the components with the longest download time, and analyze the network or server problems that contributed to the delay in response time.

For example your breakdown may show that the receive time accounted for a large portion of the download time. In this case, you know that the receive mechanism needs to be improved.

For breakdown options, see Page Download Time Breakdown graph breakdown options.

Note: Each measurement displayed on the page level is the sum of that measurement recorded for each page component. For example, the Connection Time for your site is the sum of the Connection Time for each of the page's components.

Shows at what point during scenario execution, did the network or server problems occur.

For example, your graph might show that the First Buffer and Receive time remained high throughout the scenario, while the DNS Resolution time decreased during the scenario.

Elapsed time from the beginning of the scenario run.

Time (in seconds) taken for each step in the download process.

To isolate the most problematic components, you can sort the legend window according to the average number of seconds taken to download a component. To sort the legend by average, double-click the Average column heading.

• Each measurement displayed on the page level is the sum of that measurement recorded for each page component. For example, the Connection Time for www.cnn.com is the sum of the Connection Time for each of the page's components.

• When the Page Download Time Breakdown (Over Time) graph is selected from the Web Page Diagnostics graph, it appears as an area graph.

DNS Resolution

Displays the amount of time needed to resolve the DNS name to an IP address, using the closest DNS server. The DNS Lookup measurement is a good indicator of problems in DNS resolution, or problems with the DNS server.

Connection

Displays the amount of time needed to establish an initial connection with the web server hosting the specified URL. The connection measurement is a good indicator of problems along the network. It also indicates whether the server is responsive to requests.

First Buffer

Displays the amount of time that passes from the initial HTTP request (usually GET) until the first buffer is successfully received back from the web server. The first buffer measurement is a good indicator of web server delay as well as network latency.

Note: Since the buffer size may be up to 8K, the first buffer might also be the time it takes to completely download the element.

SSL Handshaking

Displays the amount of time taken to establish an SSL connection (includes the client hello, server hello, client public key transfer, server certificate transfer, and other—partially optional—stages). After this point, all the communication between the client and server is encrypted.

The SSL Handshaking measurement is only applicable for HTTPS communications.

Receive

Displays the amount of time that passes until the last byte arrives from the server and the downloading is complete.

The Receive measurement is a good indicator of network quality (look at the time/size ratio to calculate receive rate).

FTP Authentication

Displays the time taken to authenticate the client. With FTP, a server must authenticate a client before it starts processing the client's commands.

The FTP Authentication measurement is only applicable for FTP protocol communications.

Client Time

Displays the average amount of time that passes while a request is delayed on the client machine due to browser think time or other client-related delays.

Error Time

Displays the average amount of time that passes from the moment an HTTP request is sent until the moment an error message (HTTP errors only) is returned.

If the download time for a component is high, you can use this graph to determine whether the problem is server- or network-related.

Break down your site's main URL to view the time to first buffer breakdown for each of its components. For example, your graph may show that the time to first buffer breakdown is almost all network time.

Specifies the name of the component.

Shows the average network/server time (in seconds) for each component.

• Network time is defined as the average amount of time that passes from the moment the first HTTP request is sent until receipt of ACK.

• Server time is defined as the average amount of time that passes from the receipt of ACK of the initial HTTP request (usually GET) until the first buffer is successfully received back from the web server.

• Each measurement displayed on the page level is the sum of that measurement recorded for each page component. For example, the network time for www.cnn.com is the sum of the network time for each of the page's components.

• Because server time is being measured from the client, network time may influence this measurement if there is a change in network performance from the time the initial HTTP request is sent until the time the first buffer is sent. The server time displayed, therefore, is estimated server time and may be slightly inaccurate.

• The graph can only be viewed as a bar graph.

You can use this graph to determine when during the scenario run a server- or network-related problem occurred.

Using this graph, you can break down your web site's main URL to view the time to first buffer breakdown for each of its components.

Elapsed time from the beginning of the scenario run.

Average network or server time (in seconds) for each component.

• Network time is defined as the average amount of time that passes from the moment the first HTTP request is sent until receipt of ACK.

• Server time is defined as the average amount of time that passes from the receipt of ACK of the initial HTTP request (usually GET) until the first buffer is successfully received back from the web server.

Note: Because server time is being measured from the client, network time may influence this measurement if there is a change in network performance from the time the initial HTTP request is sent until the time the first buffer is sent. The server time displayed, therefore, is estimated server time and may be slightly inaccurate.

• Each measurement displayed on the page level is the sum of that measurement recorded for each page component. For example, the network time for https://www.anysite.com/ is the sum of the network time for each of the page's components.

• When the Time to First Buffer Breakdown (Over Time) graph is selected from the Web Page Diagnostics graph, it appears as an area graph.

The elapsed time from the beginning of the scenario run.

The average response time (in seconds) for each transaction.

The elapsed time from the beginning of the scenario run.

The average response time (in seconds) for each transaction.