Heatmaps surface observed behavior. They tell you visitors clicked the wrong element, scrolled past the CTA without seeing it, or stopped reading at the third paragraph. The diagnosis — what was wrong with the element they ignored, why the CTA failed to attract — is the analyst's job.
Heatmaps require accumulated visitor sessions to be useful, which means they only work on pages with meaningful traffic. Pre-launch pages, low-traffic competitor analysis, and pages you cannot instrument with a tracking script are all blind to heatmap tools.
For diagnosis without traffic, page-level scoring is the alternative. The rubric reads the page itself and grades each element against a corpus of comparable pages. Heatmaps observe; scoring diagnoses.
How Lytms scores it
Lytms does not produce heatmaps — different tool for a different question. Lytms reads the page itself and grades each conversion-relevant element. The two complement: heatmaps show what visitors did; Lytms shows what was on the page they did it on.