On-demand only
Inspector and overlay inject after your action (icon, shortcut, menu). No default content script on every page.
CometLens · browser extension · beta
See issues directly on the page you are analyzing.
Lens overlays Insight audit findings on elements of the page you have open — without switching tools.
Lens shows a saved Insight report or runs a Quick scan. It needs a CometWeb account and API key. The overlay and inspector run on demand in the browser.
CometWeb account · on-demand · clear permissions
localhost · staging · production
LCP slow
Unused JS
Performance · 4
LCP candidate
Unused JS
Render-blocking
Cached result
Privacy and permissions
The extension touches the active tab only when you run it. Concrete rules — not marketing.
No permanent read-all access
It does not require lasting “read all sites” permission. Active-tab access is used during analysis.
API key stays local
Your CometWeb API key stays in the extension service worker — not in the page content script.
Minimized URL, no form contents
Scans send a minimized URL (no query, fragment, or credentials). Form field values are not stored.
Optional metrics
Web Vitals and related browser signals need separate consent. Declining does not block reports or the inspector.
No browsing history
Lens does not read browser history. Remove data by uninstalling the extension and deleting the key in account settings.
Run Lens in a few seconds.
Install the extension
Chrome or Edge (same MV3 package). After install, paste your API key from your CometWeb account.
Open a local, staging, or production page
Works on localhost and on pages behind login in your browser session — you analyze what you see on the tab.
Click Lens
A saved result appears immediately. A new Quick scan goes through Insight (credits) — usually about a minute, not a few seconds.
What the beta checks
Scope matches Insight results (saved audit or Quick scan) plus the local overlay. We do not list controls the extension does not show.
Performance
- Signals and issues from the Performance module in the Insight result
- Full lab Lighthouse stays in the app when Quick scan does not include it
Accessibility
- Selected automated findings (e.g. contrast, names, labels)
- Mapped to WCAG rules in the result — not a conformance certificate
SEO
- On-page signals and issues from the SEO module in the Insight result
Security
- Public signals (headers, HTTPS, CSP) from the Security module
Ecology
- Transfer and CO₂e estimates from the Eco module — same assumptions as Insight
On the page
- Overlay and inspector with DOM selectors
- CSS/HTML fix snippets with reversible preview
- Result history and compare for the same page
A different job for each role.
Designers
Check selected contrast issues on the live page
Toggle the overlay, see elements with detected accessibility issues, and send a screenshot with highlights.
Browser support
Chrome and Edge today. Firefox and Safari — tell us when you need them.
When the store listing is public, the button opens the Chrome Web Store (same package works in Edge). Until then: request the beta-channel package, then configure your API key in the app.
What does beta mean?
- Stable overlay, inspector, result HUD, Quick scan via API, CSS/HTML fix snippets.
- Limits scope = Insight / Quick result — not a pentest or WCAG certification.
- Updates we ship extension updates through the beta channel / store.
- Feedback report bugs or missing checks via contact (source=lens).
- Pricing Lens needs an Insight account; Quick scans use credits like the app.
- Data scan results live in your Insight account; locally we keep settings and optional metrics consent.
See issues without leaving the page.
Insight overlay on the live tab — with an account, on demand, with clear permissions.
CometWeb account + API key On-demand Chrome and Edge Clear permissions