How Loupely Works · WordPress Diagnostic
Loupely · WordPress diagnostic
Your site just broke.
Five seconds from now, you’ll know why.

Chrome extension plus WordPress plugin. One click. Browser and server read simultaneously. A verdict in real human terms. The exact next step.

Free to install · Capture always free · Credit refunded if wrong

Loupely CAPTURED

Diagnosis

Your caching plugin updated two days ago and broke the WooCommerce checkout hook. The session handler is returning null.

Next step

Deactivate WP Super Cache, test checkout. If resolved, update or replace the plugin.

What Loupely read

847+ browser signals
72hrs server history
15 correlation rules applied
Download capture file · free  ·  Diagnose · 1 credit
8 credits remaining Buy more

Sound familiar?

Something stopped working. You don’t know when. You don’t know why. You found out because a customer emailed you.

You go back through your mental list. Did you update a plugin? Change a setting? Add something to the header? You updated 3 plugins yesterday. You changed a redirect last week. Any of them could be it.

You start checking. The checkout looks fine on your end. You clear the cache. You deactivate the last plugin you installed. You reactivate it. You clear the cache again. Still broken for some people but not others. You can feel it. You can’t find it.

You’re alone, clicking buttons, backtracking through everything you touched in the last week, wondering which one broke it and whether fixing it will break something else.

Picture this instead.

You see the error. You open Loupely in your browser and click Capture.

The extension reads 847+ browser signals — every console error, every failed network request, every JavaScript exception. The plugin reads the last 72 hours of server events and pulls them together with what the browser saw.

Then Loupely runs 15 correlation rules across the combined picture. It finds the WooCommerce hook failure. It traces it to your caching plugin. It checks the timestamp against your plugin update log and confirms the plugin updated 2 days ago, right before the first checkout error appeared.

What you see: Your caching plugin updated two days ago and broke the WooCommerce checkout hook. Deactivate WP Super Cache, test checkout. If resolved, update or replace the plugin.

That’s it. You didn’t describe the symptoms to anyone. You didn’t wait for a reply. The evidence was already there. Loupely read it.

A Chrome extension and a WordPress plugin that read your site’s browser and server evidence together and tell you what broke, and what to do about it.

Loupely is not Query Monitor. It is not Health Check. Those tools surface data for a developer to interpret. Loupely interprets it so you don’t need one.

How it works

Two things to install. One click when something breaks.

01

Install both. About a minute each.

The Chrome extension from the Web Store. The WordPress plugin from your dashboard. The plugin starts recording server events the moment it’s active — nothing to configure.

// plugin statusPlugin active · 11 capture modules running · Recording started
02

Something breaks. Click the extension. Don’t refresh first.

Refreshing clears the browser’s error record — click first, while the broken state is still visible. The extension reads 847+ browser signals while the plugin sends the last 72 hours of server events simultaneously.

// captured simultaneously847 browser signals · 72hr server history · Credential scan complete
03

Download the file free, or spend one credit for the diagnosis.

The capture file downloads immediately, free. Or spend one credit: 15 correlation rules run, a plain-language verdict appears, and your exact next step is already written.

// triage routesROLLBACK · CONTACT_HOST · CONTACT_PLUGIN_DEV · DIY_FIX · UPLOAD_TO_AI · DEVELOPER_HANDOFF
What’s being built

Five confirmed features. Each one fully specified.

Gated behind real usage milestones — each one unlocks when the data shows it’s ready.

Phase 7 · Black Box

A state snapshot before every plugin change.

When you update or activate a plugin, Loupely takes a snapshot of your site’s health at that moment. If something breaks, you don’t have to guess when it was last fine. You know: healthy at 9:00am, plugin updated at 9:02am, first fatal at 9:03am.

For white-screened sites where the front end is gone but the database is still up, Black Box makes post-mortem diagnosis possible from the event log alone.

Black Box · Site timeline June 4
09:00SNAPSHOT

Site healthy · 14 active plugins · memory 84MB

09:02PLUGIN_UPDATED

woocommerce-payments → 7.6.2

09:03PHP_FATAL

checkout hook · every request · 82s after update

Healthy at 9:00am. Plugin updated at 9:02am. Fatals began 82 seconds later.

Inbox

WooCommerce · Your weekly report

Loupely · Site alert · 09:23

