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

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

This is the largest contentful element painted within the viewport

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

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

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

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

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

Minifying JavaScript files can reduce payload sizes and script parse time

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

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

Minifying CSS files can reduce network payload sizes

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)

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

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

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

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

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

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

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

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

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

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

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

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

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

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

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

Minifying CSS files can reduce network payload sizes

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

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

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

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

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

Minifying JavaScript files can reduce payload sizes and script parse time

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

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

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

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

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

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

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load

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

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

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)

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

This is the largest contentful element painted within the viewport

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

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

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

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

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

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

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

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