PWA Validator
Check the core pieces of a Progressive Web App: secure delivery, manifest markup, app identity, icons, launch behavior, service worker registration and mobile metadata.
Check PWA readiness
The URL helps validate HTTPS and resolve relative paths. Direct page fetching only works when the site permits browser cross-origin access.
Scope: this is a practical static check, not a browser installation guarantee. Browser criteria differ and can change. Runtime behavior, offline caching, service-worker errors and platform-specific install prompts require testing in browser developer tools.
What the validator checks
| Area | What is reviewed |
|---|---|
| Secure context | Whether the supplied page URL uses HTTPS or a localhost development address. |
| Manifest link | Whether the page includes <link rel="manifest">. |
| Manifest content | Names, app ID, start URL, scope, display mode, colors and useful 192×192 / 512×512 icons. |
| Service worker | Whether the supplied HTML appears to register a service worker. |
| Mobile metadata | Viewport, theme color and Apple touch icon declarations. |
Minimum practical PWA setup
<link rel="manifest" href="/site.webmanifest">
<meta name="theme-color" content="#176b5b">
<meta name="viewport" content="width=device-width, initial-scale=1">
<script>
if ("serviceWorker" in navigator) {
navigator.serviceWorker.register("/service-worker.js");
}
</script>Related tools
Generate a web app manifest, check a manifest in detail, or inspect the page's metadata.