U888.one

This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element

Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.

Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

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

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

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

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

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. Learn more about efficient video formats

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.

A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.

Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.

Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

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

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding 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. Learn more about HTTPS.

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.