Smallest body text is 9px (base ~16px). below the ~16px readable floor.
fix Keep body copy ≥15-16px; reserve sub-13px for fine print only.
01
Homepage / Lander
6 tactics
subscription
saas · Aug 16, 2026
zens.ai
70/100 Partial
Scores above 81% of 1,252 multi-step funnels we have measured. Among the 959 saas funnels in that group, above 76%.
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 21 links seen, 9 walkable, 3 matched, and we walked 4 pages.
What we recorded
The funnel, frame by frame
4 steps walkedIn their own words
31 quotedthe 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
Zens AI - AI Customer Support for Loop Engineering
- Meta description
Zens AI is an AI customer support system that turns user feedback into Codex and Multica workflows, helping SaaS teams improve every week.
- Headline
Support that never sleeps
- Section headings
Connect customer support to product work
See what a support lead can do with Zens AI
See how Zens AI turns support into product progress
Support breaks when feedback cannot move
Give support agents the ability to act
Everything a support loop needs
Why choose Zens AI
Connect your support agent in three steps
+8 more, not shown- Buttons and links
Sign In
Start AI support
Support lead
Product manager
Growth team
Founder
Agent developer
Success team
01 Spot repeated questions from high-value accounts
02 Prepare human handoff context
+2 more, not shown
Sections
4 identified
structural bands identified on this funnel, cropped from its own capture
measuredextracted directly from the live page. a fact, not an opinion
What we found
6 tacticsconversion tactics we could prove are present, with the on-page text that evidences each
measuredextracted directly from the live page. a fact, not an opinionOffer clarity1 of 1
Makes the pricing ladder explicit
$29/mo, $79/mo, $199/mo, free
Action path2 of 4
Offers a free trial or free tier
Start free
Offers a demo or docs entry point
docs link
Trust & proof1 of 2
Shows customer logos or a trusted-by claim
logo wall (4 distinct marks)
Friction reduction2 of 2
Answers buyer objections
How is Zens AI different from a regular live chat tool? Zens AI is more than a chat window
Offers a free trial or free tier
Start free
Value reinforcement1 of 2
Compares itself against alternatives
comparison grid: 16 rows
What we didn’t find
5 of 11 applicableapplicable tactics we checked for and did not see on any step we reached
measuredextracted directly from the live page. a fact, not an opinionWhat we didn’t see5 of 11 applicable
Press / "as seen in"
448 of 1769 measured funnels run this
Lead-capture form
310 of 1256 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
14 run · 5 flaggedcontrast, mobile, typography, accessibility, weight — each with what would fix it
measuredextracted directly from the live page. a fact, not an opinionReadability & contrast1 flagged
Text contrast (WCAG AA) needs workcontrast:text-contrast-wcag-aa
67% of measurable text passes WCAG AA. 3+ runs fail. 87% of text was unmeasurable (over images/gradients). not counted either way.
worst: “zens.” at 1.1:1 (390px, #fdfbfb on #ecf1f5). needs 3:1
fix Raise text/background contrast to ≥4.5:1 (≥3:1 for large text), especially on CTAs and body copy.
Mobile & tap targetsclear
Mobile viewport passesmobile:mobile-viewport
Responsive viewport meta is present.
Typography1 flagged
Body text size needs worktype:body-text-size
Line length notetype:line-length
26 paragraphs run past ~95 characters per line.
fix Cap measure at ~60-75ch for comfortable reading.
Accessibility hygiene1 flagged
Language declared passesa11y:language-declared
html[lang] is set for screen readers.
Image alt text passesa11y:image-alt-text
All 14 content images carry alt text.
Named controls needs worka11y:named-controls
6 buttons/links have no accessible name (icon-only, no aria-label).
fix Add aria-label to icon-only buttons and links.
Heading levels notea11y:heading-levels
1 heading skips a level (e.g. <h2> followed by <h4>). Screen-reader users navigate by this outline.
fix Step heading levels one at a time; use CSS for size, not a deeper level.
Label in name notea11y:label-in-name
9 controls have an aria-label that does not contain its visible text, so voice-control users cannot activate it by saying what they see.
fix Make the accessible name start with the visible label text.
Weight & delivery1 flagged
Page weight not measurableweight:page-weight
At least 1.0 MB across 95 measurable resources, but 55 cross-origin resources did not expose a size. The true weight cannot be determined from the page.
Render-blocking resources noteweight:render-blocking-resources
4 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
12 images are shipped at more than 2x the width shown.
“logo-wordmark.png” is 1200px wide, displayed at 137px
fix Serve responsive sizes (srcset/sizes) matching the rendered width.
Structure & reachability1 flagged
Landmark regions needs workstructure:landmark-regions
No <header> or <footer> landmark. screen-reader users cannot jump between regions.
fix Wrap the page in <header>, <main> and <footer> (or matching ARIA roles).
Keyboard reachability notestructure:keyboard-reachability
5 elements look clickable but cannot be reached by keyboard.
“How is Zens AI different from a re”, “Which teams is Zens AI built for?”, “Will AI replies be sent to custome”
fix Use <button>/<a>, or add role + tabindex="0" and a key handler.
Brand kit
5 colour roles
palette by on-page usage · type rendered live
measuredextracted directly from the live page. a fact, not an opinionfull palette ordered by on-page usage %
primary#eaefcd
accent#eaefcd
bg#ecf1f5
surface#f0f0f0
text#fdfbfb
See the roles applied
accent
Body copy in their text role, on a surface card.
the roles, doing their job
The quick brown fox40px
Jumps over the lazy dog28px
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
9pxAa
10pxAa
11pxAa
12pxAa
13pxAa
14pxAa
15pxAa
16pxAa
18pxAa
20pxAa
28pxAa
40pxAa
WEIGHTS
Aa400
Aa500
Aa600
Aa700
Aa800
FAMILIES
Instrument Serif · Inter
rendered in their own type system · webfont not loaded. system fallback if uninstalled
We also looked for Elements and Playbook match, and found none on this funnel.
X-ray a funnel
