All posts
Landing pages & CRO

Heatmaps and Session Recordings: How to Read Them and What to Fix

Heatmap analysis made practical: how to read click, scroll and move maps and session recordings, what each pattern usually means, and a weekly fix list routine.

By Mehdi Hassan12 min read

The short answer

Heatmap analysis means reading where visitors click, scroll and pause on a page, then watching session recordings to learn why. To improve a landing page with it, review one page a week, match each pattern to a likely cause (unclear copy, misleading design or a bug), and turn the top three findings into a fix list you ship that week.

Key takeaways

  • Heatmaps show where behavior happens. Recordings show why. Use both, never heatmaps alone.
  • Every pattern has more than one cause. Low scroll can mean visitors left happy or confused.
  • Segment by device and traffic source before you read anything. Mixed data hides real problems.
  • A weekly 60-minute review that ends in three shipped fixes beats a quarterly deep dive.
  • Sort each finding into copy, design or bug. The category tells you who fixes it.

What is heatmap analysis?

Heatmap analysis is the practice of reading aggregated visitor behavior on a page, such as clicks, scrolling and cursor movement, shown as color over a screenshot. Warm colors mark where many visitors acted; cool colors mark where few did. Paired with session recordings, which replay individual visits, it shows what people actually do on your landing page instead of what you assume they do.

The value isn't the pretty map. It's the questions the map raises and the fixes they lead to. Analytics tells you that most visitors leave without converting; heatmaps and recordings show you where they hesitated, what they tried to click and what they never saw. That's why we use them in every landing page review before we touch the design or the words.

This guide is the hub for our behavior analytics articles. It covers the three map types, how to read each pattern, how to watch recordings efficiently, and the weekly routine we use to turn all of it into a fix list. Deeper articles on each signal are linked as we go.

What are the main types of website heatmap?

The main types of website heatmap are click maps, scroll maps and move (or attention) maps. Each answers a different question, and none of them answers why, which is the job of recordings and surveys.

Map type

What it shows

Question it answers

Main blind spot

Click map

Where visitors click or tap

What do people try to interact with?

Doesn't show what they expected to happen

Scroll map

How far down the page visitors get

Which sections does anyone see?

Can't tell a satisfied exit from a confused one

Move or attention map

Where the cursor moves or lingers

What draws attention on desktop?

Cursor position is only a rough guide to eye position, and absent on mobile

Session recording

One visitor's full visit, replayed

Why did this person hesitate or leave?

One visit isn't a pattern; you need many

Friction signals

Rage clicks, dead clicks, quick backs

Where is the page frustrating people?

Needs a recording to confirm the cause

Most tools today bundle all of these. The choice between them is mostly about price, privacy settings and whether you also need surveys; we compare the two most common options in Microsoft Clarity vs Hotjar. If you're still deciding whether a marketing site needs these tools at all, read session recording and heatmaps on marketing sites first.

How do you read a click map?

You read a click map by comparing where visitors click with where you want them to click. Clicks on your primary call to action are good. Clicks on things that aren't links, and missing clicks on things that are, are the findings worth acting on.

Start with the primary call to action and count how its clicks compare to everything else above the fold. Then look for three patterns. First, clicks on non-clickable elements such as feature icons, screenshots or bold text, which mean visitors expected more information there. Second, heavy clicks on navigation links that lead away from the page, which on a paid landing page often mean visitors are looking for something the page doesn't answer, frequently pricing. Third, buttons nobody clicks, which can mean the label is unclear or the button doesn't look like a button.

Click pattern

What it usually means

Likely fix type

Clicks on an image or icon that isn't a link

Visitors want more detail about that thing

Design: make it expand, or copy: add the detail

Clicks on the pricing nav item from a demo page

Cost is the blocking question

Copy: answer pricing on the page

Repeated clicks on the same spot

Something looks clickable but isn't, or it's broken

Bug or design

Few clicks on the primary button

Label is vague or the offer isn't wanted yet

Copy first, then design

Clicks spread evenly across many links

Page has no clear next step

Design: reduce choices

Repeated rapid clicks have their own name, rage clicks, and they're one of the fastest ways to find broken or misleading elements. Our guide to rage clicks, dead clicks and form abandonment explains how to triage them.

How do you read a scroll map?

You read a scroll map by finding where the color drops sharply, then asking what sits just above that line. A sharp drop marks a point where many visitors stopped, and the content right before it is the first suspect.

