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

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

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

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

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

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)

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

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

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

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

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

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

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content 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

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

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

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

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

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

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

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

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

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

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)

These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)

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

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

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