What browser-only mode is #
Loupely operates in browser-only mode when the Chrome extension is installed but the WordPress Plugin isn’t installed on the site you’re diagnosing, or when the plugin is installed but the extension can’t reach it. In this mode, the extension captures browser-side data only: JavaScript errors, network requests, DOM state, and console output. It doesn’t have access to PHP Errors, Hook Execution, WooCommerce pipeline events, or any other server-side signals.
When browser-only mode applies #
You’ll be in browser-only mode if:
- You haven’t installed the Loupely WordPress Plugin on the site yet.
- You’re diagnosing a site where you can’t install the plugin (a client site where you don’t have admin access, a staging environment with restrictions, or a WordPress multisite installation where the plugin can’t be network-activated).
- The plugin is installed but the connection key hasn’t been entered into the extension yet.
- The plugin is installed and connected but the REST API Endpoint is blocked by a security plugin or server firewall.
The extension popup will indicate when it’s operating without the server layer. If you expect the plugin to be connected but the extension shows browser-only mode, see Extension Won’t Connect to My WordPress Site for troubleshooting steps.
What you can still diagnose in browser-only mode #
Some WordPress failures are primarily browser-side and can produce a useful diagnosis even without the server layer:
- JavaScript conflicts between plugins loading scripts that interfere with each other.
- Script load failures where a plugin or theme is trying to load a file that doesn’t exist or returns a 404.
- Third-party script failures (Payment Gateway widgets, embedded forms, analytics scripts) that are breaking functionality in the browser.
- AJAX requests that are failing at the network level before they reach the server.
- Page builder rendering errors that produce JavaScript errors in the browser.
What you can’t diagnose in browser-only mode #
The majority of serious WordPress failures have a server-side component that browser-only mode can’t capture. These include:
- PHP Fatal Errors and warnings that fire on the server silently.
- WooCommerce Save Pipeline failures where the order appears to process but nothing gets recorded.
- Hook Execution failures where a plugin isn’t firing correctly.
- Database write failures where data appears to save but doesn’t persist.
- Authentication failures rooted in session or nonce handling on the server.
- Email Delivery failures (wp_mail).
For any of these, you’ll get an incomplete picture in browser-only mode at best, and a Null Result at worst. The plugin is the only way to access that layer. See Installing the Loupely WordPress Plugin to add server-side capture to your setup.
Browser-only mode as a starting point #
If you’re troubleshooting a site where you genuinely can’t install the plugin, browser-only mode is still worth running. A browser-side capture can rule out JavaScript causes, document network failures, and give a developer something structured to work from even without the server layer. Download the capture file from the popup and include it with your developer handoff. It’s better than a screenshot or a description, even if it’s not the full picture.