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

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

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

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

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

Descriptive link text helps search engines understand your content

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

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

This is the largest contentful element painted within the viewport

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

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

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)

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

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

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

Preload the image used by the LCP element in order to improve your LCP time

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

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

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

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

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

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

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

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

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

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

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

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 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

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

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

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

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

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

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

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

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

Descriptive link text helps search engines understand your content

Largest Contentful Paint marks the time at which the largest 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

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

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

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

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 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

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

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