saas · Sep 26, 2026
We found more conversion tactics here than on 23% of the 1,350 multi-step SaaS funnels we have measured.
4 conversion tactics detected
2 pages walked · measured by Roentgen 1.27.0
Measured by Roentgen 1.27.0 on 2026-09-26. A capture is read once and its measurements freeze there, so the stamp says which ruleset read this one.
This is detection coverage, not a verdict — it counts the conversion tactics we could prove are present, out of the 11 that apply to a saas funnel. A low count means we did not detect those patterns, not that the funnel is weak.
Against all 1,781 multi-step funnels, more conversion tactics than 34% of them.
Walk 11 links on the entry page, 8 walkable. 1 matched a funnel step; we captured 2 pages in all, this one included.
Frequently asked questions
logo wall (8 distinct marks)
$5/mo, $9/mo
+ 1 more with evidence
+ 4 more
+ 1 more
One Link for All App Stores
OneLink generator for iOS and Android apps. One link with device detection, analytics, QR codes, and landing…
this funnel’s coverage score across measured re-scans
measuredextracted directly from the live page. a fact, not an opinionsee their whole funnel without clicking through it. scored step by step
measuredextracted directly from the live page. a fact, not an opinionthe entry page’s own title, headline, buttons and prices — quoted, never paraphrased
measuredextracted directly from the live page. a fact, not an opinionOneLink Generator - One Link for All App Stores | AppPage
OneLink generator for iOS and Android apps. One link with device detection, analytics, QR codes, and landing pages.
One Link for All App Stores
See it work
More than a OneLink generator
Choose Your Plan
Loved by app developers
Frequently asked questions
Create your OneLink today
Smart Platform Detection
Built-in Analytics+6 more, not shown
Log In
Monthly
YearlySave up to 20%
Subscribe Now
What is a OneLink?
What are smart links for mobile apps?
Is AppPage a good Firebase Dynamic Links alternative?
How do smart redirects and device detection work?
What is in-app browser bypass?
Can I track app install link performance?+2 more, not shown
$5
$9
structural bands identified on this funnel, cropped from its own capture
measuredextracted directly from the live page. a fact, not an opinion
conversion tactics we could prove are present, with the on-page text that evidences each
measuredextracted directly from the live page. a fact, not an opinionFrequently asked questions
logo wall (8 distinct marks)
featured on
$5/mo, $9/mo
applicable tactics we checked for and did not see on any step we reached
measuredextracted directly from the live page. a fact, not an opinionAbsence 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.
contrast, mobile, typography, accessibility, weight — each with what would fix it
measuredextracted directly from the live page. a fact, not an opinion4 of 13 measured checks need work1 could not be measured — not counted either way
Smallest sampled text is 10px, below the 13px floor this check uses.
FixKeep body copy ≥15-16px; reserve sub-13px for fine print only.
30 buttons/links have no accessible name (icon-only, no aria-label).
FixAdd aria-label to icon-only buttons and links.
17 images are shipped at more than 2x the width shown.
“icon.0646940a.png” is 512px wide, displayed at 32px
FixServe responsive sizes (srcset/sizes) matching the rendered width.
68 of 156 interactive targets are under 44×44px on mobile.
smallest: “Home” at 38×16px
FixGive tappable controls a ≥44×44px hit area. the touch minimum.
59 paragraphs run past ~95 characters per line.
FixCap measure at ~60-75ch for comfortable reading.
type:1 form field relies on placeholder text as the only label.
FixBack placeholders with a real <label>. placeholder text vanishes on input.
a11y: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:15 elements look clickable but cannot be reached by keyboard.
FixUse <button>/<a>, or add role + tabindex="0" and a key handler.
structure:At least 0.6 MB across 56 measurable resources, but 72 cross-origin resources did not expose a size. The true weight cannot be determined from the page.
weight:Text contrast (WCAG AA) · Mobile viewport · Language declared · Image alt text · Render-blocking resources
palette by on-page usage · type rendered live
measuredextracted directly from the live page. a fact, not an opinionBody 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.
layers 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
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.
