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

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

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

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

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

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

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

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

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

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)

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

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

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

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

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

Minifying JavaScript files can reduce payload sizes and script parse time

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

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed

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

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

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

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

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

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

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

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

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

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

Minifying JavaScript files can reduce payload sizes and script parse time

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

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

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

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

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

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

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

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

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

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

Cumulative Layout Shift measures the movement of visible elements 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)

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

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

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

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

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed

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

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

This is the largest contentful element painted within the viewport

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

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

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