Does your plugin load anything from other servers? How to check it yourself
Whether a WordPress plugin fetches anything from other servers, on a normal page view or in your dashboard, is something your browser can show you. Here is how to check your own site, how to pin a request on a single plugin, what we found when we measured 72 plugins, and what the wordpress.org guidelines require.
First, so you know who is writing: we build WordPress plugins ourselves. Six of them were part of the measurement and sit in the same table as everyone else's. The numbers in this post come from our study of external requests in 72 plugins.
Measured on September 15 and 16, 2026, in WordPress Playground. We reread the wordpress.org guidelines and the Chrome DevTools documentation on November 8, 2026.
What we found in 72 plugins
Each plugin got its own fresh WordPress in the browser: installed from the directory, activated, nothing else. We logged out, opened the homepage and a post the way a visitor would, and recorded every network request with its host. The sample is all 67 plugins with at least a million installs from our census of the plugin directory, plus six of our own. One never booted, so 72 were measured.
- No plugin: zero outside servers. WordPress with its bundled theme fetches nothing from outside on the front end. To prove the meter moves, we planted an image from example.com in the footer, and the run caught it.
- Page view: 1 of 72. Only
hostinger-reachfetched anything from outside: a script calledjs/embed.jsfromcdn-reach.hostinger.com, twice, on the homepage. - Dashboard: 9 of 72. Logged in, nine plugins fetched something from other servers. Two of them send your browser to the vendor's own site the first time you open them.
That is the out-of-the-box state. Site Kit without a connected Google account loads nothing. What a plugin does once you connect an account is outside this measurement. The risk starts with the setup, which is why your own site deserves a look.
The video walks through how the measurement was built, the two false alarms we caused ourselves along the way, and what the nine dashboard plugins load:

