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

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

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

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

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

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

This is the largest contentful element painted within the viewport

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

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

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

Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy

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

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

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

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

These DOM elements contribute most to the CLS of the page.

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).

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

Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size

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

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

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

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

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

These DOM elements contribute most to the CLS of the page.

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).

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

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)

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

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

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

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

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

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

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

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

This is the largest contentful element painted within the viewport

Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy

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

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

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

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

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

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

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

Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size

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

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

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