Optimized images load faster and consume less cellular data

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

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

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

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

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

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

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

Minifying JavaScript files can reduce payload sizes and script parse time

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

Minifying CSS files can reduce network payload sizes

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

This is the largest contentful element painted within the viewport

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

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

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

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

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)

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

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

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

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

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)

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

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

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

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

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)

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease 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

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

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

Optimized images load faster and consume less cellular data

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

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

Deprecated APIs will eventually be removed from the browser

Minifying CSS files can reduce network payload sizes

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

This is the largest contentful element painted within the viewport

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

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

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

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

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

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

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

Minifying JavaScript files can reduce payload sizes and script parse time

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

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

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)

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

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)

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

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

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

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

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

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

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

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

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

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

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

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

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