TechnSols
Advertisement

PWA Readiness Checker

Check PWA readiness online free with PWA Readiness Checker. Test manifest, service worker, HTTPS and icons, no install or sign-up needed.

Be the first to rate this tool

Paste a manifest JSON, or enter a manifest URL, then press Check Manifest.

What Is PWA Readiness Checker?

PWA Readiness Checker is a free online tool by TechnSols that checks whether a website is ready to install as a Progressive Web App, and gives a clear pass or fail verdict. It checks the manifest, the service worker, HTTPS, the icons, and the display mode, and lists each item as passed or failed.

Advertisement

An installable web app is a big promise: it sits on the home screen, opens like an app, and works offline. But installability has several requirements, and missing just one of them hides the install prompt completely, with no error shown to the user. A developer can spend hours guessing whether the manifest, the icons, or the service worker is at fault. This checker tests every requirement in one place, using the same rules browsers use, and its verdict names the exact item that failed. The Learn PWA guide from Google explains what makes a web app installable in the first place.

It is different from the live PWA Manifest Inspector, which validates a pasted manifest only. A valid manifest is just one requirement, and a site can have a perfect manifest yet still fail to install. This checker looks at the whole picture: manifest, service worker, HTTPS, icons, and display mode together. Two honest limits apply: the manifest is pasted in by hand, and a manifest URL is fetched only when the browser allows it, because other sites may block the read. The live checks cover this site only. Everything runs in your browser, and nothing is uploaded anywhere.

How To Use PWA Readiness Checker?

Using the checker takes less than a minute. There is no software to install and no account to make. Paste the manifest, enter the site address, and read the verdict. If the layout must also fit every screen, the Responsive Design Tester previews the page at many screen sizes.

Step 1: Paste Your Manifest

Copy the contents of your web app manifest file and paste it into the manifest box. The checker reads the name, short name, icons, display mode, start URL, theme colour, and background colour, and marks each field as present or missing. A manifest that will not parse is reported at once, with the error shown.

Step 2: Enter Your Site Address

Enter the address of a manifest file, or leave the field empty and check the pasted manifest only. A manifest URL is fetched only when the site allows this page to read it; a blocked fetch is reported honestly and clears the old results. The live checks of HTTPS, the service worker, and the display mode always describe this site, not the entered address.

Step 3: Read The Pass Fail Verdict

Read the verdict at the top, which counts the passes and failures, then the list of checks below it. Each failed check carries a one line hint that says how to fix it. Fix the first failure, run the check again, and repeat until every item passes and the verdict turns green.

The whole check is quick because each test runs in the browser, with no scan and no waiting. If a feature the PWA needs is missing from the browser, the Browser Feature Detector lists what this browser supports.

Why Check PWA Readiness Online?

Install prompts are silent about failure. When a requirement is missing, the browser simply never shows the install button, and the user has no idea an install was even possible. That silence costs installs, and it costs them invisibly, because no one reports a button they never saw. A readiness check turns that silence into a list, so the fix is obvious. Browser audits no longer give PWA installability its own score, which is why a dedicated check still earns its place. The Progressive Web Apps pages from MDN describe each requirement the browser checks before it offers an install.

Catch Install Problems Before Users Do

Every failed install is a user who never comes back to try again. Testing before launch finds the missing icon size or the broken service worker while there is still time to fix it. A pass here is a strong sign, but the final proof is the install prompt appearing on a real device, because install rules differ slightly between browsers. If the PWA also sends alerts, the Web Notification Tester sends a real test notification to this browser.

Prove Installability To A Client

A client who paid for a PWA wants proof that it installs, not a promise. The verdict page is that proof: a green pass for the manifest, the service worker, HTTPS, the icons, and the display mode, all in one view. It can be shared as a screenshot in a handover, and re-run any time the site changes.

Fix The Small Gaps That Block Install

Most install failures are small: one icon size missing, a display mode set to browser, or a start URL that points nowhere. Each one is a one line fix, but only when you know which line it is. The failed items list names them one by one, so the work becomes a short checklist instead of a long hunt through documentation.

What Can You Do With PWA Readiness Checker?

The checker fits any job where installability needs proving, fixing, or auditing. These are the jobs it handles best.

Check A New PWA Before Launch

Run the checker on a new PWA before the launch announcement goes out. Paste the manifest, enter the address, and confirm every item passes. A launch with a green verdict means the install button appears for users on day one, instead of a quiet failure found a week later. If the PWA must also copy text or links, the Clipboard API Tester checks whether copy and paste work here.

Find The Missing Icon Size

Browsers need icons in specific sizes, and a manifest with only one size fails the icon check even when the app looks fine. The checker lists the icon sizes it found and the ones it needs, so the missing size can be made and added. A maskable icon is the one the system may crop to fill a shaped icon slot, so it needs safe space around the artwork. This is the most common fix on real PWAs, and the one that wastes the most time when it is guessed at.

Confirm HTTPS And Service Worker

