When a site breaks and a plugin is suspected, the usual responses are: the manual deactivate-everything ritual, a staging copy, or a troubleshooting-mode plugin. Here's the honest breakdown against all three.
The manual ritual toggles real plugins on the live site — visitors watch the site fall apart while you work, and a 30-plugin stack can mean 30 rounds of it. Staging copies are safe but slow: an hour of cloning before the first test, and intermittent conflicts often refuse to reproduce away from the live data. Troubleshooting-mode plugins made the ritual safe — they isolate your session — but they hand you the toggles and leave you to run the elimination in your head. WP Conflict Radar (this site) runs the actual binary search: it halves the suspect list with every YES/NO answer, finds conflicting pairs, admits when the cause isn't a plugin at all, and — on Pro — writes the whole investigation up as a branded report with a PDF.
| Feature | WP Conflict Radar | Manual ritual | Staging copy | Troubleshooting mode |
|---|---|---|---|---|
| Visitors untouched | ✓ Session-scoped, always | ✗ They watch it break | ✓ Different site entirely | ✓ Session-scoped |
| Steps on a 30-plugin site | ✓ About 5 (log₂ n) | ✗ Up to 30, by hand | ✗ Up to 30, plus the clone | ✗ Up to 30, you keep score |
| Runs the elimination for you | ✓ Wizard-led, YES/NO answers | ✗ You, at 11pm | ✗ You, on the copy | ✗ You, with safer toggles |
| Finds conflicting pairs | ✓ Pair refinement built in | ✗ Each looks innocent alone | ✗ Same blind spot | ✗ Single-plugin thinking |
| Honest when it's not a plugin | ✓ Control step → not_plugin | ✗ Blames the last toggle | ◐ If you think to check | ✗ Not its question |
| Reproduces live-only conflicts | ✓ Tests the real site | ✓ The real site, sadly | ✗ Often won't reproduce | ✓ The real site |
| Time before the first test | ✓ Under a minute | ✓ Immediate — and live | ✗ An hour of cloning | ✓ Minutes |
| Evidence to hand the client | ✓ Branded report + PDF (Pro) | ✗ A war story | ✗ Nothing standard | ✗ Nothing on paper |
| Watches after updates | ✓ Post-update canary (Pro) | ✗ | ✗ | ✗ |
| Cost | From $49/yr · $599 lifetime | Free — plus the risk | Staging hosting + hours | Free or cheap |
You're planning a risky migration or a major version upgrade — that's staging work, test the whole change there. Or you run one small site with six plugins and a quiet audience; the manual ritual is genuinely quick at that size, and troubleshooting mode makes it safe.
You look after live WordPress sites where downtime is visible and “which plugin did it?” is a recurring question. You want the elimination run for you in log₂(n) steps, in your session only, with the culprit — or the conflicting pair — named at the end, and on Pro, a branded report to attach to the invoice. That's us.
One honest line: the canary's post-update check is server-side — it fetches and inspects the rendered homepage, it doesn't run a browser. And when the cause isn't a plugin, the verdict says so rather than inventing a culprit.