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

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

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

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

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

Minifying JavaScript files can reduce payload sizes and script parse time

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

Minifying CSS files can reduce network payload sizes

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

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

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

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

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

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

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

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

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

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

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)

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

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

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

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

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

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

Optimized images load faster and consume less cellular data

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

Remove unused JavaScript to reduce bytes consumed by network activity

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

Serve images that are appropriately-sized to save cellular data and improve load time

A fast page load over a cellular network ensures a good mobile user experience

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

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

This is the largest contentful element painted within the viewport

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

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

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

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

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

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 Meaningful Paint measures when the primary content of a page is visible

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

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

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

Serve images that are appropriately-sized to save cellular data and improve load time

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

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

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

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 fast page load over a cellular network ensures a good mobile user experience

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

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

Remove unused JavaScript to reduce bytes consumed by network activity

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

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

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

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

Optimized images load faster and consume less cellular data

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

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

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

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

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

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

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

Minifying JavaScript files can reduce payload sizes and script parse time

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

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

Minifying CSS files can reduce network payload sizes

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

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

This is the largest contentful element painted within the viewport

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