31780252.com

Lists the toplevel main thread tasks that executed during page load.

Collection of useful page vitals.

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. Learn more about the Round Trip Time.

Collects all available metrics.

The last screenshot captured of the pageload.

Used for treemap app

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. Learn more about server response time.

Lists the network requests that were made during page load.

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

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

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. Learn more about tap targets. Tap targets are too small because there's no viewport meta tag optimized for mobile screens

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. Learn more about legible font sizes. Text is illegible because there's no viewport meta tag optimized for mobile screens.

A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found

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.

A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

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

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document contains a `doctype` that triggers `limited-quirks-mode`

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

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

If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn how to size content for the viewport. The viewport size of 1203px does not match the window size of 412px.

A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` 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 about Service Workers.

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

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 about manifest installability requirements.

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

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 how to make links accessible.

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

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

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