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

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

Remove unused JavaScript to reduce bytes consumed by network activity

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

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

This is the largest contentful element painted within the viewport

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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)

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

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

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

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

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

Remove unused JavaScript to reduce bytes consumed by network activity

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

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

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

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

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

This is the largest contentful element painted within the viewport

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

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

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

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

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

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