A gradual fade down a long page is normal; people leave as they get what they need. A cliff is different. Common causes are a section that looks like the end of the page (a full-width footer-style band halfway down), a block of dense text, or an early call to action that satisfied the visitor. That last case is the trap: low scroll can mean success. If visitors who stop early are also the ones who convert, the page is doing its job.

So never read a scroll map without the conversion data next to it. We explain how to tell good low scroll from bad in what scroll depth tells you about your landing page, including how to set up scroll tracking in GA4.

How do you watch session recordings without wasting hours?

Watch session recordings with a question and a filter, never at random. Pick one page, one segment and one behavior, such as mobile visitors from paid search who reached the pricing section but didn't convert, then watch 10 to 20 of those visits.

  1. Start from a number

    Use analytics or the heatmap to find the drop-off you want to understand. The recording session should explain a pattern, not discover one.

  2. Filter hard

    Filter by page, device, traffic source and a behavior: rage clicks, a form started but not submitted, or exit after a specific section.

  3. Watch at speed

    Most tools skip inactivity and let you play at double speed or faster. Slow down only at hesitation points.

  4. Note what you see, not what you think

    Write 'scrolled up to the pricing table twice, then left' rather than 'confused by pricing'. The interpretation comes later.

  5. Stop when patterns repeat

    When the same behavior shows up in several recordings, you've found something. Write it down and move on.

Recordings are especially good at showing comprehension problems: visitors scrolling back up to reread the hero, hovering over a term they don't understand, or opening a feature tab and leaving immediately. Those patterns usually point to the words, not the layout. Our guide on how to explain a complex product on your website covers the fixes for that kind of confusion.

What does each heatmap pattern usually mean?

Each heatmap pattern has a most likely cause and at least one alternative, so treat every reading as a hypothesis to check in recordings. The table below is the reference we use in reviews.

Pattern

Most likely cause

Alternative cause

How to check

Sharp scroll drop after the hero

Hero doesn't make the reader want more

Hero answered everything and they converted

Compare scroll of converters vs non-converters

Heavy cursor movement over a paragraph

Visitors are reading it closely

They're stuck on it

Watch recordings for rereading or exits

Clicks on a logo strip

Visitors want proof from those customers

Accidental taps on mobile

Filter clicks by device

Form field clicked, then abandoned

Field asks for too much, too early

Validation error or broken input

Recordings of form sessions

Quick backs from the page

Page doesn't match the ad or search result

Slow load before content appears

Split by traffic source and check speed

Attention split between two audiences' sections

Page serves two buyers without a clear path

Natural mixed audience

Survey: who are you?

Mixed-audience patterns are common on B2B pages where developers and business buyers land on the same page. If you see that, our guide to selling to technical and non-technical buyers on the same page shows how to structure the page for both.

Why heatmaps can mislead you, and how to guard against it

Heatmaps aggregate visits, and aggregation hides differences. A page with half its traffic on mobile and half on desktop produces a blended map that matches neither group. A page with two traffic sources produces a map that averages a motivated visitor with a curious one.

They also over-represent the top of the page, simply because everyone sees it. Low activity lower down can mean visitors don't care about those sections or that few of them got there.

Three habits guard against this: always segment by device first, compare converters with non-converters when the tool allows it, and never act on a heatmap reading until at least a few recordings show the same behavior.

How do you turn heatmaps and recordings into a weekly fix list?

You turn heatmaps and recordings into a weekly fix list by reviewing one page for an hour, writing down every finding, sorting each one into copy, design or bug, and committing to ship the top three that week. The routine matters more than the tool.

  1. Pick this week's page (5 minutes)

    Choose the page with the most traffic and the biggest gap between visits and conversions. Use your landing page conversion tracking setup to find it.

  2. Read the maps by device (15 minutes)

    Scroll map, then click map, mobile first. Note cliffs, unexpected clicks and ignored buttons.

  3. Watch filtered recordings (25 minutes)

    Ten to twenty visits from the segment that matters most, filtered to the behavior you're investigating.

  4. Sort the findings (10 minutes)

    Tag each one copy, design or bug. Bugs go straight to the developer. Copy and design findings get ranked.

  5. Commit to three fixes (5 minutes)

    Pick the three with the clearest cause and the most traffic affected. Write each as one sentence: what we saw, what we'll change.

  6. Check last week's fixes

    Before the next review, look at whether last week's changes moved the pattern. Keep a short log so findings don't repeat.

Sorting by type is the step most teams skip. A bug fix is usually quick and certain; a copy fix needs a writer and some thinking; a design fix may need several pages updated. Knowing which is which keeps the list moving instead of stalling on the hardest item. When the findings are mostly about words, our SaaS website copywriting guide is the next read.

