Your First Diagnosis: Loupely

What you need before you start #

Before running your first diagnosis, you need 3 things in place: the Loupely Chrome extension installed and pinned to your toolbar, the Loupely WordPress Plugin installed and activated on your site, and the extension connected to your site using the connection key from the plugin settings page. If you haven’t done those steps yet, start with Installing the Loupely Chrome Extension and work through the setup sequence from there.

You also need either credits in your account or an active annual plan. The capture itself is free, but the diagnosis and triage step cost 1 credit. New accounts start at zero credits, so you’ll need to purchase a pack or a plan before the diagnosis will run.

How to run your first diagnosis #

1. Go to the broken page on your WordPress site. Navigate in Chrome to the specific page where something isn’t working. The checkout that’s failing, the form that stopped sending, the page throwing an error. Loupely captures data from the active page, so you need to be on it.
2. Reproduce the problem if you can. If the failure happens when you take a specific action (submitting a form, adding to cart, clicking a button), do that action before clicking diagnose. The 60-second capture buffer records browser events as they happen, so triggering the failure gives Loupely more to work with.
3. Click the Loupely icon in your Chrome toolbar to open the popup.
4. Click Run Diagnosis. The extension captures browser-side data (console errors, network requests, DOM state) and pulls server-side data from your WordPress Plugin (PHP Errors, Hook Execution, WooCommerce events) simultaneously. This takes a few seconds.
5. Read the diagnosis in the popup. Before anything downloads, you’ll see 2 sentences in real human terms telling you what broke and where it came from.
6. Read the triage step. Below the diagnosis is a specific next action: a plugin to deactivate, a setting to change, a cache to clear, or a capture file to send to your developer. Follow that step.

What the popup shows you #

The diagnosis popup has 3 parts. The diagnosis itself names the most likely cause of what you’re seeing. The triage step tells you exactly what to do about it. And below those, you’ll see an option to download the structured capture file if you want to dig deeper or hand the problem off to a developer or AI tool.

The capture file contains the full picture: every signal Loupely collected from both the browser and the server, correlated and structured. A developer who receives it has everything they need to write a fix without asking follow-up questions.

What if the diagnosis says no issues were found? #

A Null Result means Loupely captured the page but couldn’t identify a clear failure pattern from the signals it found. This can happen if the failure is intermittent and didn’t occur during the capture window, if the problem lives in a layer Loupely doesn’t cover (like a third-party Payment Gateway’s external servers), or if the error only fires under specific conditions you didn’t reproduce during the capture. See The Null Result: What It Means for next steps.

What happens to your credit #

1 credit is deducted when the diagnosis successfully completes and the result appears in your popup. If the diagnosis fails before completing due to a network error or a server-side issue on Loupely’s end, the credit isn’t charged. If you believe a credit was consumed without a diagnosis being delivered, contact support@useloupely.com.