Availability (Test or Page)
Percentage of a test runs or pages during a specific period of time that failed to fully execute. Calculated as the number of successful test runs or pages divided by the total number of test runs or pages:
(Number of Successful Tests) / ((Number of Successful Tests) + (Number of Failed Tests))
(Number of Successful Pages) / ((Number of Successful Pages) + (Number of Failed Pages))
Time (in seconds) that it takes to connect to a web server across a network. After obtaining the target IP address by using the DNS Lookup, the Gomez Agent establishes a TCP connection with the device at that IP address. TCP connections are started by the agent's transmitting a special "SYN" packet and then receiving a "SYN" packet from the server. The elapsed time between transmitting the SYN to the server and receiving the SYN response is the Initial Connection time.
Time required to receive the content of a page or page component starting with the receipt of the first content and ending with the last packet received.
Time it takes, as measured in seconds, to translate the host name (for example, www.gomez.com) into the IP address (for example, 188.8.131.52). The agent performs this translation by using the Internet's standard Domain Name Service (DNS).
An object download fails when the agent was unable to download the specified objects due to one of the following: the agent connected to the server that the object allegedly resides on but was unable to download it; the agent could not find the server because the DNS lookup failed; the agent could not connect to the server for some reason.
Number of pages/steps within the selected transactions(s) that failed to load successfully during the selected timeframe. A page is considered failed when any of the following conditions exist:
- Number of objects that returned an HTTP 200 response status code is 0.
- Content match failure
- Byte limit failure
- Timeout failure
- User script failure
- Legend aggregation: Summation.
- Excessive 1st Byte Time – Time between the completion of the TCP connection with the destination server that will provide the displayed page's HTML, graphic, or other component and the reception of the First Byte for that object. Overloaded web servers often have a long First Byte time.
Number of 200 Objects
Number of objects that returned an HTTP 2xx response status codes. The 2xx status codes indicates the action by the client was received, understood, accepted, and processed successfully.
Number of 300 Objects
Number of objects that returned an HTTP 3xx response status codes. The 3xx status codes indicates that the client must take additional action to complete the request.
Number of 400 Objects
Number of objects that returned an HTTP 4xx response status code. The 4xx class of status code is for cases in which the client seems to have erred.
Number of 500 Objects
Number of objects that have returned an HTTP 5xx response status code. The 5xx status code indicates the server failed to fulfill an apparently valid request.
Number of Bytes
Number of bytes downloaded during the test.
Number of Connections
Number of connections during the test.
Number of Hosts
Number of unique hosts that are represented in all tests and pages returned in the One Chart result set.
Number of Internal Errors
Total number of response codes greater than or equal to 20000 for objects on the page.
Number of Network Errors
Total number of response codes between 10000 and 20000 for objects on the page.
Number of Objects
Number of objects downloaded during the test. An object is a single downloaded file such as HTML, a GIF image, a Java application, or a Shockwave file.
Number of Pages
Total number of pages/steps tested for the selected test(s) during the selected timeframe.
Elapsed time during performance measurement (usually end-to-end time).
Time it takes in seconds to establish a Secure Socket Layer (SSL) connection and exchange SSL keys.
Number of objects tested during the selected timeframe that were returned successfully.
Number of pages/steps within the selected transaction(s) that loaded successfully during the selected timeframe. A page is considered "successful" when all of the following conditions exist:
- Number of objects that returned an HTTP 200 response status code is greater than 0.
- Content match status is good
- Byte limit exceeded is good
- Timeout status is good
- User script status is good
- Legend aggregation: Summation.
For more information about metrics, see the documentation: