saas · Aug 15, 2026

quitlo.com

60/100 Partial

Scores above 65% of 1,252 multi-step funnels we have measured. Among the 959 saas funnels in that group, above 57%.

5/11 tactics
4 steps
12 checks
4 flagged

How this was measured

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.

Measured by Roentgen 1.25.1, one of our versioned rulesets. A capture is read once and its measurements freeze there, so the stamp says which ruleset read this one.

Walk 34 links seen, 27 walkable, 4 matched, and we walked 4 pages.

Scan

Captured Homepage / Lander — Step 1 · Homepage / Lander1 / 4

What we recorded

Progress

2 scans

this funnel’s coverage score across measured re-scans

measured

0pts since the first measured scan (2026-08-09) — 2 re-scans

60 Partial 2026-08-09
→
60 Partial 2026-08-15

The funnel, frame by frame

4 steps walked

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

measured

Homepage / Lander

3 tactics

$0.40 +4 more · subscription

FAQLogo wallDemo / docs

Pricing

▲ strongest

4 tactics

$0 +2 more

Free trialLogo wallPricing tiersDemo / docs

Ali Varinlioglu

▼ thinnest

0 tactics

no named tactics detected on this step

Product

1 tactic

Demo / docs

In their own words

24 quoted

the entry page’s own title, headline, buttons and prices — quoted, never paraphrased

measured

Page title: Quitlo — AI Payment Recovery for SaaS
Meta description: AI voice calls for failed SaaS payments. When dunning emails don't work, Quitlo calls your customer, finds the issue, and sends a payment update link. Structured recovery report in Slack.
Headline: Dunning recovers 30%. We call about the rest.
Section headings: Every recovery. In Slack.Five minutes. Recovering revenue by tomorrow.We only make money when you do.Connects to the tools you already useCommon questions. Straight answers.Recover the revenue your emails are missing.WHY PAYMENTS FAIL
Buttons and links: ProductTry It LiveDo customers actually pick up?Do they know it’s AI?What if their card is permanently cancelled?What Stripe access does Quitlo need?LightBook a DemoBook a Demo →
Prices on the page: $0.40$7$149$0$4,850

Sections

4 identified

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

measured

Nav section of quitlo.com — **Nav**1% down the page

Pricing section of quitlo.com — **Pricing**52% down the page

FAQ section of quitlo.com — **FAQ**72% down the page

Footer section of quitlo.com — **Footer**87% down the page

Elements

1 harvested

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

measured

Rating element — **Rating**“Configurable call timing (day 3/5/7)”

What we found

5 tactics

conversion tactics we could prove are present, with the on-page text that evidences each

measured

Offer clarity1 of 1

Makes the pricing ladder explicit $349/mo, $1,499/mo, free, $99/mo

Action path2 of 4

Offers a free trial or free tier free trial

Offers a demo or docs entry point Book a Demo

Trust & proof1 of 2

Shows customer logos or a trusted-by claim logos: Google, Adobe, Microsoft, Dropbox, L'Oréal

Friction reduction2 of 2

Answers buyer objections Common questions. Straight answers.

Offers a free trial or free tier free trial

What we didn’t find

6 of 11 applicable

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

measured

What we didn’t see6 of 11 applicable

Press / "as seen in" 448 of 1769 measured funnels run this

Lead-capture form 310 of 1256 measured funnels run this

Us-vs-them comparison 304 of 1777 measured funnels run this

Proof above the fold 292 of 1777 measured funnels run this

Usage / adoption proof 224 of 1369 measured funnels run this

Scarcity / urgency copy 94 of 1769 measured funnels run this

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

12 run · 4 flagged

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

measured

Readability & contrastclear

Text contrast (WCAG AA) passescontrast:text-contrast-wcag-aa

100% of measurable text passes WCAG AA.

Mobile & tap targetsclear

Mobile viewport passesmobile:mobile-viewport

Responsive viewport meta is present.

Typography1 flagged

Body text size needs worktype:body-text-size

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

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

Line length notetype:line-length

30 paragraphs run past ~95 characters per line.

fix Cap measure at ~60-75ch for comfortable reading.

Accessibility hygieneclear

Weight & delivery2 flagged

Page weight not measurableweight:page-weight

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

Render-blocking resources needs workweight:render-blocking-resources

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

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

Oversized images needs workweight:oversized-images

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

“logo-white.4ce1da9b.png” is 882px wide, displayed at 82px

fix Serve responsive sizes (srcset/sizes) matching the rendered width.