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)

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

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

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

Remove unused JavaScript to reduce bytes consumed by network activity

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

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load

This is the largest contentful element painted within the viewport

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

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

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

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

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

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

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/).

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

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

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

Optimized images load faster and consume less cellular data

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

Descriptive link text helps search engines understand your content

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

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

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

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

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

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