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)

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

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

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

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

These DOM elements contribute most to the CLS of the page

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

Optimized images load faster and consume less cellular data

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

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

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

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

First Contentful Paint marks the time at which the first 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

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

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

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

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

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

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

This is the largest contentful element painted within the viewport

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

Optimized images load faster and consume less cellular data

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

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

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

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

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

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

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

This is the largest contentful element painted 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

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

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

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

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

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

These DOM elements contribute most to the CLS of the page

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

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

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

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

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

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

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 Meaningful Paint measures when the primary content of a page is visible

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

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