Toolsky

Free Online Tools & Utilities for Every Task.

PWA Compatibility Checker

Audit your website for Progressive Web App features.

What makes a PWA?

Security

HTTPS: A secure connection is required for Service Workers and installability.

Manifest

Web App Manifest: A JSON file that tells the browser how your app should behave when installed.

Capabilities

Service Worker: JavaScript that runs in the background for offline support and push notifications.

Mobile

Mobile Meta Tags: Essential tags that control scaling and appearance on mobile devices.

You added a manifest, registered a service worker, and your site still refuses to show an install prompt on anyone's phone. The frustrating part is that none of the pieces complain loudly when they are wrong — a missing icon size or a start URL that 404s simply makes the browser quietly decide your site is not installable. A PWA compatibility checker exists to remove that guesswork: you enter your site's URL, and it audits the page against the requirements browsers use before they treat a website as a Progressive Web App.

What a PWA Compatibility Audit Actually Checks

A Progressive Web App is an ordinary website that meets a set of technical criteria: it is served over HTTPS, it ships a web app manifest with the right fields, it registers a service worker, and it behaves reasonably on a phone-sized screen. When those boxes are ticked, browsers such as Chrome on Android can offer to install the site on the home screen, launch it in its own window without browser chrome, and let the service worker cache pages so parts of the site keep working on a flaky connection. This checker examines a live URL and reports which of those requirements are present, which are missing, and which are present but malformed — the difference between "no manifest found" and "manifest found, but it has no 512-pixel icon" is the difference between an afternoon of work and a two-minute fix.

The Signals This Checker Looks For

  • Secure context — whether the page loads over HTTPS, since service workers and install prompts are blocked on plain HTTP.
  • Manifest presence and validity — whether a manifest is linked from the page, loads without errors, and parses as valid JSON.
  • Required manifest fields — a name or short name, a start URL, and a display mode such as standalone or fullscreen.
  • Install icons — whether the manifest declares icons at the sizes browsers ask for, typically at least 192×192 and 512×512 pixels.
  • Service worker registration — whether the page registers a service worker that can respond to fetch events.
  • Mobile readiness basics — a viewport meta tag and theme colour, the small details that make the installed app feel finished.

How to Run a PWA Audit on Your Site

  1. Copy the full URL of the page you want to audit — the homepage is the usual choice, since that is where install behaviour is decided.
  2. Paste the URL into the checker and start the audit.
  3. Wait while the tool fetches the page and inspects its manifest, service worker and document head.
  4. Read the results list item by item, noting which checks pass and which fail or warn.
  5. Fix the failing items in your own code, theme or plugin settings, one at a time.
  6. Re-run the audit after each round of fixes to confirm the failures clear and nothing else broke.
  7. Finally, open the site on a real phone browser and confirm the install option appears as expected.

Where the Checker Earns Its Keep

Consider a small booking site that paid a developer to "make it an app" six months ago. The owner has never once seen an install prompt on her Android phone and assumes the feature silently died. An audit shows the manifest loads fine and the service worker is registered — but both declared icons return 404, because the files were moved during a redesign. Twenty minutes later the paths are corrected, the audit passes, and the install prompt appears. Pre-launch is the other classic moment: agencies run the check as part of their delivery checklist alongside an SSL checker, so certificate and PWA problems are caught before the client ever sees the site. It is also worth re-running after any platform migration, since moving hosts or switching themes is exactly when manifest links and service worker files get lost.

Gaps, Caveats and Misread Results

An audit is a snapshot of technical readiness, not a verdict on app quality. Passing every check does not mean your offline experience is good — a service worker that registers successfully might still cache almost nothing, and the checker cannot judge whether your cached pages are actually useful without a connection. Browser rules also differ: Chrome on Android is the most prompt-happy, while Safari on iOS has historically required users to add the site to the home screen manually through the share menu and applies its own storage limits. Treat a clean result as "eligible to be installed", then test the real behaviour on the devices your visitors actually use. If the audit reports a missing manifest but you are certain one exists, check that the link tag sits in the document head of the page you audited, not only on other pages.

Frequently Asked Questions About PWA Compatibility Checks

What makes a website count as a Progressive Web App?

At minimum: HTTPS, a valid web app manifest with a name, start URL and suitable icons, and a registered service worker. Beyond those installability basics, responsiveness and offline behaviour are what make a PWA feel like an app rather than a bookmark.

Why does my site pass the audit but show no install prompt?

Browsers apply their own engagement and timing rules on top of the technical criteria, and prompts differ by platform. Verify on Chrome for Android first, and check that the start URL itself loads without redirects or errors.

Do I need a service worker if my site works fine online?

For installability in Chrome, yes — a registered service worker with a fetch handler is part of the baseline criteria, even if it only caches a lightweight offline fallback page.

My manifest is linked but the audit says it cannot be read. Why?

Common causes are a wrong file path, the file being served with an error status, or invalid JSON — a single trailing comma will break parsing. If you are rebuilding the file, the PWA manifest generator produces a clean, valid manifest to compare against.

Does a PWA replace the need for a native app?

For content, booking and commerce sites it often does: no store approval, no separate codebase, and updates ship with your website. Hardware-heavy features and some platform integrations still favour native apps.

How often should I re-check compatibility?

After every redesign, theme change, plugin update or hosting move — the changes that typically break manifests and service workers — and otherwise once or twice a year as browser criteria evolve.

Can I audit a staging or password-protected site?

The checker has to fetch the page like a visitor. If the site requires a login or blocks outside requests, the audit may fail or see a login page instead of your app, so audit the public URL whenever possible.

From Audit Result to Working Install Prompt

Work the failing items from the top down, re-audit after each fix, and confirm on a real handset before you call it done. A short checklist, cleared methodically, is all that stands between most sites and a proper installable app.