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

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

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

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

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

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

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

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity

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

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity

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

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

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

Remove large, duplicate JavaScript modules from bundles 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

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

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

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

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

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)

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

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

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

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

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

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

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

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

Animations which are not composited can be janky and increase CLS

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

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

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

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

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

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

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

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

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

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

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

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity

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

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

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

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

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

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

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

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

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity

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

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

This is the largest contentful element painted within the viewport

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

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

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

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)

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