Lighthouse PWA audits are deprecated, but the quality questions still matter
Do not confuse a deprecated audit surface with deprecated user expectations.
Why this matters
Chrome for Developers now shows a warning that PWA testing in Lighthouse is deprecated and points developers toward updated installability criteria and PWA documentation. That does not mean the underlying quality concerns vanished. Fast load, HTTPS, offline behavior, manifest validity, viewport correctness, fallback content, maskable icons, and cross-browser checks still shape user trust.
What changed
The old Lighthouse PWA section is now better read as a smoke-test checklist rather than an authority on final PWA qualification. That is healthy: marketplace quality should not be reduced to one score. It should combine automated checks, manual review, browser support, and user-facing clarity.
What builders should check
- Use Lighthouse for performance and obvious regressions, not as the only PWA verdict.
- Review installability against current browser guidance.
- Keep manual checks: cross-browser behavior, URL quality, and network-independent transitions.
- Treat maskable icons, theme color, and viewport as listing polish, not decoration.
- Document what was manually verified before publishing a listing.
OpenPWA angle
OpenPWA can turn this into an editorial advantage. Instead of repeating a single audit score, it can explain the actual readiness story: what passed automatically, what needs manual review, and what platform caveats remain. That is more useful than a badge.
Sources:
- Chrome for Developers: Lighthouse PWA audits