Guide
How many WordPress plugins is too many?
There is no fixed number: a site with 40 well built plugins can run faster than one with 8 poorly built ones. What matters is the quality, the job each plugin does and how much it loads on every page. A good rule is to keep only plugins you actively use, from developers who keep them updated, and remove the rest.
The myth
Why the number on its own tells you little
You will often read that more than 20 plugins is too many, or that every plugin slows your site down by a set amount. Neither claim holds up. A plugin is just code, and code costs whatever work it does. A tiny plugin that adds a single setting may do almost nothing on most pages. A single large plugin that loads scripts, styles and database queries on every page can do far more harm than ten small ones put together.
So the useful question is not how many, but which ones and what they do. Does the plugin run on every page or only in the admin area? Does it load scripts and styles on pages that never need them? Does it make database queries or call outside services on each request? Is the developer still maintaining it? These matters decide the real cost, and none of them can be read from a count.
That said, plugin count is not meaningless. Each one is a piece of software that you must keep updated and trust. More plugins mean more updates, more places for a conflict and more things that can be abandoned. So the sensible goal is a lean site where every plugin earns its place, whatever the number turns out to be.
The real costs
What a plugin can cost your site
Speed
Extra scripts, styles and queries on each page request.
Security
More code that can contain a weakness, especially if it is outdated.
Conflicts
Two plugins fighting over the same job can break layouts or features.
Maintenance
Every plugin is another thing to update, test and eventually replace.
Fast hosting makes plugins cheaper to run
LiteSpeed and Redis object caching on every plan.
Weigh them
Light, medium and heavy plugins
| Type of plugin | Typical load | Examples of the job | What to check |
|---|---|---|---|
| Admin only tools | Light on visitors | Backup, import and export helpers | Do they run on the front end at all? |
| Small front end features | Light to medium | Cookie notices, social links, simple forms | Do they load files on every page? |
| Page builders | Medium to heavy | Drag and drop layouts | Is their output lean for your design? |
| Sliders and galleries | Medium to heavy | Image carousels and portfolios | Do they use large scripts and images? |
| Shop and membership | Heavy by nature | Products, baskets, accounts | Are they well supported and cached correctly? |
| Security and caching | Varies | Firewalls, login protection, speed tools | Do they overlap with your hosting tools? |
Where it hurts
Speed: which plugins really slow a site down
The plugins that hurt performance most are usually the ones that do work on every page load for every visitor. Page builders, sliders, social feeds, related post engines, live chat widgets, pop-ups and tracking scripts all load files and often make external requests. Security plugins that scan files constantly can also make the admin area sluggish.
You can see the effect with testing. Use a speed testing tool on a key page and look at the list of files loaded. If one plugin brings in several scripts and style sheets that you do not need on that page, you have found a culprit. Tools that profile database queries can show which plugin is making them, and they are worth using on a site that has become slow without a clear reason.
Good hosting changes the equation. With LiteSpeed page caching, most visitors receive a stored copy of the page, so plugin code does not run again for each of them. Redis object caching reduces repeated database work in the admin area and on uncached pages. Our guide on speeding up a WordPress site goes through the steps in order.
Audit
How to audit your plugins in an hour
List everything installed
Open the Plugins screen and write down every plugin, active or not, with its version.
Say what each one does
Next to each, write the job it does. If you cannot say, that is a flag.
Delete the inactive ones
Deactivated plugins can still be attacked. Delete those you do not need.
Check update history
Look at each plugin's page for the last update date and the reported compatibility. Anything untouched for a year or more needs a replacement plan.
Find overlaps
Two caching plugins or two SEO plugins is a problem. Keep one of each and remove the other.
Test the speed effect
On a staging copy, disable suspect plugins one at a time and compare page speed.
Write a keep list
Record what stays and why, and review it every few months.
Keep or cut
Plugins to keep and plugins to question
Usually worth keeping
- A page caching plugin that fits your host
- A well supported SEO plugin
- A trusted form plugin
- Your shop or booking plugin if you use it
- A backup plugin if you want extra copies
Worth questioning
- Plugins that duplicate a built-in feature
- Several plugins for tiny jobs
- Anything not updated in a year
- Plugins you cannot explain
- Multiple security or caching tools overlapping
Security
The security side of plugin count
Outdated and abandoned plugins are a leading way WordPress sites get compromised. A plugin is code running with the full power of your site, and a weakness in it can give an attacker a way in. The more plugins you have, the more vigilant you must be, but a short list of poorly maintained plugins is still worse than a longer list of carefully maintained ones.
Only install plugins from the official directory or from developers you can identify, and never use pirated copies of paid plugins, which are a favourite hiding place for malware. Our WordPress security guide lists the full set of precautions. On the server side, we add Imunify360 scanning, a ModSecurity firewall and CloudLinux isolation to every account, but a good server cannot rescue a vulnerable plugin on its own.
If a plugin you rely on is abandoned, plan to replace it. Look for an actively developed alternative, test it on staging and switch over at a quiet time. Putting it off only lets the risk grow.
Smarter choices
Fewer plugins without losing features
Sometimes a plugin does a job that your theme or WordPress already handles. Modern themes include features such as custom fonts, simple sliders or social links. WordPress itself now includes a flexible block editor, so you may not need a separate plugin for columns, buttons or galleries. Check what you already have before adding more.
Where you need a plugin, prefer one with a narrow, well defined purpose from an active developer. Avoid giant bundles that include dozens of modules when you use two. If a feature can be done with a short, well tested snippet of code, a child theme or a small code snippets plugin may be lighter than a full plugin. Keep any custom code documented so the next person can understand it.
Rules of thumb
A simple plugin policy
- Every plugin has a clear job
- Only one plugin per job
- Updated within the last year
- Installed from a trusted source
- Inactive plugins deleted, not left idle
- Tested on staging before major updates
- Reviewed every quarter
- Backups taken before changes
Want a second opinion on your site?
Tell live chat what is slowing you down and we will point you in the right direction.
FAQ
Common questions
Is 30 plugins too many?
Not necessarily. Quality and what they load matter more than the number. Audit them and remove anything you do not use.
Do inactive plugins slow my site?
They do not run, but they still add clutter and can be attacked if vulnerable. Delete the ones you do not need.
Should I use a security plugin as well as hosting security?
Our hosting adds scanning and a firewall. A login protection plugin can still help, but avoid several overlapping tools.
How do I find which plugin is slow?
Disable plugins one at a time on a staging copy and test speed, or use a query profiling tool.
Will better hosting let me use more plugins?
Faster hosting gives you more headroom, but you still need to keep plugins few, current and useful.
Keep reading
Related pages
Give your plugins fast hosting
LiteSpeed, Redis and Imunify360 on every plan.