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.

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

Consider using a plugin like WP Rocket to improve this audit in a few clicks »

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.

Consider using a plugin like WP Rocket to improve this audit in a few clicks »

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.

Consider using a plugin like WP Rocket to remove unused CSS with a few clicks »

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

Consider using a plugin like WP Rocket to significantly reduce server response time »

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.

Consider using a plugin like WP Rocket to improve these timings with a few clicks »

Nothing to do here, good job!

No user timings and/or marks found.

Nothing to do here, good job!