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 Packet (also known as first byte) for that object. Overloaded web servers often have a long First Byte time.
For transactional protocols, this is the percentage of software service operations completed in a time shorter than the performance threshold. For SMTP and transactionless TCP-based protocols, this is the percentage of monitoring intervals in which user wait time per kB of data was shorter than the threshold value.
Byte limit exceeded errors
The number of byte Limit errors. The byte limit error occurs when the attempt to download a page or object was blocked because the reported size of the object was greater than the current limit.
The average number of bytes downloaded for the pages per test.
The total number of bytes downloaded for pages.
The total number of downloaded bytes.
The 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 Dynatrace Performance Network 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 an "ACK" packet from the server. The elapsed time between transmitting the SYN to the server and receiving the ACK response is the Initial Connection time.
The average number of connections established for pages per test.
Total number of connections established for pages.
Content match errors
The number of errors caused by the content not matching the condition defined for the page or object.
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.
The time it takes to translate the host name (for example, www.gomez.com) into the IP address (for example, 188.8.131.52). The Dynatrace Performance Network Agent performs this translation by using the Internet's standard Domain Name Service (DNS).
The number of failing page objects within the tests.
The number of unsuccessful attempts to access a page within a test.
HTTP client errors
The number of HTTP client errors.
HTTP server errors
The number of HTTP server errors.
The average number of hosts associated with the page.
Total number of hosts associated with the page(s).
Number of 200 objects
The total number of page objects with a return code of 200-299.
Number of 300 objects
The total number of page objects with a return code of 300-399.
Number of 400 objects
The total number of page objects with a return code of 400-499.
Number of 500 objects
The total number of page objects with a return code of 500-599.
Number of objects
The number of tested page objects, including successful and failing objects.
Number of pages
The number of tested pages.
Number of tests
The number of test executions.
The average number of objects downloaded per page.
The total number of downloaded page objects.
Objects with network errors
The total number of page objects with network related errors.
Objects with server errors
The total number of page objects with server related errors.
The percentage of successful pages vs all pages.
Page response time
The average time it took the page to produce a response for the given request.
The number of pages tested.
Pages executed (failed)
The number of tested pages reported as failed.
Pages executed (slow)
The number of tested pages reported as slow.
The average client-side processing time.
Total time required to download a complete web page and its objects. For full object tests, response time is the time, as measured in seconds, from when a user clicks on a link to the time that the Web page is fully downloaded. For HTML-only tests, it is the time, as measured in seconds, from when a user clicks on the link to the time when the root object is downloaded. Response time encompasses the collection of all objects that make up a page including third-party content on off-site servers, graphics, frames, redirections, and so on. For an operation flow (a series of interactive operations on several web pages), the response time is measured from the start of the operational flow (the moment a user clicks on a link) to the end of the operational flow (the content from the last web page content is downloaded.)
Time it takes to establish a Secure Socket Layer (SSL) connection and exchange SSL keys.
Socket time-out errors
The number of errors caused by no response to the attempts to open a TCP connection to the server.
The number of successfully tested page objects.
The number of successful attempts to access a page within a test.
The percentage of successful tests vs all tests.
User script errors