> For the complete documentation index, see [llms.txt](https://docs.uxwizz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uxwizz.com/guides/usage-tips.md).

# Usage tips

## Usage tips

### Heatmaps

Compare the same page, screen size, and period before drawing conclusions from a heatmap. A small number of visits may not represent your usual traffic.

#### 1. Unused call-to-action elements

If an important button receives few clicks, check whether visitors can see it, understand its label, and reach it on mobile. Use scroll depth and session recordings to add context.

Before removing a quiet element, check its purpose. A rarely used support, accessibility, or account control can still be necessary. Test a clearer label or placement with an [A/B test](/guides/a-b-testing.md) when appropriate.

### Recordings

#### 1. Gray "play" button and fake visitors

A disabled play button means usable recording data is unavailable. Possible causes include disabled recording, retention cleanup, blocked requests, or a visit that ended before data arrived. It does not prove the visitor was a bot or that an advertising source sent fake traffic.

Check the session's pages and events, then verify the tracker on your own site. See [No data is being recorded](/guides/troubleshooting/tracking/no-data-is-being-recorded.md).

#### 2. Panic clicking

Repeated clicks can indicate that a visitor expected a response. Check whether the control worked, whether the page was slow, and whether the feedback was visible. Watch several sessions before treating this as a common problem.

### Other stats

Use referrers and [goals](/guides/goals.md) together. A traffic source that sends many visits may not send the visitors who complete your intended action. Compare counts and conversion rates over the same period.