태양촌.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.

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

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

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

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

Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Minifying CSS files can reduce network payload sizes. Learn more.

Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. 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

To set budgets for the quantity and size of page resources, add a budget.json file. 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.

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

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.

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.

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

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. 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.

If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.

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.

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.

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

If you're building a Progressive Web App, consider using a service worker so that your app can work offline. 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.

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.

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.

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.

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.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. 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.

Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.