saas · Sep 12, 2026

morsecodetranslator.run

Fewer than 1% of the 1,350 multi-step SaaS funnels we have measured showed fewer conversion tactics than we found here.

1 conversion tactic detected

3 pages walked · measured by Roentgen 1.27.0

1 conversion tactic detected
3 pages captured
12 UX checks
4 flagged

Put this x-ray to work Brief your AI X-ray your funnel

How this was measured

Measured by Roentgen 1.27.0 on 2026-09-12. A capture is read once and its measurements freeze there, so the stamp says which ruleset read this one.

This 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. A low count means we did not detect those patterns, not that the funnel is weak.

Against all 1,781 multi-step funnels, more conversion tactics than 3% of them.

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

The short version, in 5 parts

Proven on the page
1 conversion tactic detected, each backed by text on the page

Shows press logos or an as-seen-in claim
featured on

See all 1
Not seen
10 of 11 applicable tactics we checked for and did not see

FAQ / objection handling
An accordion / FAQ block answering objections.
Trusted-by logo wall
Customer/company logos or a "trusted by / used by" claim.
Free trial / freemium
A free trial, free tier, or "no credit card" entry offer.

+ 7 more

See what we looked for
Flagged
5 of 13 build checks flagged, each with a fix

Body text size
Smallest sampled text is 12px, below the 13px floor this check uses.
Form labels
1 of 9 form fields have no label.
Render-blocking resources
11 stylesheets/scripts in <head> block first paint.

+ 2 more

See the fixes
Walked
3 pages walked, Translators to Morse Code Audio Decoder

Step 1
Translators
Step 2
American Morse Code Translator
Step 3
Morse Code Audio Decoder

Walk it frame by frame
In their words
The headline: Other Code Translators

Promise
Browse Morse code translators for audio, light, images, American Morse, Japanese Wabun, Russian Cyrillic, bin…

Read every quote

Scan

Captured Translators — Step 1 · Translators1 / 3

What we recorded

Progress

2 scans

this funnel’s coverage score across measured re-scans

measured

Unchanged across 2 scans Same 1 conversion tactic detected since 2026-08-09.

1 tactic 2026-08-09
→
1 tactic 2026-09-12

The funnel, frame by frame

3 steps walked

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

measured

Translators

1 tactic

Press

American Morse Code Translator

1 tactic

Press

Morse Code Audio Decoder

1 tactic

Press

In their own words

22 quoted

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

measured

Page title: Morse Code Translators: Audio, Light & More
Meta description: Browse Morse code translators for audio, light, images, American Morse, Japanese Wabun, Russian Cyrillic, binary, NATO phonetics, and tap code.
Headline: Other Code Translators
Section headings: Why a translator directory helps users choose the right toolBrowse other code translatorsWhich specialist translator pages should come nextHow to choose between Morse and adjacent code translatorsOther code translator questionsReturn to the main Morse code translatorHow to read the status labelsAmerican Morse Code Translator+6 more, not shown
Buttons and links: Morse Code TranslatorWordsAlphabetBlogsOpen Morse Code Translator

Sections

3 identified

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

measured

Nav section of morsecodetranslator.run — **Nav**0% down the page

FAQ section of morsecodetranslator.run — **FAQ**78% down the page

Footer section of morsecodetranslator.run — **Footer**94% down the page

What we found

1 tactic

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

measured

proof1 of 4

Shows press logos or an as-seen-in claim featured on

What we didn’t find

10 of 11 applicable

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

measured

What we didn’t see10 of 11 applicable

FAQ / objection handling 1,615 of the 2,420 funnels we checked

Trusted-by logo wall 1,484 of the 2,043 funnels we checked

Free trial / freemium 1,340 of the 1,673 SaaS funnels we checked

Pricing tiers 873 of the 1,673 SaaS funnels we checked

Demo / docs entry 575 of the 1,683 funnels we checked

Us-vs-them comparison 441 of the 2,420 funnels we checked

Lead-capture form 437 of the 1,683 funnels we checked

Proof above the fold 381 of the 2,420 funnels we checked

Usage / adoption proof 289 of the 2,043 funnels we checked

Scarcity / urgency copy 125 of the 2,417 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

13 run · 5 flagged

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

measured

5 of 13 measured checks need work

Body text size

type:body-text-size

Smallest sampled text is 12px, below the 13px floor this check uses.

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

Render-blocking resources

weight:render-blocking-resources

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

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

Oversized images

weight:oversized-images

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

“?url=%2Fimages%2Fdiagnostic-dashboard.pn” is 1672px wide, displayed at 548px

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

Tap-target size (mobile)

mobile:tap-target-size-mobile

19 of 54 interactive targets are under 44×44px on mobile.

smallest: “Menu” at 87×38px

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

Worth knowing3

Line length

20 paragraphs run past ~95 characters per line.

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

type:line-length

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

Clear5

Text contrast (WCAG AA) · Mobile viewport · Language declared · Image alt text · Page weight

Brand kit

5 colour roles

palette by on-page usage · type rendered live

measured

full palette ordered by on-page usage %

accent#1d806d

bg#ffffff

surface#fffdf7

text#65736c

See the roles applied

accent

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

the roles, doing their job

The quick brown fox93px

Jumps over the lazy dog52px

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

12pxAa

13pxAa

15pxAa

16pxAa

20pxAa

52pxAa

93pxAa

WEIGHTS

Aa400

Aa700

Aa800

Aa900

Aa950

FAMILIES

Inter

rendered in their own type system · webfont not loaded. system fallback if uninstalled

Measured, found none

2 of 10 layers

layers we ran on this funnel that came back empty

measured

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

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

We ran these passes 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.

Machine version → JSON bundle Markdown brief Design tokens llms.txt