X86.org

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.

A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.

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

Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.

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.