Loupely› Loupely vs. Competitors› Plugin Detective
Plugin Detective is a free WordPress plugin that walks you through toggling your plugins on and off until the problem disappears — isolating the conflict by process of elimination. It’s honest, it works, and it requires the bug to still be happening while you run it. Loupely reads what the browser and server captured when the failure occurred and names the cause before you open a single diagnostic panel.
It’s conflict isolation by process of elimination. Useful, manual, and it needs the bug to still be there.
Plugin Detective is a free WordPress plugin with 5,000+ active installs, built by NSquared (the team behind Simply Schedule Appointments). When something breaks on your site, you click “Troubleshoot” and it opens a wizard called Otto Bot. Otto divides your active plugins into groups, disables half, and asks you if the problem is still happening. Through several rounds it narrows down to the culprit. No coding required. Works on any page, front end or admin.
For an active, reproducible conflict — something you can consistently trigger right now — Plugin Detective’s approach is sound. It automates the manual disable-and-test loop that WordPress support has recommended for years. It’s honest about what it is: a structured elimination process. When the problem is still happening and you have 20 minutes, it reliably finds the plugin at fault.
Plugin Detective requires the bug to be actively happening while you run it. If the site is fully crashed, if the problem only occurred during an overnight update, or if the failure happened once and the site came back up on its own, Plugin Detective has nothing to test against. It also reads no server logs, no browser evidence, and produces nothing you can send to a developer.
Loupely’s approach is the opposite. It captures browser and server evidence at the moment of failure — before you open any diagnostic tool. State snapshots record your site before every plugin change. When something breaks, Loupely already has the before-state, the error logs, the browser events, and the plugin change history. It names the cause without requiring the problem to still be live.
Your checkout stopped working after last night’s plugin updates. You found out this morning.
The problem: orders have been failing since 2am. You have 4 plugins that updated overnight.
Works — as long as the checkout failure is reproducible right now in your session. Takes 15–25 minutes depending on plugin count. Reads no server evidence. Produces nothing to send a developer.
No rounds. No manual testing. The capture happened automatically at 1:58am. You open the diagnosis, read the answer, do the rollback.
Plugin Detective finds conflicts through elimination. Loupely reads the evidence directly.
| Capability | Plugin Detective | Loupely | |
|---|---|---|---|
| Identifies which plugin is causing a conflict | |||
| Requires no coding to use | |||
| Works when the problem is no longer actively reproducible | |||
| Reads server-side logs: PHP errors, crash evidence | |||
| Reads browser evidence: what the browser received, failed requests | |||
| Records state before every plugin change — before-state on record at time of failure | |||
| Produces a shareable capture file with all evidence for a developer | |||
| Continuous uptime monitoring with alert when the site goes down |
The method you use depends on whether the problem is still happening right now.
Plugin Detective is a detective. Loupely is a recorder that was already running when the crime happened.
The problem is happening right now and you can reproduce it
If you can trigger the issue on demand — you visit the page and the problem is consistently there — Plugin Detective’s elimination process is a legitimate approach. It’s free, it requires no server knowledge, and for a straightforward plugin conflict it reliably narrows to the cause in a few rounds. Install it and keep it ready.
The failure happened overnight, or the site is currently down
Plugin Detective can’t test what already happened. If your site crashed at 2am and came back up by itself, there’s nothing for the wizard to test against. If the site is fully down and you can’t load the admin, the wizard can’t run. Loupely captures the evidence as it happens and holds it for you — the before-state, the crash logs, the browser evidence. The answer is in the capture whether or not the problem is still live.
You want to cover both the past and the present
Keep Plugin Detective installed for the times you catch a conflict in the moment. Keep Loupely running for everything else: overnight failures, intermittent breakdowns, problems that come and go, and anything you need to send to a developer with supporting evidence. They don’t overlap — they cover different gaps.
Plugin Detective’s approach modifies your site’s plugin state during testing.
Plugin Detective’s isolation runs only in your browser session — visitors see the site normally — but it does disable plugins in your admin session during testing. On some server configurations, particularly with Nginx or certain security plugins, activating Plugin Detective itself can trigger access errors. Reviews on WordPress.org include a small number of cases where it caused 403 or database errors on activation. Worth testing on a staging environment first if you’re on a custom server setup.
The evidence is already captured before you know there’s a problem.
State snapshots run automatically before every plugin change. When something breaks, the before-state is already on file. One click reads the browser and server together and names the cause.
Install once. It records automatically.
The WordPress plugin and Chrome extension take about 5 minutes to set up. Once connected, Loupely snapshots your site’s plugin state before every update — no manual action required. Monitoring runs every 5 minutes and alerts you if the site goes down.
When something breaks, click Capture.
One click reads browser and server together: PHP errors, failed HTTP calls, active plugins and versions, and the plugin change history since the last healthy state. Everything correlated in one structured file. The capture file is always free to download and send to a developer.
Read the answer. Fix it or send it.
The diagnosis names the specific plugin that caused the failure, explains why in real human terms, and gives you the exact next step: roll back this version, contact your host about this error, or send your developer this file. No rounds. No toggling.
Common questions about Loupely vs. Plugin Detective.
Plugin Detective found the conflicting plugin. Can Loupely tell me anything more?
Yes. Plugin Detective tells you which plugin is involved. Loupely tells you which version update caused it, what the specific PHP error was, what the browser received, and whether you can roll back yourself or need to contact the developer. For anything you need to escalate or document, the capture file gives the developer everything needed to write a fix without a follow-up question.
My site is fully down and I can’t get to the admin. Can either tool help?
Plugin Detective requires admin access and an active session to run. When WordPress can’t load, the wizard can’t start. Loupely’s Black Box feature writes a crash snapshot to a flat file even when the database is unreachable. And because Loupely records state snapshots before every plugin change, the before-state and plugin history are often already captured — available in the dashboard even when the site itself is down.
Plugin Detective is free. What does Loupely cost?
Installing Loupely and running captures is free. A diagnosis costs one credit ($1.90 per credit, or $1.45 if you buy a 20-pack). The Loupely Annual plan is $99/year. For most site owners, one Loupely diagnosis costs less than 90 seconds of developer time — and it often removes the need to contact a developer at all.
Plugin Detective’s troubleshoot wizard changes my plugin state. Is that risky?
Plugin Detective disables plugins only in your browser session — other visitors see the site normally. The risk is low on standard setups. On some server configurations (particularly Nginx with strict security plugins like Wordfence or Solid Security), activating Plugin Detective itself can trigger 403 access errors or database issues. A handful of WordPress.org reviews document this. Loupely doesn’t disable or modify any plugins at any point. It reads evidence; it doesn’t interfere with plugin state.
What’s the difference between Loupely and Loupely Lens?
Loupely handles functional failures: site down, checkout not processing, form not sending, login broken. It requires the WordPress plugin. Loupely Lens handles visual failures: wrong color, layout off, text overlapping. It’s a Chrome extension that works on any website. One account, one credit pool.
A website can fail in two ways. Something stops working. Something looks wrong.
Loupely and Loupely Lens cover opposite ends of what can go wrong. One account, one credit pool.
Something stopped working.
Site down. Checkout failing. Form not sending. Login broken. Plugin conflict after an update. Loupely captures browser and server evidence, records the before-state, monitors continuously, and names what broke and what to do next. WordPress.
Something looks wrong.
Button wrong color. Section won’t center. Text overlapping on mobile. Lens clicks on what looks wrong, reads the full CSS cascade, and tells you what’s causing it and what to change. Any website in Chrome.
The evidence was captured before you knew there was a problem.
Free to install. Free to capture. One credit for the diagnosis. Always-on monitoring included.