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 reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

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

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

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

Largest Contentful Paint marks the time at which the largest 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)

Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size

Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy

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

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

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

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

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Minifying JavaScript files can reduce payload sizes and script parse time

A fast page load over a cellular network ensures a good mobile user experience

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

Descriptive link text helps search engines understand your content

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

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

Remove unused JavaScript to reduce 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

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

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).

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

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

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

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

Minifying CSS files can reduce network payload sizes

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

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

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

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

Optimized images load faster and consume less cellular data

This is the largest contentful element painted within the viewport

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Descriptive link text helps search engines understand your content

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

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

Image formats like JPEG 2000, JPEG XR, and WebP 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

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

Minifying JavaScript files can reduce payload sizes and script parse time

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

Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy

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

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

This is the largest contentful element painted within the viewport

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)

Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).

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

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

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes

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

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

A fast page load over a cellular network ensures a good mobile user experience

Optimized images load faster and consume less cellular data

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

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

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

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

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

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

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

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

Remove unused JavaScript to reduce bytes consumed by network activity

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