Newsletter
$200
content · Sep 7, 2026
We found more conversion tactics here than on 10% of the 1,912 multi-step funnels we have measured.
3 pages walked · measured by Roentgen 1.27.0
Every figure on this page was read off the live site by Roentgen 1.27.0 on 2026-09-07, a script that reads page structure, computed CSS and matched text. No AI judgment, nothing estimated, and a capture’s numbers stay as read.
Detection coverage, not a verdict. A low count means we did not detect those patterns, not that the funnel is weak.
maidensail.com shows 2 of the 7 tactics that apply to a content funnel, and we did not see the other 5.
Proven on the page · 2
★
featured on
Not seen on any step reached · 5
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.
Their headline: “Newsletter”
Their description: “The weekly dispatch — ranks, standout launches, and one honest lesson from every launch week, straight to your inbox every Monday.”
Newsletter — Maidensail
The weekly dispatch — ranks, standout launches, and one honest lesson from every launch week, straight to your inbox every Monday.
Newsletter
What's in every dispatch
Read the latest dispatch
The archive
Search startups… /
Sign in
Submit startup
Claim yours →
Come aboard →
Read
$200
structural bands identified on this funnel, cropped from its own capture
1 could not be measured, not counted either way
69% of measurable text passes WCAG AA. 4+ runs fail.
worst: “Featured on” at 2.71:1 (11px, #98917e on #f3eee1). needs 4.5:1
Raise text/background contrast to ≥4.5:1 (≥3:1 for large text), especially on CTAs and body copy.
What this measuresSmallest sampled text is 11px, below the 13px floor this check uses.
Keep body copy ≥15-16px; reserve sub-13px for fine print only.
What this measures18 images are shipped at more than 2x the width shown.
“featured-badge.png?v=2” is 600px wide, displayed at 143px
Serve responsive sizes (srcset/sizes) matching the rendered width.
What this measures8 paragraphs run past ~95 characters per line.
Cap measure at ~60-75ch for comfortable reading.
What this measures2 headings skip a level (e.g. <h2> followed by <h4>). Screen-reader users navigate by this outline.
Step heading levels one at a time; use CSS for size, not a deeper level.
What this measuresNo same-page “skip to content” link was found. Keyboard users tab through the whole nav on every page.
Add a first-in-DOM <a href="#main"> that is visible on focus.
What this measures4 stylesheets/scripts in <head> block first paint.
Defer non-critical JS (defer/async) and inline only critical CSS.
What this measuresNo <main> landmark. screen-reader users cannot jump between regions.
Wrap the page in <header>, <main> and <footer> (or matching ARIA roles).
What this measuresNo autocomplete attributes across 2 fields. browsers cannot autofill.
Add autocomplete="email"/"tel"/"name" to identity fields.
What this measuresMobile viewport · Language declared · Image alt text · Inline validation
At least 0.4 MB across 100 measurable resources, but 78 cross-origin resources did not expose a size. The true weight cannot be determined from the page.
We measured 4 colour roles on this funnel.
Body copy in their text role, on a surface card.
We also ran these layers on the pages we captured and found nothing to show: Elements, Playbook match (2 of 9 layers). That is a measurement of this funnel, not a recommendation, and a layer we never ran is not listed.
Measured ranges for the parts of a page, from the funnels we have x-rayed.
Navigation barsHero sectionsFootersWhy we walk the whole funnel
The same measurements, in formats a build agent can read.