saas · Aug 26, 2026

supportpages.io

70/100 Partial

Scores higher than 82% of 1,391 multi-step funnels we have measured. Among the 1,074 saas funnels in that group, higher than 78%.

How this was measured

Measured by Roentgen 1.26.1 on 2026-08-26. 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 11 that apply to a saas funnel. Per device: desktop 70 · mobile 70.

Walk 25 links on the entry page, 16 walkable. 2 matched a funnel step; we captured 3 pages in all, this one included.

Captured Homepage / Lander
Step 1 · Homepage / Lander1 / 3

What we recorded

The funnel, frame by frame

3 steps walked

see their whole funnel without clicking through it. scored step by step

measuredextracted directly from the live page. a fact, not an opinion
Homepage / Lander
01

Homepage / Lander

▲ strongest
5 tactics
Sticky CTAFree trialNo cardLogo wallDemo / docs
Pricing
02

Pricing

5 tactics

$0 +2 more  ·  save 23%  ·  1 proof point

Sticky CTAFAQFree trialPricing tiersDemo / docs
Demo
03

Demo

▼ thinnest
3 tactics
Sticky CTAFree trialDemo / docs

In their own words

28 quoted

the 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
SupportPages.io – Help docs that write themselves from your code
Meta description
SupportPages reads your code and keeps your help centre up to date - every merge, no backlog.
Headline
Your customer-facing docs are out of date the moment you ship.
Section headings
See SupportPages in actionThree steps to a help centre that never goes staleA help centre from day oneHelp articles that update themselvesHuman review before anything goes liveA help centre that stays currentEvery step gets a screenshotWatch it, don't just read it+8 more, not shown
Buttons and links
ProductResourcesSign inGet started freeWhat do you do with our source code?What if our team is sceptical about AI-generated content?How long does it take to get set up?Which code hosts do you support?Book a demo

Sections

3 identified

structural bands identified on this funnel, cropped from its own capture

measuredextracted directly from the live page. a fact, not an opinion
Nav section of supportpages.io
Nav0% down the page
Logos section of supportpages.io
Logos15% down the page
Footer section of supportpages.io
Footer99% down the page

Elements

1 harvested

the atomic pieces — price anchors, ratings, guarantees — with their verbatim on-page text

measuredextracted directly from the live page. a fact, not an opinion
No credit card element
No credit card“No credit card required”

What we found

6 tactics

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 opinion

Offer clarity1 of 1

Makes the pricing ladder explicit free, $0/mo, $99/mo, $129/mo

Action path3 of 4

Offers a free trial or free tier Get started free
Lead-capture form website_url, demo_request[name], demo_request[email], demo_request[company]
Offers a demo or docs entry point Book a demo

Trust & proof1 of 2

Shows customer logos or a trusted-by claim logos: supportpages.io, WordPress, DocuSeal, Cal.com, Plausible

Friction reduction2 of 2

Answers buyer objections Frequently Asked Questions
Offers a free trial or free tier also shown under Action path

What we didn’t find

5 of 11 applicable

applicable tactics we checked for and did not see on any step we reached

measuredextracted directly from the live page. a fact, not an opinion

What we didn’t see5 of 11 applicable

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
Usage / adoption proof 237 of the 1,539 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

16 run · 3 flagged

contrast, mobile, typography, accessibility, weight — each with what would fix it

measuredextracted directly from the live page. a fact, not an opinion

3 of 15 measured checks need work1 could not be measured — not counted either way

Body text size

type:body-text-size

Smallest body text is 10px (base ~20px). below the ~16px readable floor.

FixKeep body copy ≥15-16px; reserve sub-13px for fine print only.

Oversized images

weight:oversized-images

11 images are shipped at more than 2x the width shown.

“wordpress.png” is 1412px wide, displayed at 154px

FixServe responsive sizes (srcset/sizes) matching the rendered width.

Tap-target size (mobile)

mobile:tap-target-size-mobile

53 of 79 interactive targets are under 44×44px on mobile.

smallest: “Sign in” at 38×15px

FixGive tappable controls a ≥44×44px hit area. the touch minimum.

Worth knowing7

Line length

14 paragraphs run past ~95 characters per line.

FixCap measure at ~60-75ch for comfortable reading.

type:line-length
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:heading-levels
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:label-in-name
Render-blocking resources

7 stylesheets/scripts in <head> block first paint.

FixDefer non-critical JS (defer/async) and inline only critical CSS.

weight:render-blocking-resources
Landmark regions

No <main> landmark. screen-reader users cannot jump between regions.

FixWrap the page in <header>, <main> and <footer> (or matching ARIA roles).

structure:landmark-regions
Keyboard reachability

1 element looks clickable but cannot be reached by keyboard.

FixUse <button>/<a>, or add role + tabindex="0" and a key handler.

structure:keyboard-reachability

Not measurable1

Page weight

At least 2.9 MB across 134 measurable resources, but 189 cross-origin resources did not expose a size. The true weight cannot be determined from the page.

weight:page-weight

Clear5

Text contrast (WCAG AA) · Mobile viewport · Language declared · Image alt text · Inline validation

Brand kit

5 colour roles

palette by on-page usage · type rendered live

measuredextracted directly from the live page. a fact, not an opinion
full palette ordered by on-page usage %
accent#f8fafc
bg#f8fafc
surface#ffffff
text#ffffff
See the roles applied
accent

Body copy in their text role, on a surface card.

the roles, doing their job
The quick brown fox72px
Jumps over the lazy dog30px
A subheading in their voice20px

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
12pxAa
14pxAa
16pxAa
18pxAa
20pxAa
30pxAa
72pxAa
WEIGHTS
Aa400
Aa500
Aa600
Aa700
Aa800
FAMILIES
Space Grotesk · Inter
rendered in their own type system · webfont not loaded. system fallback if uninstalled

Measured, found none

1 of 9 layers

layers we ran on this funnel that came back empty

measuredextracted directly from the live page. a fact, not an opinion

Playbook match — which funnel play this page runs — measured, evidence-quoted

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.

X-ray a funnel

Your competitor's funnel is one URL away.

Give your AI real references · Measured facts, not taste

Similar crawls