Archived Performance Report for:

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

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

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

CDNs can give an equally fast web experience to your users across the globe.

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

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

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load.

Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance.

Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins.

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

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers.

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.

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.

Large network payloads cost users real money and are highly correlated with long load times.

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

Optimized images load faster and consume less cellular data.

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.

Keep the server response time for the main document short because all other requests depend on it.

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

Animations which are not composited can be janky and increase CLS.

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

Remove unused JavaScript to reduce bytes consumed by network activity.

HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push.

This is the largest contentful element painted within the viewport.

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

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.

Nothing to do here, good job!

No user timings and/or marks found.