Lighthouse  3.0.3
50
Progressive Web App
Progressive Web App
These checks validate the aspects of a Progressive Web App, as specified by the baseline PWA Checklist.
1 Does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
2 User will not be prompted to Install the Web App
Failures: No manifest was fetched, Service worker does not successfully serve the manifest's start_url, 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.
3 Does not redirect HTTP traffic to HTTPS
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS. Learn more.
4 Does not provide fallback content when JavaScript is not available
The page body should render some content if its scripts are not available.
Your app should display some content when JavaScript is disabled, even if it's just a warning to the user that JavaScript is required to use the app. Learn more.
5 Is not configured for a custom splash screen
Failures: No manifest was fetched.
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more.
6 Address bar does not match brand colors
Failures: No manifest was fetched.
The browser address bar can be themed to match your site. Learn more.
Additional items to manually check
3 audits
These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
1 Site works cross-browser
To reach the most number of users, sites should work across every major browser. Learn more.
2 Page transitions don't feel like they block on the network
Transitions should feel snappy as you tap around, even on a slow network, a key to perceived performance. Learn more.
3 Each page has a URL
Ensure individual pages are deep linkable via the URLs and that URLs are unique for the purpose of shareability on social media. Learn more.
Passed audits
5 audits
1 Page load is fast enough on 3G
A fast page load over a 3G network ensures a good mobile user experience. Learn more.
2 Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. 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.
3 Has a <meta name="viewport"> tag with width or initial-scale
Add a viewport meta tag to optimize your app for mobile screens. Learn more.
4 Registers a service worker
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.
5 Content is sized correctly for the viewport
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 more.
Not applicable
1 audits
1 The short_name won't be truncated on the homescreen
Make your app's `short_name` fewer than 12 characters to ensure that it's not truncated on homescreens. Learn more.