Archived Performance Report for:

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

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.

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

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

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

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

Resources that may be contributing to render-blocking include:

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading.

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

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

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.

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

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.

This is the largest contentful element painted within the viewport.

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

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.

No user timings and/or marks found.