P-y.tm

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

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

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

Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. 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.

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

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.

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.

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. 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.

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 More

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. 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.

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.

A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. 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.

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.