Hotjar alternatives won't fix what heatmaps can't see
Switching heatmap tools rarely helps. What Hotjar and every alternative structurally cannot measure, what they are good at, and what to check instead.
A heatmap records what happened on your page. It cannot tell you why your conversion rate is dropping, and outside of an actual click it is not reliably recording where anyone was looking.
You installed Hotjar because something was wrong. Three weeks later you have four hundred recordings, six heatmaps, and a warm orange cloud sitting over your hero image. You still do not know what to change. So now you are searching for a Hotjar alternative, on the theory that a better tool would have told you.
It probably would not have.
What do heatmaps actually measure?
Three separate things, with three different levels of accuracy. Hotjar's own documentation lists the types as clicks and taps, scrolls, and movement. Click maps record real events and are exact. Scroll maps record how far the viewport travelled and are close to exact. Movement maps record your mouse, which is a far weaker stand-in for attention.
The movement map is the one people read as interest. That warm cloud over your headline is not a picture of where eyes went. It is a picture of where the cursor sat parked while the eyes were somewhere else.
What the data says about cursors and attention
A Microsoft Research and University of Washington study tracked 36 people through 32 search tasks on a real eye tracker, capturing 1.3 million gaze positions. The cursor sat completely still for 58.8 percent of the total time, and when it did move it trailed the eye by roughly 700 milliseconds.
"But claiming that the cursor approximates the gaze is misguided." Huang, White and Buscher, CHI 2012.
58.8% of the study time the cursor was not moving at all.
700 ms average lag between the eye arriving and the cursor following.
233 px median gap between gaze and cursor while the cursor sat idle.
39 users Nielsen Norman Group's threshold for a heatmap that stays stable.
The gap is not constant. It closes almost completely at the moment of a click, and opens up everywhere else.
Cursor idle ████████████ 233 px
Examining █████████ 167 px
Reading ████████ 150 px
About to click ████ 77 px
At the click ████ 74 px
Median distance between eye and cursor, by what the cursor was doing. On a phone, 233 pixels is most of the screen. The same paper notes the alignment is worse on ordinary web pages than on the search results pages it measured.
Is this happening on your site?
Open your busiest heatmap and try to finish one sentence: we should change this, because that. If you cannot reach the end without guessing, the tool produced data and no decision. That is the normal outcome, not evidence you are reading the map wrong.
Two more checks take a minute each. Does the page use an iframe, a canvas element, or images drawn by JavaScript? Hotjar's limitations page says iframes render as a black box with no click data, canvas content cannot be tracked at all, and screenshots do not execute JavaScript. Those parts of your page are invisible to the map, and nothing on the map warns you they are missing.
Get a ranked list instead of a red blob. Free audit, no card.
Where the money actually goes
A heatmap prices nothing. It shows a warm patch and leaves the arithmetic to you, which is how a year of recordings ends up sitting next to a flat conversion rate. Revslip publishes its formula instead: traffic, multiplied by the conversion gap, by average order value, weighted by mobile share.
The formula, worked through
Say a checkout gets 12,000 sessions a month, converts at 1.4 percent against the 2.6 percent its traffic mix should support, carries an average order of 68 euros, and runs 71 percent mobile. That is 12,000 × 0.012 × 68 × 0.71, or about 6,952 euros a month sitting in one leak.
The heatmap of that same checkout shows a warm patch near the shipping field and no number anywhere on it.
You do not need our tool to run that. You need the number to exist. A heatmap will never produce one, which is the difference between data and a decision, and part of why most sites carry around forty conversion problems rather than one.
Want that figure for your own checkout? Run a free audit.
Which Hotjar alternative should you actually pick?
If the goal is to stop paying, Microsoft Clarity is free with no traffic or session caps and covers clicks, scrolls, recordings and rage clicks. If you want replay inside your product analytics, PostHog is open source. Hotjar itself now sits inside Contentsquare. All of them record the same events.
And if you are weighing a behaviour tool against an audit rather than against another behaviour tool, Revslip alternatives names which one wins in which situation.
Switching is a cost decision. It is not a diagnostic one. Every tool on that list will hand you the same warm clouds at a different price, because they are all measuring the same three things.
Are session recordings worth watching?
Yes, for one job. A recording is the fastest way to catch a control that is broken rather than a message that is weak. It is a poor way to answer why nobody buys, because you are watching one person and guessing at their reasons. If the next move was going to be pasting the URL into a chatbot instead, that has its own failure mode.
What to change, in order
Keep the parts of the tool that record real events, stop treating the rest as attention, and put a euro figure on the shortlist before anyone touches the code. Four steps, and the first three take an afternoon rather than a sprint.
- Keep the click map and the scroll map. Both record things that genuinely happened. Trust them.
- Stop reading the movement map as attention. Use it to spot dead zones no cursor ever reaches, and nothing finer than that.
- Watch recordings with one question written down first. Without a question you will find whatever you already believed.
- Price the shortlist before you build. Run the formula above on your two biggest suspects. The cheaper fix usually is not the smaller one, which is also the argument against reaching for a redesign.
When this does not apply
If your problem is a broken control rather than a weak argument, a recording beats a crawl every time. A form that silently fails validation in Safari shows up in ninety seconds of replay and in no automated scan, including ours. That is a real gap in what Revslip covers.
Worth saying plainly: the 134 businesses Revslip has audited are not a random slice of the web. They arrived because somebody already suspected the site was leaking, so the sample skews toward broken pages. Read anything we say about how often a problem shows up as coming from a waiting room, not a census. We also sell audits, so weigh the argument above on its sources rather than on our say-so.
So was the tool a waste of money?
No. Click and scroll data is real, and rage clicks find broken buttons faster than anything else on the market. The mistake was expecting a recording of behaviour to explain the behaviour. For that you want a diagnostic that starts from the likeliest causes, or an honest look at what an audit costs before you hire anyone.
Would a free audit tool tell me more?
It answers a different question. Heatmaps show behaviour without reasons, free scanners show rule breaks without money attached. We broke down what free website audit tools actually check and where both instruments stop.