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

Remove unused JavaScript to reduce bytes consumed by network activity

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

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

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

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

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

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

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

Animations which are not composited can be janky and increase CLS

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

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

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

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

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

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

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

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)

Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement

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

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

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes

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

This is the largest contentful element painted within the viewport

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

Minifying JavaScript files can reduce payload sizes and script parse time

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

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

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

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

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

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

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

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

Minifying JavaScript files can reduce payload sizes and script parse time

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

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

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

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)

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

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

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

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

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

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

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

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

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

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

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

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

Remove unused JavaScript to reduce bytes consumed by network activity

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

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

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

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

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

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

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

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes

Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement

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

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

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

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

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

Optimized images load faster and consume less cellular data

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