
How many plugins should you use in WordPress, and what does each one cost to keep?
Most WordPress sites grow one plugin at a time, over several years and often under several different owners. Someone needs a contact form, a cookie banner or a faster cache, finds a plugin that does the job and installs it in a few minutes. Each choice makes sense on the day, so nobody counts the plugins until an update breaks something or the site starts to feel slow.
However, most of the cost of a plugin comes after the day you install it. Each one is code from a separate developer, with its own update schedule, its own security record and its own effect on page speed. WordPress keeps its own core software up to date with little help, but most plugin updates wait for a person to approve them.
So the useful question isn’t how many plugins a site should have. It’s what each plugin costs to keep, and whether the feature it gives is worth that cost. Auditing and streamlining sites where plugins have built up over the years is one of the most common jobs our WordPress development team does, and this article explains how to make that call for your own site.
WordPress updates itself, but only in part
WordPress has updated itself in the background since version 3.7. According to the WordPress.org guide to upgrading, every site gets minor core releases and translation files automatically, and sites installed since WordPress 5.6 also get major releases by default. Minor releases are the ones that carry maintenance and security fixes.
Plugins and themes follow different rules. By default they update in the background only in special cases, when the WordPress security team pushes a fix for a critical vulnerability. Site owners can turn on automatic updates for all plugins or for chosen ones, but that is a decision each site has to make.
There’s a good reason to make it with care. An update can change how a plugin behaves, and on a site with many plugins, that change can break a form or a checkout that depends on it. So teams hold updates back until a quieter week, and over the months a backlog of untested updates builds up. Every plugin you add makes that backlog longer, because it’s one more update to test and approve.
Where the security risk sits
The clearest evidence comes from Patchstack, a security company that tracks WordPress vulnerabilities and sells protection against them. Its State of WordPress Security in 2026 report covers 2025 and found 11,334 new vulnerabilities in the WordPress ecosystem, 42% more than in 2024. The report also found the following.
- 91% of the new vulnerabilities were in plugins and 9% were in themes.
- WordPress core had only 6, and Patchstack rated all of them low priority.
- 46% had no fix from the plugin developer by the time the vulnerability was made public.
- For the vulnerabilities that attackers targeted most, the weighted median time to the first attack was 5 hours.
Two more findings matter for a plugin review. Of the ten vulnerabilities attacked most often in 2025, only four were published that year, so attackers keep using old flaws on sites that haven’t updated. Premium plugins and themes, which security researchers find harder to inspect, had three times as many known exploited vulnerabilities as free ones.
So the WordPress core software is rarely the source of the problem. The risk grows with each plugin and theme you add, and a fix often depends on a developer you’ve never spoken to. A plugin you deactivate but don’t delete still sits on the server, so removing what you don’t use is the one change that takes a risk away completely.
The costs that don’t show up in a security report
Security is the cost that most people talk about, but each plugin brings other running costs with it. Most of them grow slowly, so they’re easy to miss until the site feels slow or an upgrade turns into a project.
- Page speed: a plugin can add scripts, styles and database queries to pages that never use its feature. One well-built plugin can cost less than a badly built one, so the count alone tells you little.
- Testing time: every update has to work with every other plugin on the site. Twenty plugins give far more combinations to check than five, and each combination is a place where an update can fail.
- Abandoned code: the WordPress.org directory warns readers when a plugin hasn’t been tested with the latest three major WordPress releases. A plugin in that state may already have lost its developer, so it can stop getting security fixes at any time.
- Platform upgrades: PHP is the language WordPress runs on, and each plugin has to work on the version your server uses. Each PHP version gets security fixes for about four years, according to the PHP project’s support schedule, so every few years each plugin needs testing on a newer version.
Each plugin also makes its developer one of your suppliers. A good supplier reduces that risk by keeping the list short and writing bespoke code where an off-the-shelf plugin falls short. That’s how we build, and every release we make is checked against page speed and Core Web Vitals, Google’s measures of how fast and stable a page feels.
How to review the plugins on your site
A plugin review doesn’t need special tools, only an hour with whoever runs the site and whoever owns the features. You can use this list as the agenda.
- List every plugin, active and inactive, with what it does and who asked for it.
- For each one, name the page or feature that depends on it. If nobody can name one, mark the plugin for removal.
- Delete the plugins you’ve marked, after a backup. Deactivating a plugin isn’t enough, because its code and files stay on the server.
- Look for two plugins doing the same job, such as two SEO plugins or two form builders, and keep one.
- Check when each plugin was last updated and whether the WordPress.org directory shows a warning. Plan a replacement for any that look abandoned.
- Check that every premium plugin has a current licence and is still getting updates.
- Decide how each plugin gets updated. Low-risk plugins can update automatically, while plugins that run checkout, forms or logins are tested on a copy of the site first.
- Measure page speed before and after the review, so you can see what the removals changed.
- Book the next review now, because plugins build up again over time and a regular slot keeps the list short.
Where does your site stand?
Most sites fit one of three stages, so find yours and start with the step it points to.
- You can’t list your plugins or who owns them: start with steps 1 to 3 above. Until you know what’s installed and why, every other decision about updates or speed is a guess.
- You know what’s installed, but updates wait for a quiet week: work on step 7. A testing routine on a copy of the site turns the backlog into planned, scheduled work.
- Updates are routine and tested: look at page speed and at the plugins your key features depend on. Some of them may be worth replacing with bespoke code.
Keep the plugins that earn their place
There’s no right number of plugins for a WordPress site, because a site with thirty well-kept plugins can be safer and faster than one with ten that nobody updates. What matters is that someone knows why each plugin is there and who keeps it up to date.
If your site has built up plugins over the years, we can help you work through it. When you work with us, you get the following.
- An audit of every plugin, with the ones to keep, replace or remove.
- Bespoke code where an off-the-shelf plugin falls short.
- Ongoing maintenance with security updates and performance monitoring.
- Every release checked against page speed and Core Web Vitals.
- A team certified to ISO 27001, the international standard for information security management.
To talk through the plugins on your site with our team, book a WordPress Platform Review.
Frequently asked questions
How many plugins should I use in WordPress?
There’s no fixed number that suits every site. Use as few as your features need, and make sure each plugin has a clear purpose, a named owner and a developer who still releases updates.
How many plugins is too many for WordPress?
It’s too many when nobody can say why some of them are there, or when updates wait because there are too many to test. A short list of well-maintained plugins is safer than a long list of neglected ones.
Do plugins slow down WordPress?
They can, because a plugin may add scripts, styles or database queries to every page, including pages that don’t use its feature. Measure page speed before and after you remove a plugin, so you can see the effect it was having on your visitors.
Do inactive plugins slow down WordPress?
A deactivated plugin’s code doesn’t run when pages load, so it has little effect on page speed. Its files still sit on the server, though, so delete any plugin you don’t plan to use again.
Are WordPress plugins safe?
A plugin’s safety depends on how recently it was updated and whether its developer still maintains it. Patchstack’s 2026 report found that 91% of new WordPress vulnerabilities in 2025 were in plugins, so each plugin you add is one more thing to keep updated.
Should I turn on automatic updates for plugins?
For low-risk plugins, automatic updates save time and close security gaps sooner. For plugins that run checkout, forms or logins, test each update on a copy of the site first, because an update can change how other parts of the site behave.
Sources
- WordPress.org, Upgrading WordPress, Configuring Automatic Background Updates. Read 10th November 2026.
- Patchstack, State of WordPress Security in 2026, updated 25th February 2026, covering 2025 data. Read 10th November 2026.
- WordPress.org Plugin Handbook, Alerts and Warnings. Read 10th November 2026.
- PHP, Supported Versions. Read 10th November 2026.
- Our own service page, WordPress Development. Read 10th November 2026.