content · Aug 9, 2026
planning-poker.teamretro.com
30/100 Sparse
Scores higher than 19% of 1,391 multi-step funnels we have measured.
How this was measured
Measured by Roentgen 1.20.1 on 2026-08-09. A capture is read once and its measurements freeze there, so the stamp says which ruleset read this one.
Coverage is detection coverage, not a verdict — it counts the conversion tactics we could prove are present, out of the 5 that apply to a content funnel. Per device: desktop 30 · mobile 30.
Walk 5 links on the entry page, 4 walkable. 3 matched a funnel step; we captured 4 pages in all, this one included.
What we recorded
The funnel, frame by frame
4 steps walkedsee their whole funnel without clicking through it. scored step by step
measuredextracted directly from the live page. a fact, not an opinionIn their own words
23 quotedthe entry page’s own title, headline, buttons and prices — quoted, never paraphrased
measuredextracted directly from the live page. a fact, not an opinion- Page title
Free Planning Poker App & Scrum Poker Online | Planning Poker by TeamRetro
- Meta description
Free Planning Poker app for agile teams — run scrum poker story-point estimation in your browser, in real time, with no account and nothing to install. Vote, reveal, and align with TeamRetro.
- Headline
Free Planning Poker Online for Agile Teams
- Section headings
How to run a planning poker session online
Scrum poker built for agile estimation
Planning Poker FAQ
Keep learning
Create a room
Invite your team
Vote and reveal
Built for remote teams
+2 more, not shown- Buttons and links
expand_more
Learn expand_more
support
question_mark
DISCUSS ESTIMATE REVIEW
DISCUSS
ESTIMATE
REVIEW
Try the demo
Create a room
What we found
1 tacticconversion tactics we could prove are present, with the on-page text that evidences each
measuredextracted directly from the live page. a fact, not an opinionFriction reduction1 of 1
Is Planning Poker free? What is Planning Poker? Do I need an account to use Planning Poker
What we didn’t find
4 of 5 applicableapplicable tactics we checked for and did not see on any step we reached
measuredextracted directly from the live page. a fact, not an opinionWhat we didn’t see4 of 5 applicable
Absence is a measurement, not a recommendation: we do not know why a tactic is missing, whether it belongs here, or whether adding it would change anything. Where a walk stopped early, a tactic living deeper would also read as not detected.
How well it’s built
16 run · 6 flaggedcontrast, mobile, typography, accessibility, weight — each with what would fix it
measuredextracted directly from the live page. a fact, not an opinion6 of 15 measured checks need work1 could not be measured — not counted either way
Text contrast (WCAG AA)
contrast:36% of measurable text passes WCAG AA. 4+ runs fail. 19% of text was unmeasurable (over images/gradients). not counted either way.
worst: “Estimate” at 1:1 (14px, #ffffff on #ffffff). needs 4.5:1
FixRaise text/background contrast to ≥4.5:1 (≥3:1 for large text), especially on CTAs and body copy.
Named controls
a11y:52 buttons/links have no accessible name (icon-only, no aria-label).
FixAdd aria-label to icon-only buttons and links.
Horizontal overflow
layout:The page scrolls ~48px horizontally at 1440px wide. content spills past the viewport.
FixFind the overflowing element (fixed widths, unwrapped rows) and constrain it to 100%.
Oversized images
weight:67 images are shipped at more than 2x the width shown.
“PlanningPoker.svg” is 855px wide, displayed at 192px
FixServe responsive sizes (srcset/sizes) matching the rendered width.
Landmark regions
structure:No <main> or <footer> landmark. screen-reader users cannot jump between regions.
FixWrap the page in <header>, <main> and <footer> (or matching ARIA roles).
Tap-target size (mobile)
mobile:69 of 132 interactive targets are under 44×44px on mobile.
smallest: “support” at 38×38px
FixGive tappable controls a ≥44×44px hit area. the touch minimum.
Worth knowing5
Line length
2 paragraphs run past ~95 characters per line.
FixCap measure at ~60-75ch for comfortable reading.
type:Form labels
3 form fields rely on placeholder text as the only label.
FixBack placeholders with a real <label>. placeholder text vanishes on input.
a11y:Skip link
No same-page “skip to content” link was found. Keyboard users tab through the whole nav on every page.
FixAdd a first-in-DOM <a href="#main"> that is visible on focus.
a11y:Label in name
5 controls have an aria-label that does not contain its visible text, so voice-control users cannot activate it by saying what they see.
FixMake the accessible name start with the visible label text.
a11y:Keyboard reachability
35 elements look clickable but cannot be reached by keyboard.
FixUse <button>/<a>, or add role + tabindex="0" and a key handler.
structure:Not measurable1
Page weight
At least 0.6 MB across 22 measurable resources, but 120 cross-origin resources did not expose a size. The true weight cannot be determined from the page.
weight:Clear4
Mobile viewport · Body text size · Language declared · Image alt text
Brand kit
5 colour roles
palette by on-page usage · type rendered live
measuredextracted directly from the live page. a fact, not an opinionSee the roles applied
Body copy in their text role, on a surface card.
Body copy set at their measured paragraph size. This is how their product reads to a first-time visitor. same family, same scale, same weight.
- List item one, at body scale
- List item two
- List item three
Type scale, weights & families
Measured, found none
3 of 9 layerslayers we ran on this funnel that came back empty
measuredextracted directly from the live page. a fact, not an opinionSections — structural bands identified on this funnel, cropped from its own capture
Elements — the atomic pieces — price anchors, ratings, guarantees — with their verbatim on-page text
Playbook match — which funnel play this page runs — measured, evidence-quoted
We ran these passes on the pages we captured and found nothing to show. That is a measurement of this funnel, not a recommendation — and it is a different statement from a layer we never ran, which does not appear here at all.






