PWA Audit

A PWA (Progressive Web App) audit is the process of evaluating a web application against the technical requirements necessary for it to be recognizable and installable by modern browsers. This involves checking for a valid Web App Manifest, a registered Service Worker with offline capabilities, secure HTTPS hosting, and the presence of properly formatted icons.

Most web apps fail PWA audits due to simple configuration errors. The most common culprits are missing or invalid JSON syntax in the manifest.json file, failing to serve the app over a secure HTTPS connection, missing a fetch event handler in the Service Worker, or lacking the correct icon sizes (such as a 192x192px and 512x512px icon) required by Chromium browsers.

To pass the baseline Google Lighthouse PWA audit, your application must meet three non-negotiable criteria: it must be served over HTTPS, it must include a Web App Manifest with a name or short_name, start_url, display mode, and valid icons, and it must register a Service Worker that caches assets for offline functionality.

Apple's Safari browser on iOS does not fully adhere to the standard Web App Manifest specification used by Google Chrome and Android. Even if you score 100% on a standard PWA audit, iOS requires proprietary HTML meta tags (like apple-mobile-web-app-capable) and specific apple-touch-icon link tags to achieve a native look and feel on iPhones and iPads.

Manually fixing manifest syntax, writing caching strategies for Service Workers, and generating dozens of platform-specific icons can be tedious. You can bypass these errors entirely by using a platform like Progressier, which automatically generates a flawless Web App Manifest, provides a production-ready Service Worker, and handles all iOS compatibility tags dynamically.