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

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

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds

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

Minifying CSS files can reduce network payload sizes

A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)

First Contentful Paint marks the time at which the first text or image is painted

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

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

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

Cumulative Layout Shift measures the movement of visible elements within the viewport

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

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

Largest Contentful Paint marks the time at which the largest text or image is painted

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

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load

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

First Meaningful Paint measures when the primary content of a page is visible

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

This is the largest contentful element painted within the viewport

Speed Index shows how quickly the contents of a page are visibly populated

These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)

The maximum potential First Input Delay that your users could experience is the duration of the longest task

Time to Interactive is the amount of time it takes for the page to become fully interactive

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

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

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

First Meaningful Paint measures when the primary content of a page is visible

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

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

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds

First Contentful Paint marks the time at which the first text or image is painted

Time to Interactive is the amount of time it takes for the page to become fully interactive

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

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

Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px

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

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

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

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

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

These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)

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

Largest Contentful Paint marks the time at which the largest text or image is painted

Minifying CSS files can reduce network payload sizes

Cumulative Layout Shift measures the movement of visible elements within the viewport

A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)

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

Speed Index shows how quickly the contents of a page are visibly populated

The maximum potential First Input Delay that your users could experience is the duration of the longest task

This is the largest contentful element painted within the viewport

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load