Site Health Reports
Descriptions for each report are as follows:
Status Codes by Page
The Status Codes by Page report gives you insight into the different page code statuses on your site. The Selection Summary shows high level information about each portion of the report and includes the number of pages with No Response, 200:OK status codes, and others, such as 301 and 404 codes. Additional information around status codes can be found below.
This class of status code indicates the client must take additional action to complete the request, such as reload a different page. Many of these status codes are used in URL redirection. A browser may carry out the additional action with no user interaction only if the method used in the second request is GET or HEAD. A user agent may automatically redirect a request. A browser should detect and intervene to prevent cyclical redirects.
4xx: Client Error
The 4xx class of status code is intended for situations in which the client seems to have erred. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents should display any included entity to the user.
5xx: Server Error
The server failed to fulfill an apparently valid request. Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has encountered an error or is otherwise incapable of performing the request. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and indicate whether it is a temporary or permanent condition. Likewise, user agents should display any included entity to the user. These response codes are applicable to any request method.
Page Load Time
This report shows the length of time it takes for pages to load within the audit. While there are several definitions of page load time, the definition we use is as follows:
The time it takes (in seconds) for the URL requested from our servers to send the request to the DNS, get matched up with the actual IP address of the pages being scanned, make the connection with the host server, and our server receiving the initial document..
The report is divided into five separate sections where pages that load in a specific time frame are placed: 0-3 seconds, 3-6 seconds, 6-10 seconds, 10-20 seconds, and 20+ seconds. According to the best practice and industry standard, pages should load around three seconds. The Selection Summary on top shows Total Pages and Average Load Time. To filter results, click on any bar on the graph.