Technical Root Cause Analysis

Service Workers are intended to be ephemeral (wake up, do task, sleep).

• The Bug: Poorly coded workers keep a "Keep-Alive" connection open to the server, polling for notifications every second.


• The Impact: This prevents the CPU from idling.


• The Fix: By blocking the network requests associated with these polls, SuperchargePerformance forces the worker to idle, saving your battery.




FAQ





What are service workers in Chrome?




Service workers are background scripts that web apps and extensions use for offline caching, push notifications, and background sync. They run in their own process and can consume CPU even when you're not interacting with the page.





Why do service workers use so much CPU?




Common causes: poorly written web app code that triggers frequent cache updates, extensions with aggressive background polling, and sites that abuse the service worker API for analytics or tracking. Chrome Task Manager (Shift+Esc) shows which service worker is consuming resources.





How do I stop service workers from draining CPU?




Identify the offending service worker in Chrome Task Manager, then either disable the extension or block the site's service worker registration. SuperchargePerformance's tab suspension prevents service workers in suspended tabs from running.





Common Service Worker Offenders





Not all service workers are equal. The worst CPU offenders:




• News sites (CNN, BBC, NYT) — register service workers for push notifications and offline reading. Even after you leave the page, the worker keeps checking for updates every few minutes.


• PWAs (Progressive Web Apps) like Twitter, Spotify Web, and Slack — their service workers handle caching aggressively. If you have 5 PWA tabs open, that's 5 service workers running independent cache maintenance loops.


• Ad networks — some ad scripts register their own service workers to cache ad assets. These are the hardest to identify because they don't show the site's name in Chrome Task Manager.


• Chrome extensions — every MV3 extension runs its own service worker. Extensions with frequent alarms or message passing (password managers, tab managers, ad blockers) contribute measurable CPU overhead.

How to Audit Service Workers