Front-end check: what your site loads for visitors
The steps follow Chrome, with control names as in the Chrome DevTools documentation. Firefox and Edge have the same tab.
- Open a private window. You are not logged in there, and no earlier consent choice is stored.
- Press F12 and open the Network tab. Tick Disable cache so you see what a first-time visitor loads.
- Load your homepage. Leave the cookie banner alone.
- Type your own domain into the filter box and tick Invert. The list now only shows requests that do not go to your domain. Or use More filters › 3rd-party requests, which shows everything whose origin differs from the page.
- Right-click the table header and switch on the Domain column. Write down every host you see.
- Repeat this for a post and for pages with a form, a map or a shop. Whatever a plugin only adds to certain pages only shows up there.
An outside host is not automatically a problem. Fonts, embedded videos or a payment provider may be exactly what you want.
Dashboard check: what your browser loads while you work
In the dashboard we found nine times as many cases as on the front end. The people affected there are not your visitors but you and everyone who logs in to your site.
- Log in and open the developer tools as above, this time with Preserve log ticked as well. Requests then stay in the list even when a page redirects you.
- Open the dashboard, then Plugins › Installed Plugins, then your plugins' own pages one by one.
- Subtract what WordPress loads by itself. When you are logged in, WordPress fetches the avatar in the admin bar from
secure.gravatar.com, which belongs to no plugin. - Watch for entries of type
document. Those are pages your browser was sent to, and their address shows what went along.
In our measurement it looked like this: google-analytics-for-wordpress (MonsterInsights) redirected to connect.monsterinsights.com on first open, with the site URL, the site's REST endpoint and an onboarding_key in the address. optinmonster redirected to app.optinmonster.com/wp-welcome with a connectionToken and wpUrl, and also loaded a counting pixel from p.typekit.net that sends the site's host name. Both happened before anything had been configured.
The other seven are mostly fonts. According to the study, five of the nine cases are Google Fonts, and wp-smushit gets its fonts from fonts.bunny.net. On top of that come Google Charts in all-in-one-wp-security-and-firewall and files from an email marketing provider in custom-post-type-ui.
Which plugin is behind a request?
A host in the list does not tell you who called it. Three ways lead to the plugin, from quick to certain.
The Initiator column
The Initiator column shows what triggered a request. If a script made it, Chrome links to the line in the source file. When that file sits under /wp-content/plugins/, the plugin's folder comes right after, usually with the same slug as in the directory. If the column says Parser, the request came from the page's HTML; Redirect means a redirect. In both cases, the cross-check below settles it.
Cross-check in WordPress Playground
You get certainty from a run where only that one plugin is active. That is how we measured:
- Open
playground.wordpress.netwith no plugin and record a baseline as above. Anything that shows up here belongs to the test environment. - Add the plugin's slug from its directory address to
playground.wordpress.net/?plugin=. Playground installs it and logs you in as admin, details in Try WordPress plugins in your browser. - For the dashboard, open the plugin's page right away, with Preserve log on. The two redirects above happened on the first open.
- For the front end, log out, empty the list with the Clear button, and only then open the homepage and a post.
- Measure twice. Only when both runs agree do you have a finding.
We fell into two traps ourselves. The Playground site reports its own boot errors to Google Analytics, which you can spot by playground.wordpress.net in the request address. And if you start counting before you log out, you catch the Gravatar image on the logout screen.
On your own site, without affecting visitors
How a plugin behaves with your settings only shows on your own site or a copy of it. On a staging copy, switch off every plugin, record the baseline, and switch them back on one at a time. On the live site, the Health Check & Troubleshooting plugin does this: its troubleshooting mode disables all plugins for your own session only. You are logged in while doing it, so Gravatar is part of your baseline. The same approach finds two plugins that clash, and there is an example in our post on a plugin conflict caused by Composer.
What the browser cannot see
The Network tab only shows what your browser loads. Three things stay outside it, and our study page lists the same three as limits:
- Requests from the server. If a plugin calls an outside API from your server, the browser never sees it.
- What is inside. The list shows that something was fetched and from whom. What a request sends along only shows when you click it and open the Headers and Payload tabs.
- States you do not play through. Anything that loads only after consent, after a form is sent or inside a customer account only shows if you do exactly that.
For server-side calls, the readme and the plugin's documentation are what you have. What runs on the server is a topic of its own: how fast hosts patched the last critical PHP flaw, and how to look up your PHP version, is in our post on php2shell.
What the wordpress.org guidelines require
Plugins in the official directory fall under the Detailed Plugin Guidelines. Three of them concern outside servers. In my own summary:
- Guideline 7 is titled “Plugins may not track users without their consent”. A plugin may only contact outside servers once the user has explicitly agreed, typically by registering with a service or ticking a box in the settings. How user data is collected and used belongs in the readme. Among the forbidden examples: offloading images and scripts that have nothing to do with a service.
- Guideline 6 permits plugins that act as an interface to an outside service, paid ones included. The service has to be clearly documented in the readme. For such services (guideline 7 names Twitter, an Amazon CDN plugin and Akismet), installing, activating, registering and configuring the plugin counts as consent.
- Guideline 8 allows third-party CDNs for fonts only. JavaScript and CSS unrelated to a service must ship inside the plugin, and admin pages must not be connected through iframes.
What goes into the readme is spelled out on the Common issues page of the Plugin Handbook: that the plugin relies on an outside service and under which circumstances, a link to the service, and a link to its terms of use or privacy policy. That also applies when the developers run the service themselves. Among the permitted examples, the same page lists font families from Google or an approved CDN.
For our measurement, that means a good share of the dashboard findings are fonts, and the guidelines allow fonts in so many words. Whether a single case follows the rules is for the wordpress.org plugin team to decide, not our table. Even an allowed font still means your browser contacts that server, though. What matters most for you as a site owner is whether the host you saw is mentioned in the readme.
What to do with a finding
- Read the readme. Open the plugin's page in the directory or the
readme.txtfile in its folder and search for the host from your list. If it is there with a purpose and a link to a privacy policy, you have what you need for your own privacy policy. - Look through the settings. If the request belongs to a feature you do not use, check whether it can be switched off. Then measure again.
- Ask the developers. If the readme says nothing, ask in the plugin's support forum on wordpress.org which service it is and what it is for. Give the host, where you saw it and the date.
- Think about consent. Anything that loads on the front end before the banner is clicked is the subject of Tracking before consent. Consent tools for WordPress are compared in our post on cookie consent plugins.
- Measure again after every change. New plugin, new account, new setting: the check shows whether the list has changed.
Whether a finding is a legal problem is not something this post answers. But you will know what your site loads.
All 72 plugins in one table
Every measured plugin with its outside hosts and request count, front end and dashboard, plus the method, the self-test and our two false alarms.
Frequently asked questions
How do I check if a WordPress plugin sends data to other servers?
Open your site in a private window, press F12 and go to the Network tab. Reload, type your own domain into the filter box and tick Invert, so only requests to other hosts are left. Repeat that logged in for the dashboard, then confirm the suspect in WordPress Playground with only that one plugin active.
Do many WordPress plugins load things from other servers?
Fewer than you might expect, at least straight after activation. We measured 72 plugins, all with at least a million installs plus six of our own: on a normal page view one of them fetched something from another server, and in the dashboard nine did. Once you connect an account the numbers change, and our measurement does not cover that.
What do the wordpress.org guidelines say about external services?
Guideline 7 says plugins may only contact outside servers with explicit consent, usually through an opt-in. Services are allowed under guideline 6 as long as the readme documents them clearly. The Plugin Handbook adds that the readme has to say when the service is used and link to the service and to its terms or privacy policy. Fonts from third-party CDNs are explicitly allowed.
Does the browser show every request a plugin makes?
No. The Network tab only shows what your browser requests. If a plugin calls an outside API from your server, it never shows up there. For those calls, the readme and the plugin's documentation are what you have to go on.