58.com

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

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

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

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

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

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

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

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. 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.

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

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

Meta descriptions may be included in search results to concisely summarize page content. Learn more.

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

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. 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 servedover 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.

Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more.

A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.

If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.

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

A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: 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.

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 servedover 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.

Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.

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