affiliate · Aug 9, 2026
45/100 Thin
Scores higher than 43% of 1,391 multi-step funnels we have measured. Among the 80 affiliate funnels in that group, higher than 71%.
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 10 that apply to an affiliate funnel. Per device: desktop 45 · mobile 45.
Walk 15 links on the entry page, 9 walkable. 1 matched a funnel step; we captured 2 pages in all, this one included.
see 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 opinionMkdirs - The Best Directory Boilerplate with AI
The best directory boilerplate, packed with AI, Listings, Payment, Submission, CMS, Blog, Authentication, Newsletter, SEO, Themes and more.
Launch AI-powered directory in 30 minutes
POWERED BY
MONETIZATION
HOW IT WORKS?
1. Configure your directory
2. Deploy your directory
3. Manage the content
What makes Mkdirs different
1 template, 3 codebases+7 more, not shown
Toggle mode
Switch language
Log in
Sign up
Get Mkdirs
See Demo
1. Configure your directory
Clone the repository, customize the website.
2. Deploy your directory
Deploy the project to your preferred platform.+2 more, not shown
$300
$30
$40
$59
$99
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 opinionranked list
logos: MkSaaS customer 1, MkSaaS customer 2, MkSaaS customer 3, MkSaaS customer 4, MkSaaS
disclosure present
What do I get exactly?
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 opinion6 of 16 measured checks need work1 could not be measured — not counted either way
Smallest body text is 12px (base ~18px). below the ~16px readable floor.
FixKeep body copy ≥15-16px; reserve sub-13px for fine print only.
1 button/link has no accessible name (icon-only, no aria-label).
FixAdd aria-label to icon-only buttons and links.
13 stylesheets/scripts in <head> block first paint.
FixDefer non-critical JS (defer/async) and inline only critical CSS.
67 images are shipped at more than 2x the width shown.
“logo-dark.png?dpl=dpl_3GA2TJyeREV9bLimbJ” is 512px wide, displayed at 32px
FixServe responsive sizes (srcset/sizes) matching the rendered width.
No <main> or <header> or <footer> landmark. screen-reader users cannot jump between regions.
FixWrap the page in <header>, <main> and <footer> (or matching ARIA roles).
197 of 292 interactive targets are under 44×44px on mobile.
smallest: “Toggle menu” at 32×32px
FixGive tappable controls a ≥44×44px hit area. the touch minimum.
6 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: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:1 control has 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:No autocomplete attributes across 4 fields. browsers cannot autofill.
FixAdd autocomplete="email"/"tel"/"name" to identity fields.
forms:At least 1.1 MB across 98 measurable resources, but 164 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 · Inline validation
which funnel play this page runs — measured, evidence-quoted
deriveda deterministic summary generated only from measured facts. labeled, never an LLM guessPage matches the Bridge Funnel’s listicle pattern — ranked recommendations with disclosure/outbound offers
home: ranked listAffiliate disclosure
home: disclosure present
A match means this funnel's measurable surfaces fit the playbook's pattern — the quoted language is what fired the detection. A lever is one playbook mechanism observed on-page. We never claim what a brand's ads or emails do; a crawl can't see them. All funnel designs →
Two different things sit side by side here. The claim and its quoted evidence are measured on this funnel, the same way every other fact on this page is. The playbook itself is written guidance — our strategy library, not a measurement of this site — and it lives behind the links above. Nothing on this page recommends what this brand should do.
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
We ran this pass 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.
