Heatmaps and Click Maps
Heatmaps aggregate where users click, how far they scroll, and where their attention concentrates — making invisible user behaviour visible at a glance.
Where it comes from
Web heatmaps adapted a much older idea from usability science — eye-tracking studies that recorded where people actually looked on a page — and approximated it cheaply using mouse movement, clicks, and scroll depth. The Nielsen Norman Group's eye-tracking work, including the well-known F-shaped reading pattern, is the research backbone the technique borrows from.
Why it matters for your website
The gap between where designers expect users to click and where users actually click is almost always surprising, and heatmaps make it visible without running a single research session. Common findings: users clicking non-interactive elements they perceive as buttons, users ignoring navigation the team considers primary, scroll maps showing that important content sits below the point where most users stop reading, and click maps where a secondary CTA outperforms the primary one. Modern web heatmaps use mouse-movement and click data as a proxy for visual attention — a correlation grounded in the eye-tracking research tradition documented by the Nielsen Norman Group. Each surprising pattern is an immediate, testable optimisation opportunity, and most tools generate click maps and scroll maps automatically from the same session data.
The recurring surprise is the gap between where a team expects clicks and where they land. People click images that look tappable, ignore navigation the designers consider primary, and stop scrolling well above the content the page was built around.
Best of all, the evidence arrives without a research session. A click map is a verdict from real traffic — no recruiting, no scheduling, no lab — and each surprising hotspot is an immediate, testable thing to fix.
Wrong vs right
A page puts its primary CTA above the fold, boldly styled, and the team is sure it performs because it looks prominent. No heatmap exists to confirm it.
A click map shows visitors clicking the product image — which isn't a link — at twice the rate of the CTA. The image looks clickable, so people treat it as such. Linking the image is a thirty-minute change that measurably lifts engagement.
A long landing page assumes visitors reach the testimonials and pricing near the bottom.
A scroll map reveals 80% of visitors stop before the testimonials ever appear. Moving the strongest proof higher puts it where attention actually is.
Understanding Heatmaps and Click Maps
Heatmaps turn thousands of individual sessions into a single picture. A click (or tap) map shows where people press, exposing elements that look interactive but aren't and revealing which calls to action actually earn attention. A scroll map shows how far down the page people get before they leave, which tells you whether anything below a certain point is really being seen.
It's worth remembering the data is a proxy. Mouse position and clicks correlate with attention but don't measure it directly, so heatmaps are best read as strong hints, not precise eye-tracking. They point you at the right questions — why is this non-button getting so many clicks? — which you then confirm with a change and a measurement.
Sample size matters. A reliable map usually needs at least a few hundred sessions on a page; below that, one or two unusual visitors can distort the whole picture. High-traffic pages reach a trustworthy signal in days, low-traffic ones in weeks.
How Kweri checks it
Heatmap capability rides along with the session recording tools Kweri detects — the same tools that record sessions almost always generate click and scroll maps. So Kweri reports whether a tool with heatmap capability is present, and if none is found, the absence of heatmap data is folded into the wider measurement-gap finding. Kweri doesn't generate heatmaps itself; it tells you whether you have the means to.
FAQ
What's the difference between a click heatmap and a scroll map?
A click heatmap shows where people click or tap — useful for spotting misperceived interactive elements and judging CTA engagement. A scroll map shows how far down the page people get before leaving — useful for knowing whether below-the-fold content is actually seen. Most tools produce both automatically.
How many sessions do I need for a reliable heatmap?
Most practitioners want a minimum of 200–500 sessions per page. Below that, individual outliers can skew the aggregate. High-traffic pages reach a reliable sample in days; low-traffic pages may take several weeks.
Are heatmaps the same as eye-tracking?
No. True eye-tracking measures gaze with specialised hardware. Web heatmaps approximate attention using mouse movement, clicks, and scrolling — cheaper and good enough to surface patterns, but a proxy rather than a direct measure.
Related principles
Session recording tools capture how real users behave — where they click, how far they scroll, where they hesitate — the qualitative layer that quantitative analytics alone cannot provide.
The time to hit a target depends on its size and distance — small, far targets are hard to reach.
Readers often scan in an F shape — strong across the top, weaker across a second line, then down the left.
What's visible before scrolling must say who you are, what you do, and what to do next — unaided.
Rage clicks — repeated rapid clicks on an element — are an automated signal of user frustration, typically pointing to a broken interaction, a misperceived affordance, or a failed expectation.
Attribution & sources
Identified by Usability and eye-tracking researchers. Catalogued from Nielsen Norman Group — eye-tracking research.
Heatmap visualisation has been applied to web analytics since the mid-2000s, drawing on the eye-tracking tradition documented by the Nielsen Norman Group. The mouse-as-attention-proxy correlation is studied in academic work including Huang et al. (2012).
See Heatmaps and Click Maps on your own site
Run a free Kweri audit — a plain-English review of your site’s speed, accessibility, SEO and design, ranked by what to fix first. No login, no jargon.
Run a free audit →