How to read a heatmap: clicks, scroll and what to fix
A heatmap looks obvious: red is hot, blue is cold. Reading one well is less obvious. Here's how to interpret click and scroll maps, the traps that lead to wrong conclusions, and how to turn what you see into a fix.
Short answer: read a heatmap one question at a time. On a scroll map, ask what share of visitors ever reach your key content and call to action. On a click map, ask whether clicks land on the things you want clicked — or on things that aren't links. Always split by device, and check that the map is built on enough visits.
The types of heatmap
| Type | What it shows | The question it answers |
|---|---|---|
| Click (tap) map | Where visitors click or tap | What attracts attention, and what gets ignored? |
| Scroll map | How far down the page visitors get | Does anyone see the content that matters? |
| Move map | Where the mouse moves (desktop only) | Roughly where eyes might go — a weak signal |
Click and scroll maps carry most of the value. Move maps are only a loose proxy for attention, and they don't exist on touch screens, so this guide focuses on the first two.
Reading a scroll map
A scroll map colours the page from top to bottom by the share of visitors who reached each point: warm at the top where everyone is, cooling as people drop off.
- Find your call to action and read its number. If only 40% of visitors reach the button, 60% never had the chance to act, whatever the button says.
- Look for sharp drops. A gradual fade is normal. A sudden cliff means something stops people: a "false bottom" (a section that looks like the end of the page), a huge image, a block of text nobody wants to read.
- Compare with the fold. What sits above the first screen is seen by almost everyone; make sure the value of the page is stated there, not three screens down.
The cliff is the interesting part of a scroll map, and also the most over-read. Before you act on one, it helps to know what scroll depth really measures — and what it cannot prove on its own.
Reading a click map
A click map shows the density of clicks on each element. Read it against your intentions: what do you want people to click on this page?
- Clicks on things that aren't links — images, icons, bold text, product photos. Visitors expect them to do something. Either make them clickable or make them look less like buttons.
- A cold call to action. If the main button gets fewer clicks than a secondary link, the button may be hard to spot, poorly worded, or placed after the point where people stop scrolling.
- Clicks spread on navigation. Many clicks on the menu of a landing page can mean visitors are looking for information the page doesn't give them — often pricing or details.
- Heavy clicking on one field. Lots of clicks concentrated on a form field or a coupon box can signal frustration. Open a few replays to see what's going on.
5 traps that lead to wrong conclusions
- Too little data. A map built on 30 visits is mostly noise. Wait until the page has a few hundred views per device before deciding anything.
- Mixing devices. Mobile and desktop are different layouts. Averaging them produces a map of a page that doesn't exist.
- Mixing periods. If the page changed during the period, the map blends two versions. Start a new map after each significant change.
- Mistaking attention for success. A very hot element isn't necessarily good. Many clicks on an FAQ item can mean the page doesn't answer an important question up front.
- Stopping at the "what". A heatmap shows a pattern, not a sequence. It won't show you that people clicked the coupon field three times and then left. Session replays will.
From heatmap to fix
Heatmaps are step four of the method we describe in why visitors leave your website: first find the leaking page, then watch the sessions, then check what gets ignored.
- Pick the page with the problem, usually one with a high exit rate on the path to your goal (see bounce rate vs exit rate).
- Read the scroll map, then the click map, for mobile and desktop separately.
- Write down one hypothesis: "only a third of mobile visitors reach the pricing table", "visitors tap the product photo expecting a zoom".
- Check it in 10 to 20 replays of visitors who left.
- Ship one change, mark the date, start a fresh map, and compare the goal over the next weeks. If your traffic is too low to split-test, see what to do instead of A/B testing.
SessionInsight includes click and scroll heatmaps alongside session replays and goals — 10 heatmaps on the free plan, unlimited on Growth — so the map, the sessions and the conversion number sit in one place. See how it works. If you are still deciding what runs underneath it, the realistic options are compared in GA4 alternatives for small sites.
FAQ
How many visits does a heatmap need?
There is no fixed number, but a heatmap built on a few dozen visits is mostly noise. A few hundred views per page and per device type is a common rule of thumb before drawing conclusions, and more for pages with many elements.
What is the difference between a click map and a scroll map?
A click map shows where visitors click or tap on the page. A scroll map shows how far down the page they get, usually as the percentage of visitors who reached each point. Click maps reveal what attracts attention; scroll maps reveal what is never seen.
Should I look at mobile and desktop heatmaps separately?
Yes. The layout, the fold and the way people interact are different on each device. A combined heatmap averages two different pages and can hide problems that only exist on mobile.
Are heatmaps enough to understand why visitors leave?
No. Heatmaps show patterns across many visits, but not the order in which things happened. Pair them with session replays of the visitors who left to see the sequence behind the pattern.
