Share this page

# Web Page Diagnostics graphs

This topic describes each of the Web Page Diagnostics graphs.

In this topic:

## Web Page Diagnostics graph

The Web Page Diagnostics graph provides you with performance information for each monitored web page in your script. You can view the download time of each page in the script and its components, and identify at what point during download time problems occurred. In addition, you can view the average download time of each page and its components.

Item | Description
--- | ---
Purpose | 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.
X-axis | Elapsed time from the beginning of the scenario run.
Y-axis | The download time (in seconds) for each web page in the download process.
Tips | 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.
Diagnostic Options | 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

### Uses

Use the Diagnostic graphs and measurements in the following ways:

- Determine the average download time during the scenario execution, and see when the network or server problems occurred.

- Determine the stage during which the download of a specific page was the longest.

- Determine the time (Time to First Buffer) during the scenario at which the download of a specific image file was the longest.

- Determine the time during the scenario at which the download of a specific component was the longest.

- Display the download time (over time) for a specific page as an area graph.

## Page Component Breakdown graph

This graph displays the average download time (in seconds) for each web page and its components.

Item | Description
--- | ---
Purpose | Show the average download time for each web page and sub component. For example you can display a pie chart comparing the download time for the weather and finance components of your news site, or compared to main page.
Tips | To ascertain which components caused the delay in download time, you can break down the problematic URL by double-clicking it in the Web Page Diagnostics tree. To isolate problematic components, it may be helpful to sort the legend according to the average number of seconds taken to download a component. To sort the legend by average, click the Graph's Average column.
Note | The graph can only be viewed as a pie.

## Page Component Breakdown (Over Time) graph

This graph displays the average response time (in seconds) for each web page and its components during each second of the load test scenario run.

Item | Description
--- | ---
Purpose | 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.
X-axis | The elapsed time from the beginning of the scenario run.
Y-axis | The average response time (in seconds) for each component.
Tips | 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.

## Page Download Time Breakdown graph

This graph displays a breakdown of each page component's download time.

Item | Description
--- | ---
Purpose | 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.
Breakdown options | 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.

## Page Download Time Breakdown (Over Time) graph

The graph displays a breakdown of each page component's download time during each second of the load test scenario run.

Item | Description
--- | ---
Purpose | 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.
X-axis | Elapsed time from the beginning of the scenario run.
Y-axis | Time (in seconds) taken for each step in the download process.
Tips | 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.
Notes | 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.

## Page Download Time Breakdown graph breakdown options

The Page Download Time Breakdown graph breaks down each component by DNS resolution time, connection time, time to first buffer, SSL handshaking time, receive time, FTP authentication time, client time, and error time.

These breakdowns are described below:

Name | Description
--- | ---
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.

## Time to First Buffer Breakdown graph

This graph displays each web page component's relative server/network time (in seconds) for the period of time until the first buffer is successfully received back from the web server.

Note: This graph is relevant only when the load generator does not use a proxy to connect to the application under test. If the load generator is connected through a proxy, this graph shows only the proxy latency—not the application's latency.

Item | Description
--- | ---
Purpose | If the download time for a component is high, you can use this graph to determine whether the problem is server- or network-related.
Tip | 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.
X-axis | Specifies the name of the component.
Y-axis | Shows the average network/server time (in seconds) for each component.
Measurements | 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 | 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.

## Time to First Buffer Breakdown (Over Time) graph

This graph displays each web page component's server and network time (in seconds) during each second of the load test scenario run, for the period of time until the first buffer is successfully received back from the web server.

Note: This graph is relevant only when the load generator does not use a proxy to connect to the application under test. If the load generator is connected through a proxy, this graph shows only the proxy latency—not the AUT latency.

Item | Description
--- | ---
Purpose | 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.
X-axis | Elapsed time from the beginning of the scenario run.
Y-axis | Average network or server time (in seconds) for each component.
Measurements | 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.
Note | 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.

## Client Side Breakdown (Over Time) graph

This graph displays the client side breakdown of each transaction during each second of the load test scenario run. Using the graph, you can track which transactions on the client side were most problematic, and at which point during the scenario the problem occurred.

- To isolate the most problematic transactions, it may be helpful to sort the legend window according to the average number of seconds taken for the transaction to run. To sort the legend by average, double-click the Average column heading.

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

Axis | Description
--- | ---
X-axis | The elapsed time from the beginning of the scenario run.
Y-axis | The average response time (in seconds) for each transaction.

## Client Side JavaScript Breakdown (Over Time) graph

This graph displays the client side breakdown of each JavaScript transaction during each second of the load test scenario run. Using the graph, you can track which JavaScript transactions on the client side were most problematic, and at which point during the scenario the problem occurred.

Tip:

- To isolate the most problematic transactions, it may be helpful to sort the legend window according to the average number of seconds taken for the transaction to run. To sort the legend by average, double-click the Average column heading.

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

Axis | Description
--- | ---
X-axis | The elapsed time from the beginning of the scenario run.
Y-axis | The average response time (in seconds) for each transaction.

## See also

## Downloaded Component Size graph

This graph displays the size of each web page component.

Item | Description
--- | ---
Purpose | Shows the size of each web page component. Using the graph, you can compare the sizes of the various components of your main website. Large components may be causing a delay in downloading. To reduce download time, try reducing the size of the problematic component.
Note | The web page size is a sum of the sizes of each of its components. The Downloaded Component Size graph can only be viewed as a pie graph.

## Uploaded Component Size graph

This graph displays the number of kilobytes that were sent for each web page component that was uploaded.

Item | Description
--- | ---
Purpose | Shows the number of kilobytes sent for each web page component. Each segment of the pie chart shows each component's percent of the total size of all uploaded components. If the graph shows that one of the uploaded components contains more kilobytes than all others, you may need to reduce the size of that component.
Note | The web page size is a sum of the sizes of each of its components. The Uploaded Component Size graph can be viewed only as a pie graph.

## See also

- Web Page Diagnostics

- Web Page Diagnostics overview

https://admhelp.microfocus.com Professional Performance Engineering,VuGen 8942
Tips to improve your search results... OpenText™ Professional Performance Engineering Help Center OpenText™ Professional Performance Engineering Help 26.1-26.3 All View Local Help Center View Online Help Center Version: