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

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

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

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

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

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

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)

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

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

These DOM elements contribute most to the CLS of the page

Redirects introduce additional delays before the page can be loaded

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

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

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

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

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

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

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

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

This is the largest contentful element painted within the viewport

To set budgets for the quantity and size of page resources, add a budget.json file

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

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

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

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

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

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

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)

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

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

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

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

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

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

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

To set budgets for the quantity and size of page resources, add a budget.json file

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

This is the largest contentful element painted within the viewport

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

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

These DOM elements contribute most to the CLS of the page

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

If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP

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

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

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

Redirects introduce additional delays before the page can be loaded

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

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