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

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

Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required

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

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

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

These DOM elements contribute most to the CLS of the page

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

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

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

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

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

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

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

Minifying JavaScript files can reduce payload sizes and script parse time

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

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

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

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

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

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

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

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)

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 marks the time at which the first text or image is painted

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

Optimized images load faster and consume less cellular data

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

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

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

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)

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

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

Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required

Minifying JavaScript files can reduce payload sizes and script parse time

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

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

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

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

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

This is the largest contentful element painted within the viewport

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

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

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

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

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

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

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

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

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

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

Minifying CSS files can reduce network payload sizes

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

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

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

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