Menu

CRO

Heatmaps

A practical CRO method for visualising interaction patterns and spotting what users notice, ignore, or miss.

How to use heatmaps to understand user attention, interaction hotspots, scroll depth, and layout performance.

4 min read

What it is

are a quantitative UX and CRO method used to visualise user on a page or screen.

They aggregate from multiple users and display it as colour overlays, showing where users click, move, and scroll.

Common types include click maps, move maps, and scroll maps.

Unlike , which show individual , show patterns at scale. They highlight what attracts attention and what gets ignored.

The goal is to quickly identify areas of , , and missed opportunities.

Heatmaps are useful when you need a fast visual read on attention and interaction, not a deep explanation of intent.

When to use it

Use this method when you need a fast visual overview of user .

It is most useful when:

You want to understand where users click or tap
You need to see how far users scroll
You are evaluating content visibility and layout
You want to identify ignored or underperforming elements
You are optimising page design or conversion

It is less useful when:

You need detailed behavioural understanding
You want to understand user intent or reasoning
The sample size is too small
The page is highly dynamic or personalised
Heatmaps are often used alongside session replay analysis and analytics to provide both overview and detail.

Key takeaway

Use heatmaps when you need a quick view of attention and interaction patterns before digging deeper.

How to run it

Set up properly

Be clear on the pages you are analysing, which type answers your question, and how the is collected. Click, move and scroll maps answer different things and are routinely confused.

Collect enough before reading anything. A over a few hundred shows randomness with a colour scheme.

Run the method

are aggregate and visual. They are excellent at showing what people interacted with and unreliable at explaining why, which is the opposite of how they are usually presented.

  1. Collect over a period long enough to cover a full weekly cycle.
  2. Review click, move and scroll maps separately. Mouse movement correlates weakly with attention, and treating it as gaze is a common and expensive error.
  3. Compare across pages or rather than reading one map in isolation. are far more useful comparatively than absolutely.
  4. Segment by device and source. A desktop laid over a responsive describes a page most of your users never saw.
  5. Focus on both extremes: heavily used areas, and elements that are being ignored entirely.

Focus on rather than attention. A tells you where the cursor went, and the cursor is not the eye.

Capture and make sense of it

The value comes from seeing distribution. Look across the maps to identify:

  • Areas drawing genuine
  • Elements being ignored, particularly things you consider important
  • on things that are not interactive, which misleading design
  • Differences between segments and devices

Use this alongside other rather than on its own. are best at generating hypotheses and poor at settling them.

What to look for

Focus on:

Click concentration: where users are interacting most
Dead areas: important elements receiving little or no interaction
Interaction spread: which areas draw clicks and which are dead
Visual hierarchy: whether attention aligns with design intent
Unexpected clicks: users interacting with non-clickable elements

Where it goes wrong

Most issues come from:

show what users focus on, not why.

Reading mouse movement as attention, when the cursor is not the eye
Interpreting a map built on a few hundred sessions, which shows randomness in colour
Overlaying desktop data on a layout most people saw on a phone
Assuming an ignored element is unimportant rather than badly placed
Using a heatmap alone to justify a change it cannot actually support

What you get from it

Done properly, this method gives you:

A quick view of which areas draw interaction and which are dead
Elements being ignored despite the prominence you gave them
Clicks on things that are not interactive, which signal a false affordance
Hypotheses worth testing properly, rather than conclusions

Key takeaway

It helps you quickly see what is working and what is not.

Get in touch

If this sounds like something you need, we can help you understand where users focus, interact, and drop off.

No guesswork. No assumptions. Just clear insight you can act on.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What are heatmaps in UX?

Heatmaps are a method used to visualise user interaction data, showing where users click, move, and scroll.

When should you use heatmaps?

Use them when you need a quick visual understanding of user interaction and engagement on a page.

What types of heatmaps are there?

Common types include click maps, move maps, and scroll maps.

What is the difference between heatmaps and session replays?

Heatmaps show aggregated behaviour across many users, while session replays show individual user sessions.

Are heatmaps reliable?

They are useful for identifying patterns, but should be combined with other methods to understand behaviour fully.

Quick take

If you want to see where users focus, click, and scroll at a glance, use heatmaps.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer