SASami A. · Oct 4, 2026 · 10 min read

Every plugin is a standing liability, and most sites carry far more liability than they get value.

Open the Plugins screen on a site that has been running for two or three years. Read the list slowly. Somewhere in it is a plugin installed for a single campaign, one that duplicates a feature your theme already has, one you disabled “just for now”, and one whose author you could not name. Nobody decided to keep them. They stayed because deleting is a decision and leaving is not.

This essay argues a simple position: on most WordPress sites, you should delete about half of the plugins you have. Not because a magic plugin count exists, and not because plugins are bad. Because every plugin is a standing liability, and most sites carry far more liability than they get value.

The strongest case is not speed. It is maintenance, security and clarity. Speed comes last in this argument, and we will explain why.

A plugin is a commitment, not a download

Installing a plugin takes thirty seconds. Owning it takes years. Each plugin adds code that runs with the full privileges of your site, a vendor you now depend on, an update stream you must follow, a settings screen someone must understand, and a possible conflict with everything else.

When you install a plugin, you are not adding a feature. You are hiring a contractor who has a key to the building and will never be reviewed unless you do it yourself. Put that way, most people would interview fewer contractors.

That is the frame for everything that follows. The question is never only “does this plugin do something useful?” The question is “is that usefulness worth the permanent cost of owning it?” For many plugins the honest answer is no.

The security argument is the strongest one

WordPress core is maintained by a large team with a well-established security process. Plugins are a different story. Patchstack’s State of WordPress Security in 2025 report states that 7,966 new vulnerabilities were found in the WordPress ecosystem in 2024, that 96% of them were in plugins, 4% in themes, and that only seven were in WordPress core itself.

The same report says that 33% of vulnerabilities were not fixed in time for public disclosure, that many were disclosed in abandoned plugins that will likely never receive a patch, and that 1,614 plugins and themes were removed from the WordPress.org repository for unpatched security issues.

Read those numbers carefully, because they do not say what a headline would make them say. They do not say that every plugin is dangerous. The overwhelming majority of installed plugins on a typical site will never be the subject of a vulnerability report. They say something narrower and more useful: the plugin layer is where nearly all the reported risk lives, and a meaningful share of that risk sits in code that will not be patched.

Now apply the arithmetic of exposure. If each plugin has some small chance of a serious flaw over its lifetime, and each flaw has some chance of going unpatched, then the expected risk of your site grows with the number of plugins you run. You cannot make an individual plugin safer. You can make the pile smaller. Deleting a plugin you do not need removes its entire risk, permanently, for free.

This is the same logic as least privilege, applied to code. If you are interested in the permissions side, our guide to the wider WordPress security picture covers it, and so does the piece on user roles and least privilege.

Deactivated is not deleted

A common half-measure is to deactivate a plugin and leave it in place. That is better than leaving it active, but it is not safe to treat it as gone. Files of an inactive plugin remain on the server. Whether those files can be reached depends on the vulnerability and the plugin, and you are not going to audit that for every plugin you stopped using.

The simpler rule is the correct one: if you are not using it, delete it. A deleted plugin has no files to be probed and no updates to be missed. A deactivated plugin has both, and you are quietly paying for them.

The counter-argument: plugin count is the wrong metric

The best objection to this whole essay is the one you will hear from experienced developers: counting plugins is naive. A site with 40 well-written plugins can be faster and safer than a site with five bad ones. One heavy page builder can cost more than thirty small utilities. Quality matters more than quantity, and a rule of “keep it under N” is nonsense.

That objection is right, and you should accept it. There is no number that is too many. Several of the practical guides that discuss this topic make the same point: the raw count of active plugins is rarely the real issue, and what matters is what each one does and how well it is built.

But notice what the objection does not defend. It does not defend keeping plugins you do not need. It argues that count is a bad target. Fine. We are not proposing a target. We are proposing a review, and observing that when you actually run the review, roughly half of the list usually fails it. “Half” is a rule of thumb for how much deadweight accumulates, not a quota.

The honest version of the claim is: judge each plugin on its merits, and be much stricter than you have been. The count will fall as a consequence.

Speed is the weakest argument, so do not lead with it

Most “delete your plugins” advice leads with page speed. We think that is a mistake, because it is the argument most easily answered. A plugin that only runs in the admin area, or that loads nothing on the front end, usually has little effect on how fast your pages reach visitors. Deleting it will not move your scores, and then you conclude the exercise was pointless.

Where plugins do hurt speed, the culprits are specific: plugins that load scripts and styles on every page when they are needed on one, plugins that run heavy queries on every request, and plugins that call external services during page load. Those are worth finding. You find them by measuring, not by counting. Our guides to WordPress speed optimization and fixing a slow admin show how.

So keep the speed argument, but put it in its place. It is a reason to audit the handful of plugins that load on the front end. The reasons to delete the rest are security, upgrade friction and mental load.

Every plugin multiplies your update and conflict surface

Each plugin you run is another thing that can break after an update to WordPress, to PHP, or to any other plugin. The number of possible interactions grows faster than the number of plugins. You do not need a formula to feel this: anyone who has debugged a white screen after a routine update knows that the hard part is working out which of many components is responsible.

When something does go wrong, a smaller plugin list is a smaller search. The standard first step in troubleshooting plugin conflicts is to disable plugins until the problem disappears. With eight plugins that takes minutes. With forty, it takes an afternoon and you may give up halfway.

The same goes for updates. Reading release notes, testing on staging, and deciding whether to apply a patch is real work. Doing it for twenty plugins is a part-time job that most site owners quietly skip. Skipping is how sites fall behind. A shorter list means you can actually keep your promise to update.

