Somewhere out there is a rule of thumb that says a WordPress site should have no more than some magic number of plugins: ten, fifteen, twenty, depending on who’s saying it. Here’s the professional answer, which is more useful and slightly disappointing: there’s really no magic number.

I’ve audited sites with eight plugins that were a disaster and sites with thirty that ran beautifully. What separates them isn’t count. It’s weight, quality, and overlap, and once you understand those three, you can audit your own plugin list in an afternoon and know exactly what to cut. Let’s make you dangerous.

Why plugins pile up (no judgment, it’s structural)

Every plugin on your site was installed to solve a real problem on a real day. A form was needed. A gallery. A pop-up for that one launch. Social icons. That thing a YouTube tutorial insisted on. The other one you can’t even remember installing. Each decision was individually reasonable, and nobody ever schedules the meeting where old decisions get reviewed. Five years later the plugin page scrolls twice, half the entries are mysteries, and the site has slowed in a way nobody can pinpoint, because it happened one reasonable decision at a time.

But we’re not judging here. It’s not that you’re careless, it’s that you’re busy running a business. Every unmanaged site drifts this way. So what’s the problem with all these plugins anyway? How do we know if they’re a problem?

What plugins actually cost

Three currencies, and only the first is widely understood:

Performance. Many plugins load their own scripts and styles, often on every page whether needed or not. One well-built plugin costs almost nothing; a stack of careless ones recreates the bloat problem I described with page builders, assembled piecemeal. The insidious part is that no single plugin is guilty; the pile is.

Security. Every plugin is code from a stranger with access to your site, and plugin vulnerabilities are the leading way WordPress sites get compromised. The risk concentrates heavily in abandoned plugins, ones whose developers stopped updating them, because discovered holes stay open forever. An abandoned plugin isn’t a tool anymore – it’s an unlocked window.

Conflict. Plugins are built by thousands of unrelated developers, and mostly they coexist fine. But every addition multiplies the interaction surface, and the “site broke after an update” experience is usually two plugins disagreeing. Fewer moving parts means fewer 11pm surprises.

The four-question audit

Open your plugins page, and for each entry, ask:

  • Do I know what this does? If nobody on your team can explain a plugin’s job, deactivate it and watch the site for a week. The number of plugins that turn out to do nothing is genuinely surprising.
  • Is it still maintained? Check the plugin’s page on WordPress.org: when was it last updated, and is it tested with recent WordPress versions? What do the reviews say? Years of silence means find a maintained replacement, even if it “still works.”
  • Is it earning its weight? A plugin loading assets sitewide to power a widget used on one page is a bad tenant. Sometimes the answer is a lighter alternative; sometimes it’s realizing the feature stopped being helpful five years ago.
  • Does something else already do this? Overlap is everywhere: two SEO plugins, three form builders, a security suite on top of a security suite, a bundle of single-purpose plugins doing what a few good theme functions could. Consolidation is the highest-yield move in most audits.

Two safety notes before you go cutting: take a backup first – always – and deactivate for a while before deleting, so anything that turns out to matter is one click from restored. Certain plugins also hold data you’d want to keep (forms entries, SEO settings), so a moment of thought before deletion pays for itself.

What a healthy plugin list looks like

Not a specific list of names, because the right stack depends entirely on your site, and any article handing you ten must-haves without knowing your business is guessing, not advising. A healthy list has a purpose: every plugin has a known job, comes from an actively maintained source, appears exactly once per job, and the total is as small as your actual needs allow. On a lean custom build, that often means strikingly few, because features that matter are built in rather than bolted on. On a self-assembled site, fifteen to twenty-five well-chosen plugins can be perfectly healthy. Forty-seven mystery plugins never are, and yes, that’s a real number from a real audit.

The part after the audit

Let’s be honest though: this work is never really done. A plugin audit is a snapshot, and entropy doesn’t retire. The sites that stay healthy are the ones where someone reviews, updates, and prunes on a schedule. Need some help with that? My monthly maintenance plans are a great way to keep your site running efficiently, alongside backups, security, and updates, so the pile never rebuilds itself.

And if your site is already deep in plugin debt and you’d rather have a professional untangle it, that’s a standard part of my free audit: I’ll tell you what’s dead weight, what’s dangerous, what overlaps, and what the site would feel like without it. Sometimes the single biggest speed win on a site is subtraction, and subtraction is wonderfully affordable.