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

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

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

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

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

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

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

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

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

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

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

Minifying JavaScript files can reduce payload sizes and script parse time

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

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

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

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

Minifying CSS files can reduce network payload sizes

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

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

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

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

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

Animations which are not composited can be janky and increase CLS

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

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

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

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

Minifying CSS files can reduce network payload sizes

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

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

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

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

This is the largest contentful element painted within the viewport

Minifying JavaScript files can reduce payload sizes and script parse time

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

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

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

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

Animations which are not composited can be janky and increase CLS

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

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

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

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

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

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

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

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

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)