case studies

A Shop Page Calls Five Other Sites Before Anyone Answers Its Cookie Banner

Picture the owner of a small clothing shop. She added a cookie banner because her web designer said the law needed one, and she assumes nothing goes out until a visitor clicks Accept. This case study is built on a made-up shop page that behaves the way many real ones do.

Open the product page in Watchkeeper and leave the banner alone. Before you’ve read the first line, the panel lists five other sites.

Watchkeeper on a shop’s product page with the cookie banner still unanswered at the bottom. The panel lists five other sites: an ad pixel, analytics, a chat widget, a font server and an ad partner, plus two cookies, two storage writes and a canvas read by the ad pixel.

The made-up shop from Watchkeeper’s case study pages, with the banner still waiting for an answer.

What Went Out

The analytics script loaded with the page and sent its page-view beacon straight away. It also left a visitor number in local storage, which shows up in the panel as a storage write by the shop itself, since the script runs inside the shop’s own page. The ad pixel fetched its image, drew some text on a hidden canvas and read it back, the panel’s “canvas by adpixel.example”. Then it called a partner of its own, partner-ads.example, which the shop’s code never mentions. The chat widget, in its frame from another site, wrote a key of its own. The font server saw every visit too, though only because the page uses its fonts.

None of this waited for the banner. The banner was just one more thing on the page.

What to Do With It

The useful next step is a saved report, sent to whoever built the site with one question: which of these should only load after “Accept all”? Here the likely answer is the analytics script, the ad pixel and the partner it calls, while the chat widget and the fonts can stay. After the change, opening the page again puts the old count beside the new one in the Last visit section, so the owner can see the fix work before any visitor does.

Watchkeeper can’t say whether a page meets the law where you live. It shows what the page does before anyone answers, which is the part the banner hides.

Try It

The shop is one of the made-up sites in Watchkeeper’s case study pages, served by a short Python script on your own machine. The quick start explains each line of the panel.