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

Remove unused JavaScript to reduce bytes consumed by network activity

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

This is the largest contentful element painted within the viewport

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

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

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

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

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

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers

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

Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size

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

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

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

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)

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

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

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

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

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

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

Optimized images load faster and consume less cellular data

Minifying CSS files can reduce network payload sizes

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

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

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

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

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

Serve images that are appropriately-sized to save cellular data and improve load 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

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

Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Optimized images load faster and consume less cellular data

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

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

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

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

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

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

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

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

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

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

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

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

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers

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)

Remove unused JavaScript to reduce bytes consumed by network activity

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

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

Minifying CSS files can reduce network payload sizes

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

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

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

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