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

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

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

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

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

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

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

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

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

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

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

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

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

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

Serve images that are appropriately-sized to save cellular data and improve load 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

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 using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load

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

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

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

This is the largest contentful element painted within the viewport

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

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

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

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)

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 using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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