Webpage: http://www.johnhardy.com
Device: Desktop Computer
Region: United States East (Virginia)
Single Region Score
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. [Learn more about third-party cookies].
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content], where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. [Learn more about HTTPS].
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. [Learn more about this errors in console diagnostic audit]
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to reduce Javascript execution time].
Redirects introduce additional delays before the page can be loaded. [Learn how to avoid page redirects].
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. [Learn how to minimize third-party impact].
Serve images that are appropriately-sized to save cellular data and improve load time. [Learn how to size images].
Speed Index shows how quickly the contents of a page are visibly populated. [Learn more about the Speed Index metric].
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Descriptive link text helps search engines understand your content. [Learn how to make links more accessible].
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Third party code can significantly impact load performance. [Reduce and defer loading of third party code] to prioritize your page's content.
Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size]
Keep the server response time for the main document short because all other requests depend on it. [Learn more about the Time to First Byte metric].
Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining] can move these network requests out of the critical path.
A large DOM will increase memory usage, cause longer [style calculations], and produce costly [layout reflows]. [Learn how to avoid an excessive DOM size].
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to minimize main-thread work]
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript].
Deprecated APIs will eventually be removed from the browser. [Learn more about deprecated APIs].