How Many WordPress Plugins Is Too Many?

Every few months someone forwards me the same worry, usually picked up from a friend or a hosting support agent: you have too many plugins. It arrives with a lot of confidence and no number attached, which leaves the business owner anxious and none the wiser. So here is how I actually think about it, after years of opening other people's WordPress sites and working out why they drag.

There is no magic number

Nobody can tell you the right count without looking at the site. I have opened installs running eight plugins that crawl, and installs running thirty five that load in under a second. Plugin count gets blamed because it is the one number a non-developer can see. What matters is what each plugin does on every page load, and whether two of them are quietly doing the same job in different ways.

If you want a rough steer, the small business sites I build usually settle somewhere between twelve and twenty active plugins. Under that and you are often paying me to write code that a well maintained plugin would have handled for nothing. Over thirty and I would want a proper look before I said anything either way.

What actually causes the damage

Three things, roughly in the order I find them.

The first is plugins that load their own CSS and JavaScript on every page, whether the page uses them or not. A slider plugin used once on your homepage that ships its assets to all two hundred pages of your site is a real cost, paid by every visitor.

The second is plugins that hit the database hard on every request. Related posts widgets, live visitor counters, some booking calendars. One of these can do more harm than ten quiet ones.

The third is overlap. Two security plugins, or a caching plugin fighting a cache your host already runs, and you get the worst of both. I see this constantly on sites that have passed through three or four different hands.

None of those problems is really "too many". They are all the wrong ones, configured badly.

The audit I run

When someone asks me to look, this is the order I work in:

• Sort the plugin list by last updated. Anything untouched for two years goes on the danger list, for security as much as for speed.

• Load the site with the browser network tab open and see which files come from which plugin folder. The expensive ones show up in about a minute.

• Deactivate in small batches on a staging copy and re-measure. Tedious, but it is the only way to be sure what a given plugin costs you.

• Check for duplicated jobs: SEO, contact forms, security, caching, image handling. One plugin per job.

• Read the settings of anything that stayed. Half the wins are a checkbox someone never turned off.

I do all of this on a copy of the site, never the live one. If you have no staging environment yet, that is the thing to fix before you touch a single plugin. I wrote about how I set that up in backups and staging.

The ones I nearly always remove

• Single feature plugins doing something a few lines of theme code would handle: a phone number in the header, a custom post type, a simple redirect.

• Anything abandoned by its developer, no matter how well it still appears to work.

• The second SEO plugin that someone installed, half configured, and forgot about.

• Stats plugins that duplicate what your analytics already tells you, while writing a row to your database on every page view.

• Page builders, when the site only ever used them to stack a heading on top of an image. I am not against builders in general, and I said so in when a page builder is genuinely fine, but a lot of sites carry the weight without using the tool.

What I keep without arguing

One SEO plugin. One form plugin. One backup plugin. Security, if the host is not already covering it. Caching, same test. And then whatever actually runs the business: the shop, the booking system, the membership area. That last group is the point of the site, so it gets judged on whether it works, not on the plugin count.

How to remove one safely

Take a backup. Deactivate rather than delete, and leave it deactivated for a fortnight. Walk the pages that used it, including the ones you never look at, and check your contact form still sends. Then delete it properly, because a deactivated plugin still needs updating and can still be a way in.

Watch for what gets left behind. Plenty of plugins leave database tables, scheduled jobs and shortcodes in your content that turn into visible junk on the page once the plugin is gone. Search your posts for the shortcode name before you delete anything.

So what is too many?

Here is the honest test. Too many is the point where you cannot say out loud what each one does. Open your plugins list and read down it. If there are five names you do not recognise, the number is too high for you, whatever it might be for someone else. A site you understand is a site you can maintain, and maintenance is what keeps it fast a year from now.

If your site feels slow and the plugin list is a mystery, that is a good use of a free 30 minute surgery. I will open it up with you, tell you what is costing you time, and you can take that away and act on it yourself or ask me to. Either is fine. There is more on how I look after WordPress sites on my WordPress page, and if you want the wider speed picture first, start with why your WordPress site is slow.