Hotjar

I reach for Hotjar when I need to understand why a page isn't converting despite decent traffic. Heatmaps show me where people click and how far they scroll. Session recordings let me watch individual users — I can see the cursor hesitate, the form field that gets abandoned halfway, the rage-click on a button that should work. Last month I used it on a landing page that had a 68% bounce rate. After watching ten recordings, I spotted an overlay that only appeared on mobile and blocked the CTA. Moving it dropped the bounce rate to 41% within two weeks. That kind of diagnosis is hard with just numbers.

The on-page feedback widget is useful for quick 'why did you leave?' polls. I set one up on a checkout page and learned that 22% of users left because they couldn't find a promo code field — not because the price was too high. The combination of what they did (recordings) and why they did it (polls) is Hotjar's real strength.

I used to ignore the scroll maps because I thought scroll depth was vanity. Then I compared scroll heatmaps with conversion data and saw that the key testimonial section was below the fold on tablet. I moved it up and conversions increased by 12%. Hotjar turns hunches into testable hypotheses.

Hotjar is not a replacement for analytics. If you need raw numbers — pageviews, bounce rate, user counts — stick with Google Analytics. Hotjar focuses on qualitative and visual data. It also has a habit of making pages feel heavier. On a site with a large number of pages being tracked, the JavaScript can add over 300ms to the load time. I tested this with a [website speed test](/website-speed-test/) and found that disabling Hotjar reduced load time by 15%. That matters for SEO and user experience.

The free tier is limited. You get 35 daily sessions and heatmaps on up to 35 pages. For a small blog that's fine, but for an ecommerce site you'll need a paid plan quickly. Also, session recordings can be noisy — you have to filter out bots and exclude long tail URLs to avoid hitting limits. Privacy compliance is a pain. Hotjar offers privacy settings (IP anonymisation, data deletion), but you still need to get consent. On a recent project I spent three hours configuring cookie walls just to avoid recording European users without consent.

I once relied on Hotjar's recordings to diagnose a slow checkout, only to realise that the slow page was caused by a different script — not something Hotjar surfaced. It's a tool for behaviour, not performance. For technical issues like slow rendering or broken JavaScript, you are better off with a crawler such as [Screaming Frog](/screaming-frog/).

If your budget is zero, [Microsoft Clarity](/microsoft-clarity/) is the obvious alternative. It offers free heatmaps and session recordings with no session limits. The trade-off is less mature survey tools and a slightly clunkier interface. I use Clarity on smaller projects and keep Hotjar for client work where I need the feedback widgets.

For a lighter, privacy-first approach, [Fathom Analytics](/fathom-analytics/) provides simple analytics without tracking individuals, but it does not have heatmaps or recordings. If you need that level of privacy, you will need a separate tool like Hotjar or Clarity with consent handling.

Another alternative is FullStory — it offers powerful analytics on recordings with event-based analysis, but it is expensive and overkill for most small sites. I have also tried LuckyOrange, which is simpler than Hotjar but similar in pricing. Ultimately, which tool you pick depends on whether you prioritise free unlimited sessions, deep feedback capabilities, or strict privacy compliance.