Body text size
type:Smallest body text is 10px (base ~13px). below the ~16px readable floor.
FixKeep body copy ≥15-16px; reserve sub-13px for fine print only.
saas · Sep 4, 2026
50/100 Thin
Scores higher than 49% of 1,391 multi-step funnels we have measured. Among the 1,074 saas funnels in that group, higher than 38%.
Measured by Roentgen 1.27.0 on 2026-09-04. 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.
Walk 8 links on the entry page, 2 walkable. 1 matched a funnel step; we captured 2 pages in all, this one included.
the entry page’s own title, headline, buttons and prices — quoted, never paraphrased
measuredextracted directly from the live page. a fact, not an opinionRay 3.2 AI Video Generator - Create Controlled Videos Online
Stop storyboarding. Start generating. Ray 3.2 creates smooth, cinematic AI video from your words or photos. HD output, multiple modes. Try it free now.
Ray 3.2 AI Video Generator
Try Ray 3.2 Online
What Is Ray 3.2?
What Can You Do with Ray 3.2 ?
Ray 3.2 Capabilities: 8 Production-Grade Features
Ray 3.2 Tech Specs: 1080p HDR, EXR & API
How to Use Ray 3.2 Online
Ray 3.2 Use Cases by Industry
Ray3 Vs Ray 3.14 Vs Ray 3.2+8 more, not shown
Login
Text to Video
Image to Video
Video Edit
Reframe
+
Generate with Ray 3.2 45 Credits
Get Started
Upgrade Now
What is Ray 3.2?+2 more, not shown
$9.9
$29.9
$49.9
$99.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 opinionTry it free
logo wall (4 distinct marks)
What is Ray 3.2? Is this the official Luma website? Can I use Ray 3.2 without a local GPU?
comparison grid: 18 rows
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 opinion2 of 10 measured checks need work1 could not be measured — not counted either way
Smallest body text is 10px (base ~13px). below the ~16px readable floor.
FixKeep body copy ≥15-16px; reserve sub-13px for fine print only.
5 images are shipped at more than 2x the width shown.
“ray-3-2-home-usecase-1.webp” is 1280px wide, displayed at 441px
FixServe responsive sizes (srcset/sizes) matching the rendered width.
9 paragraphs run past ~95 characters per line.
FixCap measure at ~60-75ch for comfortable reading.
type: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 <header> landmark. screen-reader users cannot jump between regions.
FixWrap the page in <header>, <main> and <footer> (or matching ARIA roles).
structure:At least 0.7 MB across 52 measurable resources, but 101 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
which funnel play this page runs — measured, evidence-quoted
deriveda deterministic summary generated only from measured facts. labeled, never an LLM guessComparison surface matches the Intent-Match pattern — measured comparison table plus comparison-intent copy
home: comparison grid: 18 rowscomparison copy
Ray3 Vs Ray 3.14 Vs Ray 3.2
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.