Every time the script associated with a web path is executed, it is considered a web test. Over time, the results of these web tests form the web path performance history charts, but details of the individual tests can also be viewed on the web test results page.

View web test results

To view the results of an individual web test:

  1. View the web path performance history for the web path you are interested in.
  2. Select a time period that includes the test you are interested in.
  3. Hover over either the End User Experience chart, the Milestone Breakdown chart, or the Apdex chart, and click the blue pip for the test you are interested in.
    • The web test page containing the following sections is displayed:
      • Timeline
      • JavaScript Errors
      • Resource list
      • Charts: Resource Timing, Performance, Domain, and Content

Using the web test results page

Once you have accessed the web test results page for the web test you are interested in, there are a number of ways to find the specific information you are looking for.

Select a section of the timeline

The data shown on the web test results page is based on the selected section of the Timeline at the top of the page. The selected section is indicated by two vertical black bars on the Timeline. By default, the entire Timeline is selected but this can be changed either by moving the selection bars manually or by choosing a milestone to view.

To change the selected section by moving the selection bars manually:

  1. Navigate to the web test results page you are interested in.
  2. On the Timeline, drag the left selection bar to the start of the selection.
  3. Drag the right selection bar to the end of the selection.
    • The results on the rest of the page are based on the section of the Timeline selected.

To change the selected section by choosing a milestone:

  1. Navigate to the web test results page you are interested in.
  2. On the Timeline, double-click the milestone you are interested in.
    • The selection bars surround the selected milestone.
    • The results on the rest of the page are based on the selected milestone.

Filter resources

Under the JavaScript Errors section of the web test results page is a list of resources downloaded by the web page or pages accessed by the script. This list can be filtered based on a search string, a predefined filter, or both.

To filter the resource list based on a search string:

  1. Specify the section of the script execution timeline you are interested in.
  2. In the Filter by… field, enter a case-sensitive search string.
    • Only the resources whose resource name contains the search string are listed.

To filter the resource list based on a predefined filter:

  1. Specify the section of the script execution timeline you are interested in.
  2. Select one of the pre-defined filters (All, HTML/Text, Javascript, CSS, Image, Flash, and Other).
    • Only the resources whose data type matches the filter are listed.

To filter the resource list based on a search string and a predefined filter:

  1. Specify the section of the script execution timeline you are interested in.
  2. In the Filter by… field, enter a case-sensitive search string.
  3. Select one of the pre-defined filters (All, HTML/Text, Javascript, CSS, Image, Flash, and Other).
    • Only the resources matching the search string and the filter are listed.

Sort resources

No matter how they are filtered, the resources can be sorted based on data in any of the columns in the resource list.

To sort the resource list:

  1. Specify the section of the script execution timeline you are interested in.
  2. Filter the resource list if desired.
  3. Click the heading of the column you want to sort by.
    • The resource list is sorted by the column you selected.
  4. Click the heading again to reverse the sort order.

View resource details

The resource list on the web test page provides some high-level information but additional information is available.

To view resource details:

  1. Specify the section of the script execution timeline you are interested in.
  2. Filter the resource list if desired.
  3. Click the resource you are interested in.
    • Resource details appear under the Headers tab.
    • Click the Timing tab to view detailed timing information.

Understanding the web test results page

The web test results page provides test execution details and is broken down by milestone. The results shown on the page are based on the section of the Timeline that is selected (see Select a section of the timeline). The main sections of this page include:

  • Timeline - shows the timeline for the web test execution including the relative time for each milestone and any subsequent processing. In addition, information for each milestone is listed.
  • JavaScript Errors - lists any JavaScript errors that occurred on pages accessed during script execution.
  • Resource list - is a list of all web page resources (resources used to build the web page) accessed during script execution and identifies resource name, the request method used, the response status, the type of resource, its size, how long it took to download (latency), and a timeline showing a breakdown of the download time. Hovering over this timeline provides detail on the resource acquisition. Note that resources can be downloaded in parallel.
  • Resource Timing chart - represents the percentage breakdown of time required to acquire the page resources for the selected part of the timeline into the following phases:
    • Blocking - the time spent in a browser queue waiting for a network connection.
    • DNS lookup - the DNS resolution time; time taken to resolve a domain name in the URL. The DNS server must “look up” the IP address associated with the domain name.
    • Connecting - the time taken to establish a TCP connection with the web server.
    • Sending - the time required to send an HTTP request to the web server.
    • Waiting - the time spent waiting for a response (the first byte of information received) from the web server.
    • Receiving - the time required to read the entire response (receive all information, first byte to last byte) from the web server.
  • Performance chart - shows the amount of script execution time associated with the network, the server, and the monitoring point’s internal web browser. Given that many operations are typically occurring in parallel, at a given point in time, if we are waiting on the network, we count it as network time. If we are not waiting on the network but are waiting on the server, we count it as server time. If we are not waiting on the network or the server, we count it as browser time.
    • Network - the amount of script execution time associated with the network. This is comprised of two parts: the time it takes to establish a connection and send the resource request to the server, and the time between when the server transmits the first byte of the response and when the browser receives last byte of the response.
    • Server - the amount of script execution time associated with the web server. This is the time between the server receiving the request and transmitting the response (calculated as the time the first byte of the response is received by the browser minus one way network latency).
    • Browser - the amount of script execution time associated with the browser. This is the time the monitoring point’s internal browser must wait for a network connection and the time it takes to render the page after all the content is received (though browser rendering begins after the first byte is received). It is the time not attributed to the network or server.
  • Domain chart - shows the number of bytes received from the servers listed.
  • Content chart - shows the number of bytes received by content type. The content type is a broad category that includes many similar data formats, determined by the mime-type of the resource.

For a given request, the timings found on the Resource Timing and Performance charts can be aligned as follows:

appview_latency_etc.png

In general, the information on the web test results page can be used to determine where the most time is being spent during script execution. If you are having performance issues, identifying the elements that most negatively affect performance enables you to determine where the largest efficiencies can be gained. Keep in mind that some of these activities occur concurrently so making them more efficient may not result in significantly faster page load times.