Latest Performance Report for:

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.

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

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

Redirects introduce additional delays before the page can be loaded.

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

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

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

This is the largest contentful element painted within the viewport.

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:

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

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.

Nothing to do here, good job!

Nothing to do here, good job!

No user timings and/or marks found.

Nothing to do here, good job!