Body text size
type:Smallest body text is 11px (base ~18px). below the ~16px readable floor.
FixKeep body copy ≥15-16px; reserve sub-13px for fine print only.
01
Homepage / Lander
3 tactics
content · Aug 12, 2026
stackscope.dev
0/100 Sparse
Fewer than 1% of 577 entry-page captures we have measured scored lower.
Walk 1 onward step matched, but we could not reach it. Everything below is measured from the entry page alone.
How this was measured
Measured by Roentgen 1.24.0 on 2026-08-12. 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 0 · mobile 0.
What we recorded
The funnel, frame by frame
1 step walkedIn their own words
9 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
StackScope.dev | Technographics for the new web
- Meta description
StackScope analyses the tech stacks of new product launches. See what frameworks, hosting, analytics and tools sites use. Detect AI-built sites. Track technology trends.
- Headline
We analyse new product launches and show you what's under the hood.
- Section headings
From the blog
Most detected technologies of all time
Latest launches
Dig into the data
- Buttons and links
×
Search
Sections
2 identified
structural bands identified on this funnel, cropped from its own capture
measuredextracted directly from the live page. a fact, not an opinion
What we didn’t find
5 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 see5 of 5 applicable
FAQ / objection handling
1,302 of the 1,968 funnels we checked
Press / "as seen in"
508 of the 1,960 funnels we checked
Us-vs-them comparison
332 of the 1,968 funnels we checked
Proof above the fold
314 of the 1,968 funnels we checked
Scarcity / urgency copy
101 of the 1,960 funnels we checked
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
15 run · 4 flaggedcontrast, mobile, typography, accessibility, weight — each with what would fix it
measuredextracted directly from the live page. a fact, not an opinion4 of 15 measured checks need work
Named controls
a11y:7 buttons/links have no accessible name (icon-only, no aria-label).
FixAdd aria-label to icon-only buttons and links.
Oversized images
weight:5 images are shipped at more than 2x the width shown.
“cover-2026-07.png” is 1200px wide, displayed at 320px
FixServe responsive sizes (srcset/sizes) matching the rendered width.
Tap-target size (mobile)
mobile:68 of 82 interactive targets are under 44×44px on mobile.
smallest: “Tech” at 29×20px
FixGive tappable controls a ≥44×44px hit area. the touch minimum.
Worth knowing6
Line length
1 paragraph runs past ~95 characters per line.
FixCap measure at ~60-75ch for comfortable reading.
type:Heading levels
1 heading skips a level (e.g. <h2> followed by <h4>). Screen-reader users navigate by this outline.
FixStep heading levels one at a time; use CSS for size, not a deeper level.
a11y:Label in name
3 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:Render-blocking resources
4 stylesheets/scripts in <head> block first paint.
FixDefer non-critical JS (defer/async) and inline only critical CSS.
weight:Keyboard reachability
2 elements look clickable but cannot be reached by keyboard.
FixUse <button>/<a>, or add role + tabindex="0" and a key handler.
structure:Autocomplete hints
No autocomplete attributes across 1 field. browsers cannot autofill.
FixAdd autocomplete="email"/"tel"/"name" to identity fields.
forms:Clear5
Text contrast (WCAG AA) · Mobile viewport · Language declared · Image alt text · Page weight
Brand kit
5 colour roles
palette by on-page usage · type rendered live
measuredextracted directly from the live page. a fact, not an opinionfull palette ordered by on-page usage %
primary#fef3c7
accent#fef3c7
bg#ffffff
surface#dde4ec
text#475569
See the roles applied
accent
Body copy in their text role, on a surface card.
the roles, doing their job
The quick brown fox32px
Jumps over the lazy dog22px
A subheading in their voice21px
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
SIZE SCALE
10pxAa
11pxAa
12pxAa
13pxAa
14pxAa
15pxAa
16pxAa
18pxAa
20pxAa
21pxAa
22pxAa
32pxAa
WEIGHTS
Aa400
Aa500
Aa600
Aa700
FAMILIES
Noto Sans Display · Figtree
rendered in their own type system · webfont not loaded. system fallback if uninstalled
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 opinionElements — the atomic pieces — price anchors, ratings, guarantees — with their verbatim on-page text
What we found — conversion tactics we could prove are present, with the on-page text that evidences each
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.
X-ray a funnel
