Most plugin audits start in the wrong place. Someone opens the Plugins screen, counts the rows, and decides the site has "too many plugins." That is tidy, but it is not very useful.
A site with twelve careful plugins can be lighter and easier to maintain than a site with four giant plugins that all load global assets, duplicate features, and quietly fight over the same hooks.
The better question is: what job does each plugin do, and what does that job cost on the front end, in the editor, and during support?
Start with the jobs
I like to put plugins into plain categories:
- Must-have infrastructure: security, backups, forms, analytics, commerce, SEO.
- Workflow helpers: cloning content, template controls, imports, admin utilities.
- Visitor-facing features: search, filters, popups, course pages, checkout improvements.
- Unknowns: anything nobody can explain in one sentence.
That last bucket is where the audit usually pays for itself.
If a plugin has no owner, no clear job, and no visible output, do not delete it immediately. First, look for shortcodes, blocks, widgets, custom post types, scheduled tasks, and database tables. A tool like Plugin Detective exists for exactly that kind of boring, necessary work.
Look for overlap, not just weight
The worst plugin stacks are not always the heaviest. They are the ones where three tools each handle a slice of the same job.
One popup plugin captures emails. A form plugin also captures emails. A theme option panel injects header scripts. An SEO plugin injects schema. A separate schema plugin injects another version of the same thing.
Overlap creates support drag. When something breaks, nobody knows which setting owns the output.
Keep the small tools small
This is the main idea behind the PDS free plugin line. A focused plugin should do its job, expose the few settings that matter, and stay out of the way. Clone It should clone content cleanly. Speed Lite should help with performance basics. Backup Migrate Lite should make safety work less fragile.
The Pro suites can go deeper, but the free tools should still be useful on their own.
Tie plugins to the rest of the stack
Plugins do not live alone. A fast theme from PDS Themes and sensible hosting from PDS Hosting change what your plugin stack needs to compensate for.
If the theme is already clean and the server is already tuned, you can stop installing plugins to fix problems that should not exist in the first place.
The goal is not a tiny plugin count. The goal is a site where every plugin earns its place.