WebLens Page Lens

WebLens Page Lens collects a clear, copyable evidence packet from the active browser tab. Run it manually on a published or locally hosted page to see what the page rendered, what bounded console errors or warnings appeared after collection started, and which browser-visible WordPress or request boundaries may be worth reviewing. Page Lens can report: • Page URL, title, viewport, document size, link count, image count, broken rendered images, canonical URL, and meta description • Bounded console errors and warnings from the current page session • Browser-visible references such as WordPress plugin paths, theme paths, wp-json, WooCommerce, Elementor, cart, checkout, nonce, REST, CORS, and explicit HTTP status references • Suggested discrepancy review boundaries without claiming a verdict or cause • A clean evidence packet that can be copied into an issue, support request, or AI assistant WebLens works on normal published pages without an account, cloud service, or local helper. An optional local WebLens helper can add source context when local project files are available on the same device. The helper is not required for normal Page Lens use and is checked only when the user explicitly requests it. WebLens does not crawl websites, automate browser actions, click page controls, submit forms, upload source code, send page content to external services, or make security, vulnerability, or production-behavior claims. Evidence is collected only when the user opens the extension and runs Page Lens on the active tab.