All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs

Remove unused JavaScript to reduce bytes consumed by network activity

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

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

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)

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

This is the largest contentful element painted within the viewport

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

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

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

Deprecated APIs will eventually be removed from the browser

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Remove unused JavaScript to reduce bytes consumed by network activity

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)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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/).

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

This is the largest contentful element painted within the viewport

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs

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

Deprecated APIs will eventually be removed from the browser

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