How many other servers is your WordPress loading from?
Published October 30, 2026
Open any WordPress site and it looks like it’s coming from one place. It usually isn’t.
When Site Doctor renders a page in a real browser, it notes every other server that page reaches out to — fonts from one company, analytics from another, a chat bubble, a maps embed, a reviews widget, a tag manager that then pulls in six more things on its own. We pulled that count across the roughly hundred sites we watch, and 79% of them were loading content from at least one server they don’t own.
That’s not a scandal on its own. One font host is fine. The problem is the tail.
The distribution
| External hosts on the page | Roughly how many sites |
|---|---|
| 1–2 | about a third |
| 3–5 | about a quarter |
| 6 or more | a stubborn handful — up to 11 |
Most sites sit in the sane range. But a real set of them — ordinary business sites, nothing fancy — were pulling from eight, nine, eleven different companies’ servers to paint a single page.
Why each one costs you
Every external host on your page is three things you didn’t ask for:
- A delay you don’t control. The browser has to do a fresh DNS lookup and a new TLS handshake for each new host before it can download anything. On a phone on mobile data, that’s real time, and it happens before your content shows. Eleven hosts is eleven of those.
- A dependency that can break your page. When one of those third parties is slow, or down, or changes its script, your page inherits it. You find out from an angry client, not from a deploy you made.
- A place your visitors’ data goes. Every one of those requests carries your visitors’ IP and page URL to another company. In Brazil that’s an LGPD question with your name on it, not theirs.
The widget nobody remembers adding
The pattern I see most: a site is clean for a year, then someone adds a chat widget for a campaign, a reviews badge for trust, a heatmap tool “just to check something,” a second analytics because marketing wanted their own. Nobody removes any of them. Two years later the page loads from nine servers and everyone’s forgotten why.
None of those tools show up as a plugin to disable. They’re a line of JavaScript in a header, or baked into the theme, so a plugin audit walks right past them. You only see them when you watch the page actually load.
How to check yours in five minutes
Open your site, open your browser’s network tab, reload, and sort by domain. Count the distinct ones that aren’t you. If it’s more than you can explain in a sentence each, you’ve got cleanup to do — start by killing anything no one can name a reason for.
Site Doctor does this count on every scan and flags the hosts, read-only, so you can see the creep before it’s nine deep. But honestly, the network tab is free and the exercise is worth doing by hand once — it tends to be a surprise.