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

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

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

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

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

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

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

Minifying CSS files can reduce network payload sizes

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

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

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

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

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

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs

Minifying JavaScript files can reduce payload sizes and script parse time

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

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

Deprecated APIs will eventually be removed from the browser

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

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

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

If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP

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

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)

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

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

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

Support for third-party cookies will be removed in a future version of Chrome

These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)

This is the largest contentful element painted within the viewport

Optimized images load faster and consume less cellular data

Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required

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)

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

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

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

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

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

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

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

Minifying JavaScript files can reduce payload sizes and script parse time

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

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

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

Support for third-party cookies will be removed in a future version of Chrome

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

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

Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required

Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements

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

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

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

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

Minifying CSS files can reduce network payload sizes

Deprecated APIs will eventually be removed from the browser

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

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

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

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

These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)

Optimized images load faster and consume less cellular data

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)

This is the largest contentful element painted within the viewport

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)

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

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

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

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs

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

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