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

Optimized images load faster and consume less cellular data

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

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

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

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

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

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

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

Minifying CSS files can reduce network payload sizes

These DOM elements contribute most to the CLS of the page

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

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

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)

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

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

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

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

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

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

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

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

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

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

Optimized images load faster and consume less cellular data

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

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

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

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

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

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

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), or have enough space around them, to be easy enough to tap without overlapping onto other elements

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

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

Minifying CSS files can reduce network payload sizes

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

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)

This is the largest contentful element painted within the viewport

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

These DOM elements contribute most to the CLS of the page

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

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

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

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

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

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

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

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

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

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

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