How Many Plugins Is Too Many? You’re Asking the Wrong Question.
A WordPress topic for the ages: how many plugins is too many for one website? Mark Szymanski took a swing at it, and look — I don’t think Mark’s wrong, exactly. But is he cooking with this one, as the kids say? Eh. I’m not so sure.
The gut reaction baked into the whole debate is that more plugins = bad. I don’t agree with that. Because it’s not about the number. It’s never about the number.
I’ve run WordPress installs with 60-plus plugins, and that site kept plugging right along with everything plugged in. (Yes, I’m going to keep doing that. It’s my article.)
Okay, one thing is true
There’s an irreversible, irrevocable, incontrovertible truth here: the more code you throw at something, the more brittle that thing becomes. Josh Koenig of Pantheon said that to me once, and honestly? That’s a bar. I think about it all the time.
And yet — I still run dozens of plugins across different sites. So clearly, I don’t think “brittle” and “more plugins” are the same sentence. There’s just a lot more to consider than a headcount.
Why does everybody fixate on the number?
Because it’s easy. It’s a nice, round figure sitting right there on your plugins screen. You don’t have to run a single tool to find it. You just glance at it and go, “ooh, big number, bad.”
That’s the amateur response. The pro response asks better questions. Does each of these plugins have a specific purpose? Could it be replaced? Does it earn its spot? Is it being duplicated somewhere else on the site?
Do the boring thing: an inventory
Write down what every plugin actually does. All of them. Then look for overlap.
A lot of what I run is small utility stuff — something to help me organize a menu, a column-management tool, little things that make a site easier for me and my clients to manage. That’s where a chunk of my so-called “bloat” comes from, and I’m at peace with it.
But here’s the move that comes with time: every so often you find one plugin that bundles up a bunch of those little jobs into one. Or you ask the real question — do I even need a plugin for this, or is it a tiny utility I could write myself? I could fold a dozen of those into a single custom plugin and cut my dependence on third-party authors I’m not as familiar with. Fewer unknowns, same functionality.
Plugin count is the wrong axis
What we should actually be looking at is performance — and not by vibes. We need real numbers. Is the site heavy to use? Slow? Sluggish? There are concrete metrics for all of that, and they’ll tell you the truth; a plugin count never will.
Not all plugins are created equal
This is the one I always come back to. So what does it actually mean? A few things I look at:
- Does it load everything, everywhere? Some plugins dump all their scripts on every page, even when the plugin isn’t being used on that page.
- Does it nag you? Ads, upsells, and UI clutter for other products you don’t even own. (I’m looking at Awesomotive and Syed Balkhi here.) That’s bloat and a worse experience.
- How’s it coded? Are its queries efficient? Does it autoload options it shouldn’t? Does it load assets site-wide or only where they’re needed?
- How well is it maintained? Are the updates meaningful — or just padded version bumps to keep the plugin visible in the directory? There’s a difference.
- Does it play nicely? Does it use actions and filters properly, and expose hooks so you can extend it cleanly?
The stuff nobody tweets about
Overlap. People don’t talk about it, but you’ll constantly find two plugins doing the same job, or stepping on each other’s toes. Then there’s what loads where, the security risks that ride along with anything unmaintained, and the quiet one: cleanup. When a plugin hits the database, does it have routines to clean up after itself? A lot don’t, and it gets out of hand fast — especially with bigger platform plugins. Sensei is a good example of one who can really pile up.
So if you’ve got a lot of plugins, interrogate each one. Does it earn its spot? Single-purpose or multi-purpose? Is it overlapping something else? Can it be removed—and what would actually break if you do? You definitely don’t want to duplicate core functionality or anything your theme already handles.
And if you’re measuring with Query Monitor, New Relic, or similar, test the site with and without the plugin. Is it mission-critical? If it vanished today, would it hurt the business tomorrow? That’s how you find the dead weight.
So… where do I land?
Ten can be too many. Sixty can be perfectly fine. It depends — and I genuinely don’t think it’s the big scary issue people make it out to be.
What experience has taught me is that bad actors exist, and even good developers ship bad code or a rough update now and then. That’s worth keeping in mind, especially now that more people can ship code at any time. The real discipline isn’t restraint for its own sake. It’s knowing how much each plugin costs you and deciding whether it’s worth it.
So, back to Mark. His instinct isn’t really about the number — it’s about value. Strip it down and he’s saying “don’t be careless,” which is correct! He’s just measuring it with the wrong ruler. Respect the instinct, ditch the number, do the analysis, and make every plugin justify its existence in your install.
