Progressive Web App Audits
What you'll learn: How Lighthouse evaluates whether your web app meets Progressive Web App (PWA) standards through automated checks of key technical requirements.
When you run a Lighthouse audit, one of the five categories it examines is "Progressive Web App." This section verifies that your site meets the baseline requirements to be installable and work reliably, even when network conditions are poor.
What Lighthouse Checks
Lighthouse's PWA audits focus on three fundamental pillars:
1. Web App Manifest
Lighthouse verifies that a valid manifest.json file exists and is properly linked. It checks for required fields like name, short_name, start_url, display, and icons of appropriate sizes (at least 192x192 and 512x512). Without a proper manifest, users cannot install your app to their home screen.
2. Service Worker
The audit confirms that a service worker is registered and active. It verifies that the service worker successfully intercepts at least one fetch event, proving it can manage network requests. Think of this like having a smart intermediary that can decide whether to serve content from cache or fetch it fresh.
3. Offline Capability
Lighthouse tests whether your app responds with a 200 status code when offline. It simulates a disconnected state to ensure your service worker provides some content—even if it's just a friendly "You're offline" page. This is the hallmark of a reliable PWA.
How the Score Works
Unlike the Performance score, PWA audits are largely pass/fail. Each requirement either succeeds or it doesn't. Lighthouse presents these as a checklist, making it clear which criteria you've met and which need attention.
Key Takeaway: Lighthouse's PWA audits systematically verify that your app has a manifest, an active service worker, and can respond when offline—the three technical foundations that make a web app "progressive."