Fast is a privacy feature

The very first guide in this series mentioned a "speed tax" — the quiet irony that the analytics tools people install to grow their traffic are often the very thing slowing the site down enough to lose it. This piece is that thread pulled all the way through, because it turns out the speed tax and the surveillance aren't two separate costs. They're one cost, billed twice.

Once you see why, every other guide in this series clicks into place. Fonts, trackers, analytics, consent banners, lock-in — they were never really about five different problems. They were about one: things added to your page that take something, and slow it down in the taking.

Why surveillance is slow by nature

A tracker isn't a passive observer. To watch a visitor, a script has to run — and it runs on the one lane that also has to draw your page and respond to every tap: the main thread. While a tracking script is executing, the browser can't do the work the visitor actually came for. The page is busy being watched.

It compounds, because surveillance scripts rarely travel alone and rarely stop working. They attach listeners that fire on every click, every scroll, every movement — reporting behavior long after the page has loaded. Each listener is a small toll on every interaction. The richer the surveillance, the heavier the drag. They are slow because of what they do, not by accident.

A tracker can't watch without running, and it can't run without making the visitor wait. Slowness isn't a side effect of surveillance. It's the shape of it.

The same script, charged twice

Here's the cleanest way to see it. Take any single third-party tracker on a typical site and ask what it does. It does two things at once — and both are costs to the people you're trying to serve.

You don't get to keep one cost and shed the other. They're welded together. Which is the good news hiding in plain sight: you don't get to keep one benefit and shed the other either. Remove the tracker for privacy's sake and the page gets faster in the same motion. Strip it for speed and your visitors stop being surveilled. One action, two repairs.

Why the clean site is just… fast

This is why a privacy-respecting site doesn't have to work at being fast — it's fast because there's nothing extractive left to slow it down. When the page is your content and little else, the main thread has nothing to fight. Nothing phones home, nothing blocks the first paint, nothing lags the first tap.

• Fewer scripts, faster paint. No tag manager, no pixel stack competing with your actual page for the visitor's first second.
• No listeners, snappier taps. Nothing fires on every scroll and click, so interactions stay instant instead of queuing behind a tracker.
• Less to download, lighter on weak connections. The visitor on a phone in a dead zone — often the one you most want to reach — gets a page that arrives.

Search engines reward this, because they're measuring exactly the responsiveness that surveillance erodes. But the ranking is a side effect. The real win is simpler and older: a page that respects the person waiting on it — their data and their time, which were always the same respect.

Watch it block, right now

You can see the main thread choke in your own browser. On any site — including your own:

1. Open your browser's developer tools (right-click → Inspect, or F12) and open the Performance panel.
2. Record a trace while the page loads, then stop it.
3. Look for the long blocks on the main thread — and check the labels. The biggest ones are usually named for trackers: a tag manager, an analytics library, a pixel, a chat widget.
4. Every one of those long blocks is a moment your visitor waited — and a moment they were being watched. The same moment.

Whatever you find, it's not a disaster — it's just information. It's the proof, in your own trace, that speed and privacy were never two projects. Fix one and you've fixed the other.