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

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

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

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

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

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)

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

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

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

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

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

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

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

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

Minifying JavaScript files can reduce payload sizes and script parse time

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

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

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

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

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

Animations which are not composited can be janky and increase CLS

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)

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

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

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

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

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)

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

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

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

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

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

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

Minifying JavaScript files can reduce payload sizes and script parse time

Animations which are not composited can be janky and increase CLS

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

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)

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

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

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

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

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

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

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

This is the largest contentful element painted within the viewport

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

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

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