saas · Aug 15, 2026
80/100 Strong
Scores higher than 94% of 1,391 multi-step funnels we have measured. Among the 1,074 saas funnels in that group, higher than 93%.
Measured by Roentgen 1.25.1 on 2026-08-15. 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 80 · mobile 80.
Walk 91 links on the entry page, 80 walkable. 3 matched a funnel step; we captured 4 pages in all, this one included.
this funnel’s coverage score across measured re-scans
measuredextracted directly from the live page. a fact, not an opinionsee their whole funnel without clicking through it. scored step by step
measuredextracted directly from the live page. a fact, not an opinionthe entry page’s own title, headline, buttons and prices — quoted, never paraphrased
measuredextracted directly from the live page. a fact, not an opinionCheapest Twitter API & X API: $0.05/1K Tweets | GetXAPI
GetXAPI is the cheapest Twitter API and X API. $0.001 per call returns ~20 tweets ($0.05 per 1,000). Fetch tweets, profiles, followers. No dev account.
The Cheapest Twitter API. Period.
Built Different. Priced Better.
Twitter / X MCP Server
Real-Time Tweet Monitoring
Why Choose GetXAPI?
Frequently Asked Questions
Uptime SLA
Response Time
Flat-Rate Pricing+5 more, not shown
Compare & Tools
Company
$npx -y @getxapi/mcp@latest
What is GetXAPI and what can I fetch?
Is there a Twitter API free option to test first?
Do I need an official X developer account?
Does GetXAPI have platform-level rate limits?
Should I use a Twitter unofficial API in production?
How does GetXAPI handle my data and privacy?
Start monitoring+2 more, not shown
$0.001
$0.1
$0.01.
$1.00
$10.00
$10
$49
$0.005+9 more, not shown
structural bands identified on this funnel, cropped from its own capture
measuredextracted directly from the live page. a fact, not an opinion
the atomic pieces — price anchors, ratings, guarantees — with their verbatim on-page text
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 opinionfree, $49/mo, $19/mo
free credit
email, password
Read the docs
used by
Frequently Asked Questions
comparison table: Features · GetXAPI BEST VALUE · twitterapi.io · Official API · Others Ap
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 opinion4 of 15 measured checks need work1 could not be measured — not counted either way
93% of measurable text passes WCAG AA. 4+ runs fail. 39% of text was unmeasurable (over images/gradients). not counted either way.
worst: “📊” at 1:1 (30px, #000000 on #000000). needs 3:1
FixRaise text/background contrast to ≥4.5:1 (≥3:1 for large text), especially on CTAs and body copy.
Smallest body text is 9px (base ~14px). below the ~16px readable floor.
FixKeep body copy ≥15-16px; reserve sub-13px for fine print only.
85 images are shipped at more than 2x the width shown.
“logo.png” is 2048px wide, displayed at 24px
FixServe responsive sizes (srcset/sizes) matching the rendered width.
327 of 458 interactive targets are under 44×44px on mobile.
smallest: “Open menu” at 40×40px
FixGive tappable controls a ≥44×44px hit area. the touch minimum.
12 paragraphs run past ~95 characters per line.
FixCap measure at ~60-75ch for comfortable reading.
type:4 headings skip 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:No same-page “skip to content” link was found. Keyboard users tab through the whole nav on every page.
FixAdd a first-in-DOM <a href="#main"> that is visible on focus.
a11y:68 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:No <main> landmark. screen-reader users cannot jump between regions.
FixWrap the page in <header>, <main> and <footer> (or matching ARIA roles).
structure:20 elements look clickable but cannot be reached by keyboard.
FixUse <button>/<a>, or add role + tabindex="0" and a key handler.
structure:At least 2.8 MB across 206 measurable resources, but 227 cross-origin resources did not expose a size. The true weight cannot be determined from the page.
weight:Mobile viewport · Language declared · Image alt text · Render-blocking resources · Inline validation
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 opinionPlaybook 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.