Checkout is failing on useloupely.com

PHP fatal in woocommerce-payments at 09:20. Capture file attached. 20-minute alert window.

Mailchimp · Campaign sent successfully

Monitoring active · heartbeat every 5 min · 20-min alert window
Phase 8 · Always-On Monitoring

Know your site broke before your customers do.

A heartbeat check every 5 minutes. A 20-minute alert window. When something breaks, you get an email before the first customer emails you. The alert includes what Loupely found so you’re not starting from scratch.

Included with the annual plan. No additional cost.

Phase 9 · Troubleshooting Mode

Test with a plugin isolated. Visitors see nothing different.

Troubleshooting Mode isolates one suspected plugin for your admin session only. You see the site with that plugin out of the picture. Every visitor sees the normal site with all plugins running. No downtime. No deactivating things for customers mid-purchase.

Confirm a conflict without touching the live site.

Troubleshooting Mode · Active

Plugin under test

WooCommerce Payments ISOLATED

You (admin)

WC Payments (off)
All others active

Checkout works

Visitors

All plugins active
Normal site

Unaffected

Confirmed: WooCommerce Payments is the cause. Roll back or contact the developer.

4 findings · ranked by severity
PHP_FATALcheckout hook

Crashing on every checkout attempt

Diagnose
MAIL_FAILcontact form

Failing silently for 18 days

Diagnose
SLOW_CRONbackup job

4× longer than last week

Diagnose

Capture is free. The ranked view is free. 1 credit per diagnosis.

Phase 10 · Ranked Findings

See every problem before you decide which one to diagnose first.

Every signal Loupely captured, ranked by severity, visible before you spend a credit. A PHP fatal and an SMTP failure and a slow cron job — all three visible at once. Choose the one that’s hurting you most right now.

The capture is free. The ranked view is free. One credit for whichever you diagnose.

Phase 11 · Predictive Detection

Warnings before the site breaks, not after.

Memory climbing steadily toward the limit. Disk space running low. A cron job taking longer every run. An SSL certificate expiring in two weeks. These are all patterns that end in site failures. Predictive Detection flags them while you still have time to act.

Reactive becomes proactive.

Predictive · 3 early warnings

Memory trending up

+31% this week

At this rate, fatal crashes will begin within 4-7 days.

Disk space low

62MB remaining

Below 50MB, uploads and caching fail silently without error messages.

SSL cert · 14 days

expires 2026-06-20

Renewal pending with host.

What Loupely captures

Everything the browser knows. Everything the server recorded.

Most WordPress failures leave evidence in two places at once. Loupely reads both simultaneously, runs 15 correlation rules, and produces a structured file that tells the complete story.

847+browser signals per capture
72hrsof server history captured
15correlation rules applied
php_error

PHP errors and fatal crashes

Every PHP error, named to the plugin or theme that caused it, with the exact line and timestamp.

network_failures

Network failures and blocked requests

Every failed request: status codes, CORS blocks, timeouts. Loupely shows which request failed and what the server said back.

mail_result

Email failures going back 30 days

Every wp_mail() failure recorded. Your contact form stopped sending 6 weeks ago. Every failed attempt is in the file.

woo_event

WooCommerce pipeline events

Order status changes, checkout hook failures, payment gateway responses. Named to the plugin involved.

plugin_update

Plugin updates correlated to errors

Updated 3 plugins and something broke? Loupely correlates the timestamps and names the one that caused it.

cron_result

Cron failures and scheduled events

Scheduled posts stopped publishing. Memberships not renewing. Loupely finds whether it’s a cron or a hook failure.

Pricing

Free to install. Free to capture. One credit for the diagnosis.

Credits never expire and work across both Loupely and Loupely Lens from one pool.

Always free
$0

The capture file is always free. Complete structured evidence from the browser and server. Send it to a developer, your host, or an AI tool.

Join the waitlist
Most people start here Pay as you go
$1.90 per diagnosis

Credits never expire. A single avoided developer hour pays for more than 25 diagnoses.

$19
10 credits · $1.90 each
$29
20 credits · $1.45 each
See all plans →

Loupely Annual: $99/year for unlimited diagnoses. Includes Always-On Monitoring from Phase 8. Compare all plans →

The evidence was there the whole time

Install free and run your first capture.

Free to install. Free to capture. One credit when you want the diagnosis.