Installability needs HTTPS and a registered service worker, and both are easy to break with a server change. A site that moved hosts or changed its certificate can lose HTTPS, and a bad deploy can unregister the worker. Current Chrome no longer demands a service worker with a fetch handler before it offers an install, but an app without one cannot open offline, so the checker still treats the worker as a required check. The checker confirms both in seconds, so a broken deploy is caught before users notice. If the PWA also offers a share button, the Web Share API Tester checks whether sharing works in this browser.

Quality And Settings

The checker tests the manifest, the service worker, HTTPS, the icons, and the display mode, and reports a pass or fail for each one. It shows the verdict first, then the full list of checks with reasons, so the fix is always clear. There is nothing to configure before the first check, because the manifest box and the address field are the whole tool.

Advertisement
  • Manifest check for name, short name, icons, display, start URL, and colours.
  • Service worker check for this site, with its registration state shown.
  • HTTPS check for this site, with the live result shown.
  • Icon check for 192 and 512 pixel icons, including the maskable icon.
  • Clear pass or fail verdict, with a reason for every failure.

The checks re-run on every submit, so a fix can be verified at once without reloading the page. If the server itself needs a look, the HTTP Header Checker shows the headers the server sends for any URL.

How PWA Readiness Checker Works

The tool runs entirely in your browser and tests each requirement directly. It parses the pasted manifest and checks every field the browser needs, it reads the service worker registration and the display mode for this site, and it checks whether this site runs over HTTPS. It checks the icon sizes and purposes the manifest declares, but it does not fetch the icon files themselves. The verdict is green only when every check passes. If a page shows a broken picture instead of an icon, the Broken Image Checker finds every broken image on a page.

Two honest limits are worth knowing. First, the manifest is pasted in by hand, so the tool checks the manifest you paste, not one it fetches itself. Second, URL checks work only for same origin or CORS enabled URLs, because the browser blocks cross origin reads from arbitrary third party URLs, and no browser tool can work around that. The checker does not test screenshots, shortcuts, or the display override field, and it cannot prove an offline page loads; that needs a real offline test on the device.

The verdict also reflects the browser you run it in, because install rules differ slightly between Chrome, Edge, Firefox, and Safari. A pass in one browser is a strong sign, but the final proof is the install prompt appearing on a real device. Test on the browser your users actually use, and the verdict will match their experience.

Privacy

Everything you check stays in your browser. PWA Readiness Checker runs on your own computer, and nothing you do is uploaded to a server, stored, or shared with anyone. No file is ever uploaded, and the tool does its job and shows the answer, and that is all it does.

Because no account is needed, there is no name, email, or history tied to what you do. Closing the tab ends the session, and the browser clears the check from memory. That is the same protection on every tool here: your work stays yours, and nothing about it is kept, shared, or sold.

Tips

A few habits make PWA Readiness Checker work smoother, whether this is your first PWA check or your five hundredth.

  • Fix the first failure, then re-run the check.
  • Include 192 and 512 pixel icons, plus a maskable icon.
  • Set the display mode to standalone, not browser.
  • Test on the browser your users actually use.
  • Re-check after every deploy that touches the worker.

When every item passes and the verdict is green, the check is done. If the site logs errors during the install test, the Website Error Log Viewer shows the errors a page produces.

More Tools For The Same Job

These tools handle the same kinds of jobs: web apps, manifests, headers, and checking whether a site works as it should.

FAQ

Common questions about checking PWA readiness online, answered plainly.

Is PWA Readiness Checker By TechnSols Free?

Yes, PWA Readiness Checker by TechnSols is completely free to use, with no account, no sign-up, and no usage limit. You can check readiness as often as you like, and everything runs in your browser, so nothing is uploaded or stored anywhere.

What Makes A Site Installable?

A site is installable when it runs over HTTPS, has a valid manifest with a name and icons, registers a service worker, and sets a display mode. The checker tests each of these and shows a pass or fail for every item, so you can see exactly which requirement is missing.

Why Did My PWA Fail The Check?

Most failures come from a missing icon size, a manifest field with a wrong value, no service worker, or a page served over plain HTTP. The verdict lists each failed item with its reason, so fix the first failure, then run the check again until every item passes.

Can It Check Another Website?

It checks a URL only when the site allows it, because browsers block cross origin reads from other sites. Same origin URLs and CORS enabled URLs work, while other third party URLs are blocked by the browser. Paste the manifest instead, and the manifest checks always work.

Does It Test The Service Worker Offline?

It confirms a service worker is registered and reports its state, but it cannot prove offline pages load without a real offline test. Turn off the network on the device, reload the site, and check that the page still opens. That live test, with this checker, proves the PWA works offline.

Paste the manifest, enter the address, and read the verdict. A PWA that passes every check shows its install prompt to real users, and one that fails tells you exactly which line to fix.

Follow TechnSols on Google
Add TechnSols as a preferred source to see more of our tools in Google Search.
Add to Preferred Sources
Advertisement