PWA Inspector
Local processing with network featuresAudit manifests, icons, installability, and common PWA issues
Source
URL mode sends this URL to CodingTool servers, which fetch the public page, its manifest, icons and a few scripts without cookies or login. Only inspect public pages.
Results show what a server can fetch anonymously. Login walls, bot protection, regional rules or client-side rendering can make a real browser see something different.
What it checks
PWA Inspector audits Web App Manifest members (name, start_url, scope, id, display, colors, icons, screenshots, shortcuts and handlers), icon candidates, installability signals, service-worker registration hints and offline signals. Each check is labelled Required, Important, Recommended or Optional, and optional members never count as failures.
Three modes
Paste manifest and Upload manifest run entirely in your browser with no network requests. Public URL mode sends the URL to CodingTool servers, which fetch the public page, manifest, a limited number of icons and scripts through a guarded fetcher that blocks private, internal and metadata addresses and enforces time, redirect and size limits.
Fixes and readiness score
Deterministic problems such as a missing start_url, display mode, id or scope get a suggested value and a patched manifest you can copy or download. Choices that need product or design input, such as theme colors or icon artwork, are listed without invented values. The readiness score is a transparent heuristic with a per-tier breakdown, not an official browser certification.
Limits
Remote inspection sees what an anonymous server request sees: login walls, bot protection and client-side rendering can hide the manifest link. Service-worker detection reads static script text, so it reports Detected, Not detected or Unable to inspect remotely instead of guessing, and it never treats a missing worker as non-installable. Browsers apply their own install criteria, which change over time.
