Te.eg

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. Learn more.

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

Optimized images load faster and consume less cellular data. Learn more.

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

Redirects introduce additional delays before the page can be loaded. Learn more.

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

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

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

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

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

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

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

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

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.

This is the largest contentful element painted within the viewport. Learn More

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. Learn more.

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

These DOM elements contribute most to the CLS of the page.

Descriptive link text helps search engines understand your content. Learn more.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.

The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the `pagehide` or `visibilitychange` events instead. Learn more

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more.

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more

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.

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

Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.

A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more. Expected publicId to be an empty string

For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.

A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.

A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched

The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.

The 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. Learn more.

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. Learn more.

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.

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.

Low-contrast text is difficult or impossible for many users to read. Learn more.