← all guides
Privacy & Sovereignty

Why your site doesn't need 40 trackers

The average website quietly loads dozens of third-party trackers before a visitor reads a single word. Most site owners have no idea they're there — and almost none of them are necessary. Here's what they do, what they cost, and what to do instead.

Open the developer tools on a typical small-business website, click the network tab, and reload the page. You'll usually see something that surprises people: the site didn't make one request to one server. It made dozens — to ad networks, analytics platforms, social-media pixels, font services, tag managers, and "customer experience" tools you've never heard of. Many sites fire off thirty, forty, fifty separate third-party requests just to show you a homepage.

None of that is load-bearing. The site would work fine without almost all of it. So how did it get there — and why should you care?

Where the 40 trackers come from

Nobody sits down and decides to add forty trackers. They accumulate, one well-meaning decision at a time:

Every one of those had a reason. But nobody ever does the subtraction. The trackers only ever get added, never removed, and a year later the site is hauling around a surveillance payload heavier than its actual content.

A year later the site is hauling around a surveillance payload heavier than its actual content.

What they actually cost you

This isn't just a philosophical problem. Trackers have real, measurable costs — to you, the site owner, before we even get to your visitors.

Slower
Every third-party script is a separate network request that blocks or delays your page. Trackers are a leading cause of sluggish sites.
Riskier
Each external script is code you don't control running on your site. If a tracker is compromised, so are your visitors — through you.
Liable
Privacy laws increasingly treat hidden tracking as something you must disclose and get consent for. Forty silent trackers is forty risks.

The speed tax

Search engines rank slow sites lower, and visitors abandon them. The irony is sharp: the analytics tools people install to grow their traffic are often the very thing slowing the site down enough to lose it. You can be paying — in lost visitors — for the privilege of being surveilled.

The trust tax

People increasingly check. Browsers now show tracker counts. Privacy extensions display a number in the corner. When a potential customer sees that your "small local business" site is feeding forty data brokers, it doesn't read as sophisticated — it reads as careless, or worse.

What your visitors pay

The people who land on your site never agreed to be the product. But a tracker-laden site quietly hands their behavior — what they read, how long they stayed, what device they're on, often enough to identify them — to companies they've never heard of, for purposes they'll never see. They came to read about your services. They left a data trail sold to the highest bidder.

You can run a perfectly successful website without doing that to the people who visit it. Most site owners simply were never shown the alternative.

What a clean site looks like instead

Here's the part nobody tells you: you can have almost everything those tools promised — without the surveillance.

The honest substitutes

  • Want to know your traffic? Privacy-respecting, self-hosted analytics count visits without fingerprinting people or shipping data to third parties.
  • Want fast fonts? Serve them from your own server — or use the system fonts already on every device. No request ever leaves for a font company.
  • Want a contact path? A plain form or a direct email does the job without a third-party widget that tracks every visitor.
  • Want to run an ad sometime? You can add a single pixel for a campaign and remove it when it's done — instead of leaving forty embedded forever.

The clean version isn't a sacrifice. It's faster, safer, cheaper to run, easier to keep compliant, and more trustworthy to the people who matter. The "default" surveillance build is the compromise — most people just never realized they were making it.

The clean version isn't the sacrifice. The surveillance build is the compromise — most people never realized they were making it.

How to find out what your site is doing right now

You don't need anyone's permission to look. Right now, on any site you own:

  1. Open your browser's developer tools (right-click → Inspect, or F12).
  2. Click the Network tab.
  3. Reload the page.
  4. Look at how many different domains your one page is talking to.

If it's more than a small handful, your site is doing things you probably never asked it to. That's not a disaster — it's just information. And it's the first step to taking your site back.

When you're ready

Want this done for you?

Auditing what's leaking and handing you back a clean, fast, private site you fully own is exactly the work I do. No surveillance baked in, no lock-in, verifiable in your own network tab.

See privacy & hardening services →