A long cache lifetime can speed up repeat visits to your 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/).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 Contentful Paint marks the time at which the first text or image is painted

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

Largest Contentful Paint marks the time at which the largest 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

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

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

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

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)