What a fix list looks like

What we saw

Type

Change

Owner

Mobile visitors tap the product screenshot repeatedly

Design

Make the screenshot open a short demo clip

Designer

Paid visitors click Pricing in the nav and leave

Copy

Add a pricing answer section above the form

Writer

Submit button does nothing on one older browser

Bug

Fix form handler and retest

Developer

These rows are illustrative, not from a client. The shape is what matters: an observation, a category, a specific change and a person.

When should you add surveys to heatmap analysis?

Add surveys when recordings show hesitation you can't explain from behavior alone. A heatmap can show that visitors stop at the pricing section; only asking them can tell you whether the price is too high, unclear or simply not what they expected.

A one-question on-site poll on the page you're reviewing, shown after visitors have spent some time or are about to leave, fills the gap. Ask what stopped them, or what they were looking for, and read the answers in the visitors' own words. We list the questions that work best in on-site surveys and polls that reveal why visitors don't convert. Survey answers are also the best raw material a writer can get; if you're hiring one, our guide to hiring a SaaS website copywriter explains what to hand over.

How do heatmaps fit with conversion metrics?

Heatmaps explain your conversion metrics; they don't replace them. Conversion rate tells you whether a page is getting better, and behavior data tells you why. Without both, you either know something is wrong but not where, or you see behavior but can't tell whether it matters.

Before you start, make sure you measure the right conversion and calculate it the same way every week. Our guide to how to calculate conversion rate covers which rate matters at each funnel stage. Then use the weekly review to explain changes in that number. When the page needs more than a weekly list can deliver, a structured audit is the next step; our breakdown of CRO audit cost explains what a good one includes.

Keep tracking intact through a redesign or migration

If you're rebuilding the page or moving platforms, reinstall your heatmap tool and conversion events on the new site before launch, and keep old URLs working so historical data still lines up. Our guides to building a redirect map for a website redesign and a 301 redirect map template cover the URL side.

Read next based on the signal you're working on. Each of these goes deeper on one part of the routine above.

If you need to

Read

Choose a heatmap and recording tool

Microsoft Clarity vs Hotjar

Understand where people stop reading

Scroll depth explained

Find broken or frustrating elements fast

Rage clicks, dead clicks and form abandonment

Set up conversion events on Framer, Webflow or Next.js

Landing page conversion tracking

Measure the right conversion rate

How to calculate conversion rate

Ask visitors why they didn't convert

On-site surveys and polls

Frequently asked questions

How many sessions do you need before a heatmap is useful?
There's no fixed number, but a heatmap built from a handful of visits mostly shows individual quirks. Wait until the map looks stable, meaning new visits stop changing the overall picture, and segment by device before reading it. For low-traffic pages, recordings are often more useful than heatmaps, because a few watched visits can still reveal a clear problem.
Are heatmaps GDPR compliant?
They can be, but compliance depends on your setup, not the tool alone. Most tools mask form inputs and let you mask other sensitive text, and many require a consent banner in the EU because they set cookies or process personal data. Check your tool's privacy documentation, configure masking, and get advice on consent for your specific situation.
Do heatmaps slow down a website?
Heatmap tools add a script to every page, so they add some weight. Most load asynchronously and have a small effect on a well-built site, but stacking several analytics and testing scripts adds up. Run one behavior tool, not two, and check your Core Web Vitals after installing it to confirm the impact is acceptable.
Can heatmaps tell me why visitors leave?
Not on their own. Heatmaps show where behavior happens, such as where scrolling stops or clicks cluster. Session recordings get closer by showing individual hesitation, and on-site surveys can tell you the reason in the visitor's words. Use all three together: the heatmap to find the spot, recordings to see the behavior, and a short poll to hear the cause.
Should I use heatmaps on mobile and desktop separately?
Yes. Layouts, fold positions and behavior differ a lot between devices, so a combined map blends two different experiences into one that matches neither. Most tools let you filter by device. Review mobile first on most landing pages, because that's where layout problems like buried buttons and long headlines usually hide.

· CEO & Design Director

Copywriter, designer and developer, and founder of Designify Studio. Over five years, 60+ projects across 14+ industries, for startups that have raised $300M+.

Want this done for you? Brand & design sprint, $3,000.

A brand refresh or redesign, plus design explorations for your website and product. $3,000, one-time, fixed price. Book a free 30-minute call to see if it fits.

Schedule Call