“Don’t install too many plugins” is one of the most-repeated pieces of WordPress advice out there. The version most people internalize, that more than 10 is bad, is wrong. The real answer depends on what the plugins actually do, not on how many you have installed.
Where the “too many plugins” idea came from
In older WordPress versions, each active plugin loaded all of its code on every single page request. More plugins meant slower sites, full stop.
Two things changed since then:
- WordPress core improved how plugins load their code.
- Modern caching plugins serve most page requests from a static cache, bypassing most plugin code entirely.
Today, the raw count isn’t really the issue. What each plugin does on each request is what matters. If you haven’t set up caching yet, our WordPress caching guide covers exactly how much this changes the equation.
What actually slows a WordPress site
1. Plugins that load on every page when they shouldn’t
Some plugins are well-scoped. A contact form plugin, for instance, only loads its scripts on the pages that actually contain a contact form.
Other plugins aren’t nearly as careful. They inject scripts and styles into every single page even when the feature only gets used on one page.
The result: a site running one bloated plugin can end up slower than a site running five well-scoped ones.
2. Plugins that hit the database heavily
Some plugins run many database queries on every page load. Image-heavy gallery plugins, social-counter plugins, and “popular posts” widgets that recalculate on every load are common offenders. These slow things down even with caching in place.
3. Plugins that fetch external resources
Plugins that load fonts from external CDNs, analytics scripts, social widgets, or advertising each add a separate third-party HTTP request. The number of external requests affects page speed more than plugin count ever does.
4. Plugin conflicts
Two plugins doing similar things sometimes interfere with each other. Common conflicts include:
- Two caching plugins running at once.
- Two SEO plugins running at once.
- Two security plugins running simultaneously.
- Two image optimization plugins competing on the same uploads.
Conflicts cause everything from minor bugs to a full white-screen-of-death. The fix is simple: run only one plugin per category.
How to audit your plugins
For each plugin currently installed, ask yourself a few questions:
1. Do I actually use this?
Many bloggers have plugins they activated months ago and then completely forgot about. If you don’t actively use it anymore, deactivate and delete it.
2. Is there a built-in alternative?
Some plugins handle things WordPress now does natively, or that your theme already handles. A few examples:
- The block editor now handles most layout needs that page builders used to require.
- Modern themes often include social sharing buttons, breadcrumbs, and related posts already. Aurora, for example, builds several of these directly into the theme, which removes the need for a separate plugin altogether.
- Some hosts include caching and security at the server level already.
3. Is there a leaner alternative?
Some popular plugins do far more than you actually need. Check whether a smaller, more focused plugin covers your real use case instead.
For example, Jetpack offers more than 30 features bundled together. If you only use two or three of them, install the focused standalone alternatives instead. They tend to be lighter, faster, and carry fewer dependencies.
4. Is this one of two plugins doing the same thing?
If the answer is yes, pick one and deactivate the other.
5. Is it well-maintained?
Run through your full plugin list. Anything not updated in the last 12 months or more should be replaced or removed.
The essentials for a typical blog
If you stripped a typical blog down to bare-minimum plugins, it would probably look something like this:
- SEO: Yoast SEO or Rank Math.
- Caching: WP Rocket, W3 Total Cache, or LiteSpeed Cache.
- Image optimization: Imagify or ShortPixel.
- Backups: UpdraftPlus.
- Security: Wordfence or Solid Security.
- Anti-spam: Akismet.
- Contact form: Fluent Forms or WPForms Lite.
- Analytics: Site Kit by Google.
That’s eight plugins total, and for most blogs, this represents the floor rather than the ceiling.
Add niche-specific plugins as needed on top of that (a recipe plugin for food blogs, e-commerce tools for stores, and so on). Most blogs end up running 10 to 20 active plugins total once everything settles.
When 30+ plugins is fine
Some sites legitimately need many plugins to function properly:
- Membership sites with multiple specific features to manage.
- E-commerce sites with payment, shipping, inventory, and marketing integrations.
- Multi-language sites with translation and SEO add-ons layered on top.
- Educational sites with course, quiz, and progress-tracking plugins.
These sites can run 30 or more plugins just fine, as long as each plugin is well-scoped and the hosting can actually handle the load.
When 5 plugins is too many
Some sites struggle even with just 5 plugins, because those particular plugins are bloated:
- A site running Jetpack, Yoast, two outdated security plugins, and an abandoned caching plugin all at once.
- A site running an old slider plugin that loads jQuery on every single page.
- A site running a page builder to do things the block editor would handle more efficiently.
The right question is never just “how many” but rather “are these the right ones, well-maintained, well-scoped, and not stepping on each other’s toes.”
How to test plugin performance impact
There are two reliable methods for this:
1. The deactivation test
Pick a plugin you’re unsure about. Run a PageSpeed Insights test before deactivating it, then deactivate it, then re-test and compare the results.
If deactivation produces no real improvement, the plugin is well-scoped, so go ahead and keep it.
If deactivation significantly improves your scores, the plugin is heavy, and it’s worth considering a replacement.
2. Query Monitor plugin
Install Query Monitor temporarily. It shows you exactly which plugins are slowest, what database queries they’re making, and where time is being spent on each page load. Deactivate Query Monitor once you’re done, since it’s meant to be a diagnostic tool rather than a permanent install.
The “more plugins, more security risk” reality
Every plugin is a potential security entry point, and the math behind that is real:
- 10 plugins means 10 potential attack vectors.
- 30 plugins means 30 potential attack vectors.
That said, well-maintained plugins carry low risk, while abandoned plugins carry high risk regardless of count.
The real security rule is this: only install plugins from reliable sources, only keep the ones you actively use, and only run plugins that are currently maintained. Five abandoned plugins are worse than 30 actively-maintained ones. For a deeper walkthrough of hardening a WordPress install beyond just plugin choice, see our WordPress security hardening checklist.
Choosing plugins carefully matters just as much when you’re installing your first one as it does years later during an audit. If you’re still getting comfortable with the basics, our guide on how to install a WordPress plugin the right way covers how to vet a plugin before you ever activate it, which heads off a lot of the bloat this post is about cleaning up.
Count less, scrutinize more
The number of plugins doesn’t matter nearly as much as people assume. Plugin quality, scope, and conflicts matter far more. Pick well-built, well-maintained plugins from reliable sources. Remove anything you’re not actively using. Avoid running duplicate-function plugins side by side. Test performance impact whenever you’re in doubt. A typical blog runs 10 to 20 active plugins comfortably. The “10 is the max” rule was already outdated a decade ago.
