M MurmTools

Service Worker: a heavy request count that mostly stays first-party

A service worker is a script a website installs in your browser that keeps running when the page is closed. It sits between the page and the network, so it can serve files from a local cache, keep a web app working offline, sync data in the background and deliver push notifications. Sites install one deliberately; it is a sign that someone treated the site as an application rather than a document. This index found a service worker on 286 of the 5,294 sites measured, 5.4% of the corpus, and the pages it found them on have an unusual profile: a lot of network traffic aimed at very few third parties.

Third-heaviest in requests, tenth of thirteen in companies

The median site running a service worker made 51 requests during the measured load. Against the thirteen technologies broken out in this index, that ranks 3rd on request volume, where rank 1 is the heaviest.

The same median page reached only 5 distinct companies, which ranks 10th of 13 on that measure, and 1 classified tracker, which ranks 9th of 13. So the traffic is near the top of the set while the number of separate organisations behind it sits near the bottom. That gap is what a service worker is built to produce: it intercepts and replays requests, and a cache that answers from the site's own origin generates request volume without adding anyone new to the page.

95.5% of these sites made contact before a banner could be answered

273 of the 286 sites reached a third party inside the opening window — the stretch that ends where a visitor could first have read a banner and answered it. That share ranks 4th of the 13 technologies here, with rank 1 the highest. The median first contact landed at 593 ms; the earliest single site in the group reached out at 80 ms.

The median number of companies first contacted after that window had closed is 0. The index measures that per site and takes the median of the result; it is not the difference between two other medians. For the median service-worker site, the third-party contact list is complete before the visitor has done anything.

The banner mix leans hard on the advertising framework

Consent software was detected on 117 of the 286 sites. The tool seen alongside most often was an IAB TCF framework banner, on 76 sites. OneTrust followed on 34, then CookieYes and Cookiebot on 2 each, Usercentrics on 1 and Iubenda on 1. One page can run two of these at once, so those are sightings, not slices of the 117.

TCF is the advertising industry's own consent framework, which encodes a visitor's choices into a string that bidders read. Its lead here is worth noting precisely because the pages themselves are not ad-heavy by company count: five companies at the median is a light page. What that suggests is two different populations sharing one technology — app-like sites that installed a worker for offline behaviour, and large commercial publishers that installed one and also sell inventory.

Two populations, visible in the named sites

reddit.com reached 5 companies, all 5 inside the window, first contact at 279 ms with no banner detected. twitch.tv reached 5 with 3 inside the window at 721 ms behind a TCF banner. amazon.co.uk contacted 4 companies, all 4 inside the window, at 172 ms, and amazon.de the same 4 with all 4 inside, at 272 ms — both behind TCF banners. soundcloud.com is the busiest of the group at 15 companies, 11 of them inside the window, first contact at 228 ms behind OneTrust. t-mobile.com reached 26 companies but only 6 inside the window, at 951 ms.

The opposite pattern shows up clearly in a cluster of Russian-language properties. vk.com contacted 6 companies with none of them inside the window and first contact at 3,653 ms. userapi.com: 6 companies, none early, at 3,153 ms. vkontakte.ru: 6 companies, none early, at 2,854 ms. vk.ru breaks with its siblings — 6 companies with 5 inside the window at 1,488 ms. A first contact after three seconds usually means the page rendered its own content from cache before it went looking for anyone else, which is exactly what a service worker makes possible.

The lightest entries are ampproject.org with 1 company at 776 ms and amazonalexa.com with 3, all inside the window, at 914 ms.

Why request count is the wrong number to worry about

Fifty-one requests sounds like a lot, and on this group it mostly is not a privacy figure. A cached image fetched through a worker is a request; so is a font and a background sync. The measure that maps onto exposure is how many separate organisations a page reached, and on that measure a service-worker page is quieter than most technologies in this index.

What the corpus records is timing and destination, not payload.

Highest-ranked sites where this was seen
SiteCompaniesBefore consentFirst contact
reddit.com55279 ms
vk.com603653 ms
soundcloud.com1511228 ms
userapi.com603153 ms
vk.ru651488 ms
twitch.tv53721 ms
amazon.co.uk44172 ms
ampproject.org11776 ms
vkontakte.ru602854 ms
amazon.de44272 ms
t-mobile.com266951 ms
amazonalexa.com33914 ms
Consent tools seen on these sites
ToolSites
IAB TCF consent tool76
OneTrust34
CookieYes2
Cookiebot2
Usercentrics1
Iubenda1

The six most common are listed. The remaining 1 of 117 sites with a banner carry something outside that six. One tool is recorded per site, so these counts never overlap.

Questions

What does a service worker do?

It is a script the site registers in your browser that runs independently of any open tab. It can intercept network requests and answer them from a cache, keep the site usable offline, sync data in the background and receive push notifications.

Does having a service worker mean a site tracks more?

Not in this index. The median site with one reached 5 companies, which ranks 10th of the 13 technologies broken out here, where rank 1 is the highest. Its request count is high, but requests served from a local cache do not reach a third party.

How many sites here run one?

286 of the 5,294 measured, or 5.4%. Detection is based on what the page registered during a single load from one location, with no banner clicked and no return visit, so a worker installed later in a session would not be counted.

Why do some of these sites take three seconds to contact anyone?

The measurement does not record why. A page that renders from its own cache first has no need to reach the network early, and several sites in this group show first contact after 2.8 seconds. This index can show the delay but not the reason for it.

Check any page yourself MurmStack is the tool that produced these figures. Free, two permissions, no host access.
Add to Chrome — free