Overview
The Page Summary Audit report will give you a snapshot of the health of the pages scanned in your Audit. It is also a great place to look up a specific URL for troubleshooting or analysis. You can look here for page load times to measure the performance of your site and page status codes to troubleshoot potential access issues with your Audit or identify broken pages across your site.
Summary Metrics
The summary metrics displayed include:
The # of pages scanned
The average page load time
The # of Broken Initial Pages
The # of Broken Final Pages
Pages with Broken Links
Web Vitals
Hover over each metric to view detailed explanations to help you analyze and interpret the results. Learn more about Web Vitals, their functionality, and their importance for your website.
Page Load Time
ObservePoint's page load metric is defined by Chrome. To manually test the load time for any page in the browser, open the Network tab in the Dev Tools and refresh the page. You will see a red load metric at the bottom of the page when all of the core resources have been loaded on the page.
Page Size
The size of a webpage is calculated by considering various elements, including HTML, CSS, JavaScript, images, and other resources. It includes the total file size of all these components that need to be downloaded by a user's browser to fully render the webpage. Factors like code efficiency, image compression, and external resource usage impact the overall size, affecting page load times.
Page Status Codes
Page status codes indicate whether or not ObservePoint (and your customers) are able to access your site.
Status Codes following the following categorization:
Informational responses (
100–199)Successful responses (
200–299)Redirects (
300–399)Client errors (
400–499)Server errors (
500–599)
Broken Pages
Broken pages are defined as pages with a 0, 400, or 500 level status code. These pages are inaccessible to users and make for a terrible customer experience. It may even put an abrupt end to a customer's Journey on your website. Make sure to identify broken pages and resolve them as quickly as possible. It's really important to analyze the parent URL where the link was found on. You can find the parent URL when you inspect a specific page in the Page Details report.
If you are surprised by the results of the Audit, test the page in a browser. If it renders with no issue, ObservePoint may be getting blocked by your website's security protocols. You'll want to discuss solutions internally with your IT teams and your ObservePoint Customer Success Manager.