Some background
This WordPress website was built by the owner and relied on 20+ plugins – many of which we couldn’t even confirm were in use.
I see this a lot. People add plugins to introduce new features. Sometimes they test several to find “the best one”, then forget to delete the ones that didn’t make the cut. Other times, they don’t realise they already have plugins installed that include the functionality they’re now trying to add.
The result is a mess they don’t dare to touch because they don’t know which plugins are actually doing something, or whether deleting one might break content on the front end.
And so the mess grows…
…until it breaks, and they have no idea where to start.
Troubleshooting the problem
Luckily, in this case, troubleshooting was fairly straightforward, as WordPress clearly displayed the error. Well — clearly for me, anyway. With a developer background and familiarity with the back end, it made sense. For the client, it was just a wall of error messages causing stress.
As it turned out — lo and behold — a plugin update had indeed caused the issue.
After some testing, we found the plugin wasn’t even needed.
Which was lucky, as it made the fix as simple as deleting it.
Annoying, though, because the problem was entirely preventable.
Key takeaway learnings
(aka: how not to end up here)
Too many plugins = zero clarity
Problem: When every plugin is marked active, it’s impossible to know what’s actually in use. Plugins, unfortunately, don’t announce themselves with “I’m doing something important!”
Takeaway: When testing plugins, delete the ones that aren’t the right fit. At least then you’ll know what’s left is there for a reason.
You may already have what you need
Problem: Most plugins (unless very niche) offer multiple features. People often install new plugins without realising existing ones already cover the same functionality.
Takeaway: Before installing anything new, check what your current plugins can do. If that feels overwhelming, give ChatGPT (or another AI tool) a list of your current plugins, explain what you want to achieve, and ask if any of them already support it. It’s often just a hidden setting.
Plugins don’t make a site “professionally built”
Problem: Installing and activating plugins doesn’t make you — or your “developer” — a developer. Plugin-heavy sites are often fragile and unpredictable.
Takeaway: Save money where you need to, but factor in the cost of time, stress, and things breaking. If upfront investment isn’t an option but you still want professional support, RentaSite is a solid alternative.
Discuss my website options(And yes, we will be rebuilding the site in question sometime this year.)
