Latest Performance Report for:

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

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

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

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

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

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

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.

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease 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.

This is the largest contentful element painted within the viewport.

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

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.