Your landing page’s weakest score is Trust.
How Radius ranks
category scores
category scoresShowHide
Score over time
Trust
58FairProof that the product is real, competent, and safe to try.



| Trust read | |
|---|---|
| Radius | Detailed product screenshot showing an agent session editing files ("Edited 3 files +15 -5") with passing tests in the t |
| "feels like going from typing with two fingers to having eight arms" — Frank, Product Designer, Thinking Machines | |
| No visible trust signal identified. | |
| No visible trust signal identified. | |
| Detailed 'Cursor Desktop' product UI showing the 'Plan Mission Control' agent workflow and Cursor CLI output | |
| Embedded Devin session demo showing the task "Migrate all gradient text to #317CFF in both repos, then test" with real P |
Mobile web
74FairThe phone experience as a first-class citizen.
123- Clipped app screenshot — Desktop IDE capture runs off the right edge, truncating chat text and diff counts mid-word.
- Download for macOS button — Desktop-proportioned pill floats in the column instead of a full-bleed, thumb-friendly tap target.
- Tiny terminal text — Terminal output in the screenshot renders at squint-small size, unreadable on a phone.
CTA
78FairCopy, size, verb, cost-feel — does the primary CTA earn the click?



Problems
- download feels heavy, no de-risking
- no value payoff in the label
- macOS-only excludes other visitors
Information hierarchy
82StrongDoes the design help or inhibit what the page is trying to say?
123- Duplicate nav Download button — Outlined nav Download competes at near-equal weight with the hero "Download for macOS" CTA.
- Three nav exit links — Docs, Changelog, and Community sit above the CTA and leak attention before the download action.
- Cropped product screenshot — The agent-session screenshot is cut mid-fold, so its diff/terminal payoff never lands on desktop.
Value props
82StrongTitle, subtitle, hero — do they sell the product's true value?
Your browser should be your IDE.
Radius is a browser where you can run coding agents in parallel, right next to your PRs, docs, terminals, and localhost servers.
Working
- Bold, concrete category claim
- Subhead lists real dev nouns
- Hero shows agent fixing a real issue
Could improve
- No numbers or measurable outcome
- Emotionally flat — no pain named
- Parallel-agent payoff left implicit
