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

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)

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

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

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)

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

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

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

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

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

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

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

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 lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to 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

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

Redirects introduce additional delays before the page can be loaded

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

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

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

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

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

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

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

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

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

Redirects introduce additional delays before the page can be loaded

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

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

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

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

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

This is the largest contentful element painted within the viewport

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

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

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

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

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

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

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)

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)

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

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

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