A Live Attention Heatmap on Any Page You're Browsing

A server-side scan has one hard limit: it can only see what a visitor with no account, no cookies, and no cart can see. Your checkout flow, your SaaS dashboard, your staging environment — invisible. The Heatpoints Chrome extension removes that limit by capturing the page from the one place that always has access: your own browser.

It sees exactly what you see. Logged in, mid-funnel, behind a VPN, on localhost — if it renders in your tab, it can be analyzed.

The pages a server will never see

When you scan a URL on heatpoints.com, a headless browser on our servers visits the page like a stranger. That's exactly right for public pages — landing pages, blogs, product pages, anything a first-time visitor or a search engine would encounter.

But some of the most conversion-critical screens in your product don't exist for strangers. The cart with three items in it. The onboarding step after signup. The billing page of your SaaS. The staging build that isn't public yet. A server scan hits the login wall and analyzes the login wall — which is occasionally useful, and usually not what you asked for.

The extension flips the model. Instead of sending a crawler to the page, it captures the page from your session and sends that capture to the model. Same UniSAL prediction, same heatmap — but pointed at the page state only you can reach.

A live overlay that follows you

The signature feature is the live overlay. Turn it on and the attention heatmap renders directly on the page you're viewing — and keeps updating as the page changes. Scroll, and the prediction follows the new viewport. Resize the window, and it recomputes for the new layout. Open a dropdown or hover a menu, and you see how the attention distribution shifts in response.

This turns the heatmap from a report into an instrument. You can drag a breakpoint and watch a hero lose its focal point at tablet width. You can open a modal and see whether it actually dominates attention or fights with the content behind it. It's the closest thing to strapping an eye tracker onto your own browsing.

One detail worth knowing: live frames don't count against your quota. Access to the live overlay is gated by your plan, but once you have it, scrolling around with the overlay on doesn't burn credits. Explore as long as you want — the meter only runs when you generate a full report.

A full report from the current tab, in one click

When you've found something worth documenting, the extension generates a complete Heatpoints report from the current tab — the same full analysis you'd get from a server scan, with the heatmap, scores, and insights.

The click is the only part that happens in your browser. The analysis job runs server-side: you can close the popup, switch tabs, or move on with your day. When the job finishes, the report is waiting in your Heatpoints account like any other scan — shareable with the teammate who needs to see it.

What you'd actually use it for

• Audit a competitor by browsing them: Walk through a competitor's signup flow or pricing page with the live overlay on. See what their layout makes prominent, where their CTA sits in the attention order, and what they've buried — as you browse, not from screenshots.

• Check a staging page before it ships: Staging environments are password-protected by design, which makes them invisible to server scans. With the extension, the pre-launch attention check happens on the actual build, minutes before you promote it.

• Review a front-end PR: Pull the branch, open the preview, run a report. Attention data attached to the PR review turns "this feels off" into "the new banner steals focus from the primary action."

• Walk your checkout funnel: Cart, shipping, payment, confirmation — the pages where attention problems cost the most money are exactly the ones behind session state. Browse the funnel as a real customer and heatmap every step.

What happens to the captures

An extension that can see behind your logins should be explicit about what it does with that access. So, explicitly: captures are sent to the Heatpoints API for inference and are not retained. The model computes the prediction, returns it, and the capture is discarded. Nothing is tracked in your browser — no browsing history, no analytics on which sites you visit, no background activity. The extension does work when you ask it to, and nothing when you don't.

The rule is simple: the extension sees what you see, when you ask it to look — and forgets it as soon as the prediction comes back.

The pages that matter most to your business are the ones a crawler can't reach. Now the heatmap can.