What “not capturing correctly” looks like #
Capturing problems with Loupely Lens fall into 3 patterns: the capture completes but the diagnosis is missing or incomplete; the capture completes but the data appears to be from the wrong element; or the capture never completes at all. Each has a different cause and a different fix.
Incomplete or missing diagnosis after a successful capture #
If the popup shows that a capture completed but the diagnosis text is very short, says “insufficient data to diagnose,” or doesn’t reflect the visual problem you can clearly see, the most likely cause is that Lens captured the element’s CSS state but didn’t find a clear conflict pattern in it. This is a low-confidence result, not a failed capture.
The most common reasons:
- You clicked the wrong element. The visual problem you can see may be caused by a rule on a parent container rather than on the element you clicked. Try clicking the parent container instead, or clicking the specific sub-element that looks most wrong (for example, the text inside a button rather than the button’s wrapper).
- The page is in a partially loaded state. If the page hasn’t fully rendered when you capture, the CSS state may not reflect the final computed styles. Wait for the page to fully load and any animations or transitions to settle before clicking.
- The problem is functional, not visual. If the element looks correct but isn’t working, the cause is JavaScript or server-side logic, not CSS. Lens reads CSS state. For functional problems on WordPress sites, Loupely is the right tool.
Diagnosis doesn’t match the visual problem #
If the diagnosis mentions a problem you can’t see or doesn’t address the problem you can see, Lens may have captured a different element than the one you intended. This happens most often on pages with closely spaced elements where your click lands on an adjacent element, or on pages with transparent or zero-opacity overlay elements sitting on top of the visible content.
To check: after a capture, the popup should briefly highlight the element that was captured. If that highlight appears on a different element than the one you intended to click, deactivate Lens (click the toolbar icon again), reactivate it, and click more precisely on the correct element.
Capture never completes #
If you click an element and the popup shows a loading state that never resolves:
- Check your internet connection. Lens sends the sanitized capture payload to Loupely’s servers for diagnosis. Without a working connection, the diagnosis request can’t complete.
- Reload the page and try again. Some pages enter states where the content script can’t complete the CSS read cleanly. A page reload resets this.
- Try a different element on the same page. If captures work on other elements but not on 1 specific element, the element may have unusual CSS properties that cause the capture to time out. Download the capture file if it’s available and share it with support@loupelylens.com.
- Check if the page has a Content Security Policy (CSP) that restricts extensions. Some high-security sites block content scripts. If Lens works on other sites but fails consistently on 1 site, that site’s CSP may be the cause. The popup will usually indicate this. Lens can’t diagnose elements on pages with CSPs that block the content script entirely.