The total time spent on monitoring a page, that is, from the monitor beginning to the end of the monitoring.
The basic page is the plain text HTML file returned by the web server.
When monitoring a page, the total time of network transaction.IE browser using the WINDOWS network layer (winInet) to communicate with and server. The metrics include DNS time, Establish a connection time, SSL handshake time, redirection time, time to request, time to receive the first packet, content download time, and close connection time
Through the domain name resolution service (DNS), resolving domain name into the IP address time-consuming. For example, www.tingyun.com resolved to 42.62.56.35.After a domain name resolution occurs, the WINDOWS operating system will cache the result of this operation. When the monitoring node resolves the same domain name again, WINDOWS will return the result of this cache to the monitoring node, and the corresponding time value may be zero.
In the process of browsing a page, including the elements in the page, the total time for DNS resolution.
The time it takes for the browser and the web server to establish a TCP / IP connection.When the element is downloaded, the browser may keep the connection based on the results returned by the server, rather than completely closing the connection. When the monitoring node establishes a connection with the same server again, the connection will be multiplexed, and the corresponding time may be zero.Note: This metric is the first two handshake time of the TCP / IP connection three handshake (from IE to send TCP packet SYN to the server to return TCP packet SYN ACK time), the third handshake time (from IE to send TCP Packet ACK to the server to receive this TCP packet) is not included.
In the process of browsing a page , including elements in the page, the total time to establish a connection.
IE browser and WEB server to establish a secure socket layer (SSL) connection time.After the TCP / IP connection is established, a Secure Sockets Layer (SSL) connection may be established based on the needs of the web server , such as the URL using https protocol. As with TCP / IP connections, SSL connections may also be connected and multiplexed by the same server, and the corresponding elapsed time may be zero.
Redirection technology can be divided into two categories, one is the client redirect, one is the server-side redirect. This metric does not include client redirection time.When the IE browser through a Web site to access the Web server, the server may notify the IE browser that this URL has been replaced by other web sites, the server will return to IE browser new URL, the browser then continue to visit the new site, which is Server redirection.Redirection time is from receipt of request that WEB server redirects the request to the first element requested by WEB.
The time it takes for IE browser sending an HTTP request.Note: The time that the last packet of HTTP request transacting and arriving WEB server is not included. When an HTTP request contains a relatively small amount of data, for example, only one element download (GET) request, issuing the request time is usually relatively short. When an HTTP request contains a relatively large amount of data, such as upload file (POST) request, this request will be divided into multiple packets by WINDOWS network layer (winInet) to send to the WEB server. Each packet will notify the IE browser to continue to send the next packet only after the each packet received by WEB server, so the request time will be relatively long.
The time it takes from IE browser sending an HTTP request to the first packet received that returned by the web server.This metric contains the transmission time of the last packet on the network when the HTTP request was sent, the time the server responds to the request, and the transmission time of the first packet responded by the server on the network.
When monitoring a page, the sum of the time pieces of the network transaction did not occur.This metric includes the initial memory allocation of browser memory, parsing downloaded packets, page displays, and so on.Note: When the IE browser to resolve data packets and other operations and network communication at the same time, this time is not included in the client time.
Monitoring a page, from the view point of page, the time consuming that IE browser receiving the first non-first packet returned by WEB server.
The total number of network traffic bytes returned from the web server in a browsing page process. This metric contains the number of bytes of the HTTP protocol header, representing the network traffic that actually occurred.
When downloading an element within a page, such as the image element, the css element, the number of bytes returned from the web server.Note: This metric does not contain the number of bytes of the HTTP protocol header, so when the server does not enable HTTP compression, the total number of bytes downloaded by all elements in the page will be slightly smaller than the total number of bytes downloaded. The web packets returned by the web server are compressed via HTTP and IE browser will extract the original network data packets. This metric refers to the size of the extracted elements. The grand total number of bytes downloaded in the page is much larger than the total number of bytes downloaded.
The basic page is the plain text HTML file returned by the web server.The number of bytes downloaded in the basic page is the total number of bytes of the plain text HTML document.
Download speed = page total download bytes / network layer time
Download speed = page total download bytes / network layer time
The total number of bytes of the elements contained in the first screen main page displayed by IE browser.
The number of elements downloaded from the web server during a page process.
The total number of elements contained in the first screen main page displayed by IE browser.
The time it takes during IE browser displaying the first screen.The definition of the first screen is 800X600 pixel size as the standard.The time is to start timing from the beginning of the monitoring, to the IE browser page shows the height of up to 600 pixels and this area has the content.When the monitored page is relatively simple, all displayed height is also below 600 pixels, the first screen height to take the actual height of the page.
While a page browsing process, including the elements in the page, the total number of DNS resolution occurred.
While a page browsing process, including the elements in the page, the total times of establishing connections.
While a page browsing process, the number of DOM elements downloaded from the web server.DOM = Document Object Model,document object model. DOM elements can be understood as an identification of various objects in a page , such as a picture, a form, a line of a table .Note the difference between the number of pages and the number of objects.
The number of errors that elements occur in page.
The number of elements loaded by the browser after the onLoad event.
The time at which browser starts displaying the page, starting with the current page to start the event.
Users can customize the time on the page, using external.log (1013, "10 | ms") function to trigger. For example, a user can define an event that is triggered after an important UI control is loaded on the page. The start viewing time of the current page is the starting point of the time.
When switching between the two homologous pages, the time point on which the previous page began to unload. The start viewing time of the previous page is the starting point of the time. The time is 0 when there is no previous page.
When switching between the two homologous pages, the time point on which the previous page finished unloading. The start viewing time of the previous page is the starting point of the time.
The time that the browser starts processing Dom content of the current page. The start viewing time of the previous page is the starting point of the time.
The user can start interacting on the current page, such as clicking and scrolling the page. The start viewing time of the current page is the starting point of the time.
The time that the browser starts processing DOMContentLoaded events. The start viewing time of the current page is the starting point of the time.
The time that the browser ends processing DOMContentLoaded events. The start viewing time of the current page is the starting point of the time.
The time that the browser starts processing loading DOM content of the current page. The start viewing time of the current page is the starting point of the time.
The time that the browser starts processing onLoad time, starting with the start viewing time of the current page.
The time that the browser finishes processing onLoad time, starting with the start viewing time of the current page.