The hidden overlap: plugins that do the same thing twice

The cheapest deletions are overlaps. These are common:

  • An SEO plugin and a separate redirect plugin, when the SEO plugin already handles redirects.
  • A cache plugin and a host-level cache that does the same job, sometimes fighting each other.
  • A security plugin whose firewall duplicates one your host or CDN already provides.
  • A page builder, plus a separate “extra blocks” plugin, plus a theme that also ships its own blocks.
  • A contact form plugin installed years ago, then another one added by a different person for a different page.
  • A one-click “maintenance mode” plugin that you use for ten minutes a year.

None of these is an unreasonable decision when it was made. Together they are a site that does everything twice. The overlap is usually obvious once you list what each plugin is for, which is the first step of the review below.

What you cannot safely delete

An essay about deletion owes you the other half: what to keep. Three categories deserve protection.

  • Plugins that store content or data you need. Forms with stored entries, membership plugins, e-commerce, custom field plugins, and any plugin that created content types or shortcodes used in your posts. Deleting these can orphan content, display raw shortcodes, or destroy records. Export first, and verify.
  • Plugins that provide security or backups you do not get elsewhere. If your host does not back up your site, your backup plugin is not clutter. Do not delete it because the list looks long.
  • Plugins that replace a lot of custom code. A well-maintained plugin that does a hard job is often safer than a copy-pasted snippet in your theme. The goal is fewer unneeded plugins, not more homemade code.

There is a fair counter-argument here: some people will replace a small plugin with a code snippet and call it a win. Often it is not. A snippet has no update channel and no author watching for vulnerabilities. If you replace a plugin with code, own that code the same way you would own a plugin. Our piece on plugin or code for custom post types works through when each choice is right.

A review you can run in one afternoon

Here is the practical process. It assumes nothing exotic and needs no special tools.

  1. Back up first. Take a full backup of files and database and confirm you can restore it. If you do not have a routine, set one up with our backup routine tutorial.
  2. Work on a copy. Do the experiment on a staging site, not on production. The staging site guide explains how.
  3. List every plugin with one sentence of purpose. Write what it does and which page or feature depends on it. If you cannot write the sentence, that plugin is your first candidate.
  4. Mark overlaps and orphans. Anything that duplicates another plugin, your theme, or your host is a candidate. Anything unused for a year is a candidate.
  5. Check maintenance status. For each remaining plugin, look at the directory listing: the last update date, the tested-up-to version and the support forum. A plugin that has not been updated for years and that nobody answers is a risk. The directory itself closes plugins for guideline violations, security issues or at the author’s request, so a missing listing is also a signal.
  6. Deactivate in small batches on staging. Deactivate a few, browse the main pages, test forms and checkout, and check the error log. Then delete the ones that passed.
  7. Replace carefully. If a plugin is unmaintained but does something you need, search for a maintained alternative before deleting. Our list of plugins you can delete gives common safe candidates.
  8. Repeat on production, with a backup taken immediately beforehand. Apply the same deletions, test again, and keep the backup for a few weeks.

If that feels like a lot of ceremony for removing a plugin, remember what the ceremony protects: the one plugin that turns out to power a page you forgot existed.

Make it hard to add the next one

The review fixes the past. The habit fixes the future. Before installing any plugin, ask four questions. Can the theme, the block editor or the host already do this? Is it actively maintained? Does it load assets on every page? And would you be comfortable removing it again in a year?

We cover the vetting process in detail in how to vet a WordPress plugin before you install it. The short version is to treat installation as a decision that needs a reason, written down, rather than as a reflex.

One more habit is worth adopting: a recurring review. Put it into your maintenance checklist and run it every quarter. Twenty minutes with the plugin list, asking the one-sentence-purpose question again, prevents the pile from rebuilding itself.

The case for stopping at “enough”

There is a quieter benefit that is easy to miss. A site with a short, understood plugin list is a site you can hand over. A new developer, a client, or you six months from now can read it in a few minutes and know what every part is doing. A site with sixty plugins is a site only its original builder understands, and often not even them.

That is the real argument for the half-deletion rule. It is not minimalism for its own sake. It is a way of keeping a site small enough to be held in your head. When you can hold the whole thing in your head, you update it, you secure it, and you fix it faster. When you cannot, you just hope.

The strongest objection remains the best one: count is the wrong metric, quality beats quantity, and a well-built plugin costs little. We agree. So do not obey a number. Obey the question. For every plugin on the list, ask what it does, who maintains it, and what would happen if it were gone tomorrow. Where the answers are “nothing sure”, “nobody”, and “nothing”, you have found a plugin to delete.

Conclusion

Plugins are not the problem. Unexamined plugins are. The vulnerability data says the plugin layer is where nearly all reported WordPress risk lives, a third of it unpatched at disclosure, and the cheapest way to cut that exposure is to run less code. Speed is a side effect, not the argument.

Back up, work on staging, write one sentence of purpose for every plugin, delete what fails, and set a quarterly reminder. Most sites will end up with fewer plugins than they started with. All of them will end up with a clearer idea of what they are running. For a wider view of what a healthy stack looks like, see our guide to the best WordPress plugins.

← All opinion

SponsoredNibWP

Stop clicking. Start telling.

Ask your AI to build pages, fix speed and nail SEO, and NibWP does it on your WordPress site in minutes.

Try NibWP.com

Get the WPMusk Sunday brief

One email a week with our newest tutorials, honest tool reviews and resources you won’t find on the blog. No spam, unsubscribe in one click.

Newsletter (Sunday brief)