What this looks like #
You click Run Diagnosis in the Loupely popup, the loading state starts, and it keeps spinning. The popup never updates to show a result. No error message appears. It just sits there.
This is different from a capture that fails before the diagnosis starts (which usually produces an error message) or a diagnosis that returns a Null Result (which produces a “no pattern found” message). A perpetually spinning popup means the diagnosis request started but never received a response.
Step 1: Check your internet connection #
The diagnosis runs on Loupely’s servers. The extension captures data locally and on your WordPress server, then sends the payload to Loupely for analysis. If your internet connection dropped between the capture and the analysis, the request can hang. Check that your browser can load other pages normally, then try again.
Step 2: Check Loupely’s status #
Occasionally Loupely’s analysis servers experience brief outages or elevated latency. If diagnoses are consistently timing out and your connection is fine, check useloupely.com for any status updates or contact support@useloupely.com to ask if there’s a known issue.
Step 3: Check whether your WordPress server is responding slowly #
The capture phase requires the Chrome extension to request server-side data from the Loupely WordPress Plugin via a REST API call. If your WordPress server is under heavy load, experiencing a memory limit issue, or has a long-running process blocking the response, the REST API call may time out. The loading state in the popup covers both the capture phase and the analysis phase, so a slow server-side capture can look identical to a slow analysis.
To test: navigate to https://yoursite.com/wp-json/ in a browser tab. If it loads quickly and returns a JSON response, the REST API is responding normally. If it takes several seconds or fails, the server is the bottleneck.
Step 4: Try reloading the page and running again #
Close the popup, reload the page you’re trying to diagnose, then re-trigger the failure (if applicable) and click Run Diagnosis again. A page reload clears any stale connection state in both the extension and the plugin.
Step 5: Try a different page on the same site #
If the diagnosis hangs consistently on one specific page but works on other pages of the same site, the problem may be specific to that page’s PHP execution or response size. A page that generates a very large PHP error log or triggers an unusually complex hook sequence can produce a capture payload that takes longer than normal to process. If diagnosis works on simpler pages, this is likely the cause. Contact support@useloupely.com with the URL of the problematic page and the support team can investigate.
If none of the above resolves it #
A diagnosis that consistently hangs on a specific site or page regardless of connection and server health may indicate a configuration issue that needs investigation. Email support@useloupely.com with your WordPress version, hosting provider, and the URL where the hang occurs. Include whether the wp-json test URL loaded quickly or slowly. That information typically narrows the cause within a few messages.