If you’ve used WordPress for a while, I’m sure someone has told you that you “shouldn’t use too many plugins”. It’s obvious – using too many plugins will slow your WordPress site down, right?
But is that actually true? I mean, people tell me I shouldn’t swim after eating, but I’ve done that my whole life and I’m still alive and kicking! So is the common knowledge that “too many plugins is bad” good for WordPress?
In this post, I’m going to attempt to answer that question. So, if your admin sidebar is bursting at the seams with links to plugin settings pages, join me on this adventure into the world of plugin collecting.
Is Having Lots of Plugins Always Bad?
Let’s start at the beginning. I’m not a developer, but in my reading, I’m fairly certain that I’m accurate in saying that there’s nothing inherently wrong with having lots of plugins.
I mean, I remember reading somewhere that Pippin Williamson has over 80 plugins running on some of his sites! Pippin knows a thing or two about plugins, so I’m going to trust him on this one.
In a perfect world populated with perfect developers, all plugins would be coded to the highest standards and constantly maintained. If we all lived there, we could pretty much install plugins until the cows came home.
But here’s the thing…
We don’t live in that world. Far from it actually. I mean, just take a look at some plugin lists from a few years ago. It’s so easy to find plugins that once were popular but now have fallen into disrepair. They look like this:
They once were great, but now they look like they’re straight out of a zombie movie.
So even if plugins start off perfectly coded and optimized, two years without updates can easily change things.
Plugins Don’t Have Equal Impact
There’s another concept that makes it difficult to give a simple answer like “you should always have fewer than 50 plugins”
See, you can have 30 plugins making all kinds of minor tweaks. And maybe they result in almost zero hit to your site’s performance.
But then you can have one plugin which tanks your site’s performance with heaps of database queries and HTTP requests. So 30 “small” plugins might well have a smaller effect on your site than one “big” plugin.
I mean – look at it logically – why would you treat WooCommerce the same as the “Disable Emojis” plugin? Sure, each is “one” plugin, but WooCommerce creates a whole friggin’ eCommerce store while Disable Emojis just removes one line of code from your site.
That’s why it’s silly to just look at the raw number of plugins you have installed. The real situation is more complicated than that.
What Are the Practical Problems With Installing Lots of Plugins?
Ok, I’m moving on from “perfect world” to “real world”. Because I think there are some real issues which might arise from telling people they’re free to install as many plugins as they’d like.
These issues do not automatically come with installing lots of plugins, but I’m willing to bet they correlate well with inexperienced users who install a large number of plugins.
If you’re installing plugins which are processor-intensive or add database queries or HTTP requests to your site, they’re probably going to drag down your site’s performance. If the plugin is adding tons of new scripts and requests, it’s always going to result in at least some hit to your site’s performance.
Install enough of those plugins and your site’s gonna grind to a halt.
Plugin vulnerabilities are one of the common ways for hackers to get into your site. Just 3 major plugins (which also happen to be the plugins bundled with many ThemeForest themes) accounted for a huge chunk of hacked WordPress sites according to Sucuri.
WPScan also maintains a database of plugin vulnerabilities. Let’s just say the database is not hurting for entries…
So each time you install a new plugin, you might just be buying an entry ticket to the plugin vulnerability lottery.
Ever installed a new plugin and had it break one of your existing plugins? I know I have. Each time you add a new plugin, you’re increasing the chance of that happening (even if it’s only ever-so-slightly higher).
This is kind of a throw-in – but have you ever seen those admin menus which are packed to the gills? I can’t imagine working in that WordPress dashboard. Maybe it’s the minimalist in me, but I like my workspaces simple!
Of course, you can always use something like Admin Menu Tweaker to get some control over your admin menu.
So What’s the Solution?
When you add a new plugin, you should consider what it actually does. If it’s:
- Adding HTTP requests
- Increasing database queries
- Eating up processing power
Then you should probably think long and hard about whether you actually need that plugin. Because if you add too many of those plugins, you will slow your site down.
There are some plugins, Broken Link Checker for instance, which people install without a second thought. Those are the plugins you need to watch out for! Database queries out the whazoo.
On the other hand, if you’re installing a plugin that’s just adding a bit of static code or tweaking something minor, you should be safe (as long as it’s coded properly).
Some people, myself included, even recommend creating custom plugins to add code snippets instead of always using functions.php. Obviously, a plugin that only adds a sole code snippet is not likely to hurt your site.
To figure out which of your plugins are causing the largest hit, you can use P3 (Plugin Performance Profiler). You can also go the manual route and deactivate all of your plugins. Then, slowly reactivate them one by one to find out which are slowing down your site.
And finally, you can also check out what types of requests your plugins are making by using the Network tab of Chrome Developer Tools.
So, is there such a thing as “too many WordPress plugins”? Not in a perfect world. But in the real world, I bet that if you install plugins willy-nilly, you’ll increase your chance of encountering performance or security issues.
That’s why I still think that the idea of running as few plugins as possible is a good one to propagate throughout the WordPress ecosystem. We need to remember that WordPress users are not always tech-savvy.
Beginners don’t know how to analyze HTTP requests and database queries – so telling them that they need to use as few plugins as possible is a good way to minimize the issues they encounter, even if it’s not 100% “true”.
But it’s by no means an unbreakable rule. As long as you look at what the plugins you add are actually doing, you don’t need to worry about passing some arbitrary maximum for the number of plugins on your site.
Now I want to hear your thoughts – how many plugins do you have installed on your site? Don’t be shy! Let’s see who has the highest number.