
It starts innocently. One plugin to duplicate posts. Another to allow SVG uploads. One for SMTP, one for login limits, one to hide the admin bar, one to clean the database. A couple of years later the site has 40 plugins, the admin is slow, and every update day feels like a gamble.
The number of plugins isn't the real problem on its own. A single badly written plugin can do more harm than ten good ones. But every plugin adds code to load, settings to manage, updates to apply and one more possible conflict. Here's how to trim the list without losing anything you actually use.
Step 1: Make a plugin inventory
Before you deactivate anything, take a full backup, then list every plugin in a spreadsheet with four columns:
- What it does, in one sentence.
- Where it's used: front end, admin only, or both.
- Last updated (shown on the plugin's WordPress.org page).
- Keep, replace or remove.
You'll usually find a few plugins nobody can explain. Those are the first to investigate.
Step 2: Remove what you no longer use
Inactive plugins should be deleted, not just deactivated. Deactivated plugins still sit on the server, and a vulnerable one can still be exploited in some cases. Also look for plugins that solved a one-time job, like a migration or an import, and were never removed.
Step 3: Replace abandoned plugins
A plugin that hasn't been updated in a year or more, or that WordPress.org marks as untested with recent versions, is a security risk waiting to happen. Find a maintained alternative, or a plugin you already have that covers the same feature.
Step 4: Consolidate the small utilities
This is where most of the savings are. Many sites run a dozen single-purpose plugins for small tweaks:
- login page branding and login limits;
- duplicate posts and pages;
- SVG uploads and default featured images;
- admin footer text, dashboard widgets and toolbar tweaks;
- email sender name, SMTP and email logs;
- disabling emojis, embeds, XML-RPC and other unused features;
- database cleanup.
An all-in-one utility plugin can replace most of these with one settings screen and one update. The free All-in-One Utilities plugin, for example, groups user, login, security, media, admin, performance, content and email tools, and you switch on only the modules you need, so unused features don't load.
Be careful with plugins that do one big, complex job well (e-commerce, forms, SEO, page builders, membership). Those usually deserve to stay as dedicated plugins.
Step 5: Test one change at a time
On a staging copy of the site, remove or replace one plugin, then check the pages it affected. Compare speed in PageSpeed Insights and click through the admin. When everything checks out, repeat on the live site. Going one plugin at a time makes it obvious what caused a problem if one appears.
Step 6: Keep it lean
Agree on a simple rule for your team: before installing a new plugin, check whether an existing one already does the job. Review the list every few months, the same way you'd review software subscriptions.
What you gain
- Faster pages and admin: less code loaded on every request.
- Fewer conflicts: fewer plugins competing for the same hooks.
- Safer updates: less to update and less that can break.
- A smaller attack surface: fewer places for vulnerabilities to hide.
If you'd rather not do the audit yourself, a WordPress care plan usually includes a plugin review as part of onboarding. Either way, an afternoon spent trimming plugins pays you back every time you update.
Written by the team at WordTenance, who look after WordPress and WooCommerce sites for small businesses and build the All-in-One Utilities plugins. Visit wordtenance.com.
