N11.com

Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.

Redirects introduce additional delays before the page can be loaded. Learn more.

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

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

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Optimized images load faster and consume less cellular data. Learn more.

Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.

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 more.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more

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

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.

To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

This is the largest contentful element painted within the viewport. Learn More

These DOM elements contribute most to the CLS of the page.

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. 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 servedover 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.

Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.

Image display dimensions should match natural aspect ratio. Learn more.

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more

The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the `pagehide` or `visibilitychange` events instead. Learn More

A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more.

A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.

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 servedover 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.

Screen reader users rely on frame titles to describe the contents of frames. Learn more.

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.

Low-contrast text is difficult or impossible for many users to read. Learn more.