You have multiple site health or audit plugins running. Each one scans your site independently, uses server resources, and may give conflicting advice. One trusted scanner is all you need.
Why This Matters
Multiple scanning/audit plugins:
- Duplicate server load — each runs its own checks against your database and files
- Conflicting advice — one may recommend actions the other warns against
- Notification fatigue — overlapping alerts make it harder to focus on real issues
- Dashboard clutter — multiple admin panels with overlapping information
How to Fix It
Step 1: Compare Your Scanners
List the audit/health plugins you have active. Common overlap:
| Plugin | Function |
|---|---|
| WordPress Site Health (built-in) | Basic environment checks |
| Health Check & Troubleshooting | WordPress team's extended diagnostics |
| Dravasite | Conflict detection + actionable insights |
| Query Monitor | Developer debugging (different scope) |
Step 2: Keep What's Most Useful
- Dravasite covers conflict detection, environment checks, and actionable guidance — that's the core of site health
- WordPress built-in Site Health is always there (can't remove it), provides basic checks
- Query Monitor is developer-focused — keep it if you're a developer, remove if you're not
Step 3: Remove the Rest
Deactivate and delete any scanners that overlap with your chosen tool. Fewer plugins = less overhead.
What to Watch For
- Security scanners (Wordfence, Sucuri) are different from health/audit plugins. They serve a different purpose and should be kept if you need security monitoring.
- Performance plugins (like WP Rocket) may have some health checks but are not full scanners — they can coexist with a health plugin without conflict.
- WordPress's built-in Site Health is lightweight and always available — it doesn't need a separate plugin.
