I’ve been working on websites for small businesses for three years. I’m not a full developer, but I know enough to handle what needs to be done. I just got a new client and thought their site had 20 plugins. Turns out, they have two websites (members and non-members), and the second one has 81 plugins!
Some members are facing technical problems, which could be small fixes or something bigger, like a plugin compatibility issue. My first thought was they need a developer to clean this up and maybe build a custom solution. But as I keep working on it, I feel like I need advice from more experienced people before I suggest anything to the client.
Here are my questions:
Should I just walk away from this?
Can someone who isn’t a backend developer figure this out? (The plugins range from basic to pretty complex.)
Is this a job for a developer or just someone who really knows their way around plugins?
I’ve been fixing older websites for over 10 years, and it’s the main part of my work. Just because I’ve done it for so long doesn’t mean you can’t handle it too. Here’s my take on the ‘too many plugins’ issue and how you can approach it.
People often get hung up on the idea of ‘too many plugins’ and end up doing things like cramming everything into one big plugin or theme, which can create even worse problems. A plugin is just a tool with specific functions.
You said the second site has 81 plugins—probably the membership one. Membership sites often have a ton of features, and each of those might need its own plugin. For example, MemberPress has about 30 add-ons for different features. It’s better to keep those as separate plugins than to bundle everything into one big, bloated plugin.
Support plugins for those core tools (like payment gateways or shipping options).
Marketing or SEO tools.
Security and performance tools.
Plugins that are unnecessary or overlap.
Ask yourself:
Do they need all these plugins?
Are there duplicates or outdated ones?
Can any be replaced with simpler options?
Once you’ve mapped them out, create a backup and test the changes on a staging site. Disable plugins one at a time to see what happens. It’s a tedious process, but it’ll help you figure out what’s truly needed.
@Briar
Great advice . I’d add that duplicate plugins are a huge problem. I’ve seen sites with three Mailchimp plugins or multiple Google Analytics plugins—sometimes not even set up properly. A quick spreadsheet listing what each plugin does and whether it’s active can help clean things up.
@Briar
Thanks for breaking this down! You’re right—membership sites come with a lot of plugins for all those extra features. I appreciate the detailed response!
Dax said: @Briar
Thanks for breaking this down! You’re right—membership sites come with a lot of plugins for all those extra features. I appreciate the detailed response!
Think of it like this: if all those functions were packed into one custom plugin, who would maintain it when things go wrong? Multiple plugins mean you have dozens of developers updating their tools for you—often for free. As long as the plugins are reliable, it’s a safer option.
Dax said: @Briar
Thanks for breaking this down! You’re right—membership sites come with a lot of plugins for all those extra features. I appreciate the detailed response!
Don’t feel bad for being overwhelmed. Any developer would raise an eyebrow at 81 plugins. Sometimes it’s better to start fresh, but you’ve got a great answer here to guide you.
It depends on the plugins. Sometimes, a small function is uploaded as a whole plugin. The person who built the site might have been experimenting. I’d figure out what the site actually needs, remove duplicates, or even rebuild it and import the content. The database could be a mess if this is a result of trial and error.
@Jai
This answer assumes the worst. Many sites with 80+ plugins run just fine when managed well. It’s more about the quality of the plugins, not the number.
Drew said: @Jai
This answer assumes the worst. Many sites with 80+ plugins run just fine when managed well. It’s more about the quality of the plugins, not the number.
Fair point! The wrong plugins can leave junk in the database, but with good management, it’s not a problem.
81 plugins might mean the site has been worked on by multiple people, some experienced and others not. Some plugins could be replaced by simpler solutions.
Should you walk away? That’s up to you.
Yes, it’s possible to handle.
This might need someone with solid WordPress experience.
81 plugins can cause overlaps. For example, two plugins might try to optimize images or enable lazy loading, which can create conflicts. You’ll need to go through them one by one and disable what’s not needed. It’s tedious but doable.
No WordPress site needs 81 plugins. That’s just asking for trouble with compatibility and maintenance. I’d recommend reducing the plugin count or going for custom solutions.
Maddox said:
No WordPress site needs 81 plugins. That’s just asking for trouble with compatibility and maintenance. I’d recommend reducing the plugin count or going for custom solutions.
This is outdated thinking. Well-maintained plugins from reputable sources work just fine. Many complex sites use 80+ plugins efficiently.
. I’d add that duplicate plugins are a huge problem. I’ve seen sites with three Mailchimp plugins or multiple Google Analytics plugins—sometimes not even set up properly. A quick spreadsheet listing what each plugin does and whether it’s active can help clean things up.