Heatmap Score Calculator
The formula
What the heatmap attention score tells you
Compresses click maps into one number: CTA attention against a healthy-placement benchmark, plus the leak share going to other elements.
Calculation: Attention score = (CTA clicks ÷ visitors) ÷ benchmark × 100. Enter your inputs and every substitution is shown below the result.
Reading the result
A score under 70 with a high leak share is a layout diagnosis — the clicks exist on the page, just not where revenue lives.
Rules of thumb: Score 100 = on benchmark; below 60 warrants a layout test before any traffic spend
Limitations and best practice
Beware "orange but useless": scroll maps flatter above-the-fold; judge click maps against actionability — the nav clicks leaking are often the menu doing its job.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Do scroll or click maps predict conversion better?
What about rage clicks?
Source & methodology
UX heat-mapping practice (Hotjar/CrazyEgg conventions).
Heatmap Score explained: formula, worked example and honest limits
You want to know what the number requires, not just what it is; this page shows both. Searchers land on a Heatmap Score page for three reasons — to plan, to compare options, and to check that somebody else’s arithmetic is honest. This tool serves all three, and everything after the calculator explains the model instead of hiding it.
The useful way to hold Heatmap Score is as a ratio with a story attached: Attention score = (CTA clicks ÷ visitors) ÷ benchmark × 100 says how the parts combine, and the 72.6 /100 figure above is simply that sentence written in numbers. Everything that follows unpacks one clause of the sentence at a time.
Most confusion about Heatmap Score comes from mixing up the input you control with the input you merely observe. The formula treats them identically, but your decisions should not: one deserves measurement, the other deserves a defensible estimate.
Every figure in the prose is generated by the engine rather than written beside it — the worked example resolves to heatmap attention score = 72.6 /100 on the default inputs, and the sensitivity section ranks the inputs that move the result — Page visitors first, at ≈11.1 % of the headline for a ten-percent error either way in that input — which is the thread the rest of this guide pulls on.
The Heatmap Score formula, explained
The engine implements a single stated model: Attention score = (CTA clicks ÷ visitors) ÷ benchmark × 100. There is no hidden coefficient and no login-gated precision — the formula printed is the formula executed, which is also what makes the result citable.
Page visitors (example value 17,250) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
Clicks on the primary CTA (example value 401) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
Total recorded clicks (example value 6,550) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
Healthy CTA click share of visitors (%) (example value 3) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. Enter it exactly as your document states it — quoted annual, monthly and effective rates are three different numbers.
Heatmap Score with real numbers, step by step
Abstract formulas are hard to trust, so here is the complete substitution using the default inputs, written the way an examiner would want it. Starting figures: Page visitors, Clicks on the primary CTA, Total recorded clicks, Healthy CTA click share of visitors (%). The computed heatmap attention score comes out at 72.6 /100, which the interpretation band labels “CTA earns 73% of where it should be”.
- On-target rate = 401 ÷ 17250 = 2.32%
- Score = 2.32 ÷ 3.2 × 100 = 73
CTA clicks per 100 visitors — 2.32. This is the number experienced users quote when the headline alone would mislead.
Clicks on non-target elements — 93.9 %. This is the number experienced users quote when the headline alone would mislead.
Visitors needed for +20% score lift — 11,244.8. Compare it against the main result of 72.6 /100 before drawing conclusions.
Overwrite any input above and every line of this example updates with it — the substitution is live, not a screenshot of somebody else’s numbers.
The Heatmap Score corridor: your result across a realistic band
The honest version of any estimate is a corridor, and this one is cheap to produce: Heatmap Score was recomputed at 5 points along the dominant input, with every other field left untouched.
| Page visitors setting | Heatmap attention score |
|---|---|
| 80 % of the example value | 90.8 /100 |
| 90 % of the example value | 80.7 /100 |
| example inputs | 72.6 /100 |
| 110 % of the example value | 66.0 /100 |
| 120 % of the example value | 60.5 /100 |
That spread — 60.5 /100 at the low end, 90.8 /100 at the high — is what a careful read of Heatmap Score looks like: a band you can state out loud, with the reason for each edge. Reproduce it in the form above by editing Page visitors alone; the substitution steps will follow your figures exactly.
Where Heatmap Score is fragile — and where it is not
This list was computed for this specific engine just now: each numeric input was nudged ±10 % while every other field held its example value, and the heatmap attention score was recalculated from scratch. For Heatmap Score the ranking is measured rather than guessed, and it belongs to these defaults: shift the starting point and the order can shift with it.
- Page visitors: ten percent up gives 66.0 /100, ten percent down gives 80.7 /100 — ≈11.1 % of the heatmap attention score either way
- Nudge Healthy CTA click share of visitors by ±10 % and Heatmap Score lands between 66.0 /100 and 80.7 /100 (sensitivity ≈11.1 %)
- Clicks on the primary CTA +10 % → Heatmap Score = 79.9 /100 · −10 % → 65.4 /100 (the heatmap attention score shifts ≈10.0 %)
Page visitors is the dominant lever here: ten percent either way moves the result by about 11.1 %, from 66.0 /100 to 80.7 /100. Measure that input from a document rather than from memory, and Healthy CTA click share of visitors is effectively tied with it (≈11.1 % for the same nudge), so verify the pair together. The rest of the inputs earn only a rounding-error of attention, and that asymmetry is the practical payoff of measuring rather than asserting.
What a Heatmap Score of 72.6 /100 means in practice
A number on its own is trivia; a number against a range is intelligence. The default case lands in the “CTA earns 73% of where it should be” band, and bands are deliberately wide because real situations overlap. Before treating the band as fact, note its width: ten percent either way on Page visitors already spans 66.0 /100 to 80.7 /100. The practical reading rules: compare against your own history before comparing against other people; treat band boundaries as zones, not walls — one point on the wrong side of a threshold rarely changes a real outcome; and when a companion output contradicts the headline, believe the pair.
The comparison worth making is not with somebody else’s Heatmap Score but with the version of your own situation measured last quarter — same formula, same conventions, different inputs.
Why Heatmap Score results go wrong — and how to prevent it
Beware "orange but useless": scroll maps flatter above-the-fold; judge click maps against actionability — the nav clicks leaking are often the menu doing its job. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Comparing a Heatmap Score computed here with a figure from another source that uses different conventions. Same name, different denominator — the disagreement is usually in the definitions, not the data.
One mistake is specific to this engine: assuming every input matters equally. The computation above shows Page visitors dominating — a careful figure there beats false precision everywhere else.
A final trap is presentation: reporting Heatmap Score to more decimal places than the inputs support. The tool prints what the arithmetic gives; you should quote only what your least precise field justifies.
Heatmap Score verification checklist
- State, in one sentence, which convention each rate, unit or period in the form is using.
- Recompute once with the dominant input deliberately set low, and see whether the decision changes.
- Put Page visitors under a magnifier; the sensitivity table above is the reason why.
- Compare the result with one independent method or published benchmark.
- Check that every field the formula needs actually arrived from a document, not from recollection.
- Repeat the ±10 % test on the inputs that matter and see whether the decision — not just the number — still holds.
Five steps from raw inputs to a figure you can defend
Using a calculator well sounds trivial, but the difference between a decision-grade figure and a throwaway one lives entirely in the routine. The routine for Heatmap Score takes a minute to learn and applies to every input above.
Step 1 — collect, then type. Everything this tool asks for is listed above (page visitors, clicks on the primary cta, total recorded clicks, healthy cta click share of visitors (%)). Pull each figure from something you can point at — paperwork, a dashboard, a label — before touching a field. Guesswork at the input stage cannot be repaired at the interpretation stage. Re-running a number costs seconds; retracting a decision costs considerably more.
Step 2 — compute the version you would not be embarrassed by. If a stranger audited your inputs, which set would you hand over? Enter that set, read the result, and treat everything else as upside. If the answer changes your behaviour, it deserves a second run with different assumptions.
Step 3 — isolate your variables. Change one field, observe, revert. The live sensitivity list does the ranking for the default inputs; verify it against your own, because dominance shifts when the starting point shifts. The input you reach for first is usually the one you measured longest ago.
Step 4 — stress before you commit. A decision that survives a ten-percent squeeze on its two biggest inputs needs no luck to be sound. One that does not survive is a decision about hope, not about arithmetic. The test of a good estimate is not that it feels right but that it changes what you do.
Step 5 — write the one-line memo. “Heatmap attention score = 72.6 /100 on this date, from these inputs.” That line is the entire deliverable; everything else on this page is how you earned the right to write it. Most surprises in numbers are surprises about inputs, not about formulas.
From calculation to decision: where Heatmap Score earns its keep
Numbers earn their keep in conversations, and Heatmap Score is no exception. In Business & Entrepreneurship discussions around Marketing & Growth, this figure decides whether an option stays on the table: it converts an opinionated debate into an arithmetic one, and arithmetic is the only referee both sides accept. Rounding early is the quietest way to introduce a permanent error.
Professionals in Marketing & Growth use this style of calculation as a screening filter before spending real money or effort: a quick Heatmap Score check eliminates weak options in minutes, and the survivors earn the deeper, slower analysis. Precision is a promise you make about your data; make sure your inputs can keep it.
There is a personal-administration use people overlook: periodic self-checking. Heatmap Score quietly drifts as life changes — rates move, bodies change, costs compound — and re-running it a few times a year catches drift while correction is still cheap. One decimal place more than your data supports is one decimal place of fiction.
People also ask about Heatmap Score
What affects Heatmap Score the most?
Measured on this engine, Page visitors is the dominant lever: moving it ±10 % shifts the heatmap attention score across 66.0 /100 to 80.7 /100 — about 11.1 % of the headline, with Healthy CTA click share of visitors next at ≈11.1 %. The ranked list in the sensitivity section is computed live, not asserted from a template.
Do healthy cta click share of visitors and page visitors matter equally?
On these inputs, yes: the two measured within a rounding error of each other — ≈11.1 % and ≈11.1 % of the heatmap attention score per ten-percent change. Treat them as one pair to verify together rather than ranking them.
What is a typical Heatmap Score?
With the example inputs on this page the result is 72.6 /100, labelled “CTA earns 73% of where it should be”. “Typical” varies with situation, which is why every result here ships with its verdict band and its sensitivity list: they turn one figure into a range you can locate yourself inside.
How do I calculate Heatmap Score by hand?
Attention score = (CTA clicks ÷ visitors) ÷ benchmark × 100 is the entire method. Work the inputs in that order — On-target rate = 401 ÷ 17250 = 2.32% — and you will reach 72.6 /100 on the default figures, the same number this tool prints.
What happens to Heatmap Score if page visitors changes by 10 %?
On these inputs a ±10 % change in page visitors takes Heatmap Score to 66.0 /100 against the 72.6 /100 example — around 11.1 % of the headline. The same test on every other field is in the sensitivity section.
Is the Heatmap Score result of 72.6 /100 good or bad?
Neither, on its own — the label “CTA earns 73% of where it should be” is the band this figure falls in for the example inputs, and your own inputs will place you elsewhere on the same ladder. Judge the number against your history and your alternatives, and remember that a ten-percent error in Page visitors alone moves it by ≈11.1 %.
Should I use Heatmap Score before launching?
Yes — a Heatmap Score run on honest inputs before spending is the cheapest consulting an entrepreneur can buy. Re-run at every pricing change; the number moves more often than founders expect.
Is Heatmap Score accurate?
The arithmetic is exact: Attention score = (CTA clicks ÷ visitors) ÷ benchmark × 100 is evaluated with full floating-point precision and every substitution is printed in the worked example. What limits accuracy is input quality and the model’s assumptions, so treat the 72.6 /100 result as the correct answer to the question you typed — and check the assumptions section before acting on it.
Do scroll or click maps predict conversion better?
Click maps on conversion pages — they measure intent directly; scroll maps measure attention, which only pays through layout decisions.
What about rage clicks?
Rage patterns (rapid repeats on one non-interactive spot) are usability defects — triage them before optimising placement.
Is my data private on this page?
Yes — computation happens locally in your browser, with no account, no tracking of your inputs and nothing sent to a server. The printed formula is the whole story of what happens to your figures.
Glossary for Heatmap Score
- CTA clicks per 100 visitors
- 2.32 for the Heatmap Score worked case; it sits next to the main result because it carries context the headline leaves out.
- Clicks on non-target elements
- 93.9 % for the Heatmap Score worked case; it sits next to the main result because it carries context the headline leaves out.
- Visitors needed for +20% score lift
- 11,244.8 in the default Heatmap Score calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Heatmap attention score
- The primary output of this tool: 72.6 /100 for the default inputs, computed exactly from Attention score = (CTA clicks ÷ visitors) ÷ benchmark × 100.
- Worked example
- Every substitution in order, from the example inputs to 72.6 /100 — the audit trail for the headline figure.
- Verdict band
- A named zone on the range of plausible results; the example inputs land in “CTA earns 73% of where it should be”, and your inputs may not.
- Sensitivity (±10 %)
- How far the Heatmap Score moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Methodology, sources and limits
The model is published arithmetic implemented exactly as written: Attention score = (CTA clicks ÷ visitors) ÷ benchmark × 100. Source of record: UX heat-mapping practice (Hotjar/CrazyEgg conventions). Where a professional version of this calculation differs, it differs in inputs and jurisdiction-specific coefficients, not in the algebra — which is why re-checking your inputs beats hunting for a second calculator.
This page is an estimation aid, not professional advice. The design rule is simple: two people entering identical figures must get identical answers. What that buys you is reproducibility — two people, two browsers, the same arithmetic, and a printed trail from inputs to result that either of them can audit.
Next steps after the calculation
Refresh the calculation every term or test cycle — weightings and raw scores both move.
Whoever you are (students and candidates planning toward a target score), the next step is the same: replace the example inputs with your own, note the date, and re-run whenever a figure moves. In Business & Entrepreneurship, a dated figure is a trend, and an undated one is a rumour.