Your landing page’s weakest score is CTA.
How Philon ranks
40Growth scoreupdated
category scores
category scoresShowHide
Score over time
CTA
32PoorCopy, size, verb, cost-feel — does the primary CTA earn the click?
Problems
- no CTA exists on the page
- only action is footer mailto
- open-source claim has no repo link
Information hierarchy
42PoorDoes the design help or inhibit what the page is trying to say?
123- Email footer link — The only actionable element is a low-contrast mailto link in the footer — the page has no primary CTA.
- Backer badges row — Investor badges sit above and outweigh the mission statement, outranking the value proposition.
- Mission statement text — The core value prop is set at body-text weight with no headline hierarchy, so it reads as an afterthought.
Trust
42PoorProof that the product is real, competent, and safe to try.
| Trust read | |
|---|---|
| Philon | Backed by Y-Combinator badge |
| implicit context Figure AI may benefit from pre-existing familiarity among its target audience. | |
| Hero photo of the Apollo robot performing real warehouse pick-and-pack work | |
| Hero photography of the NEO robot in three colorways | |
| "Digit is a humanoid robot with 65,000 hours of real production experience" (mobile fold) | |
| Mobile spec line "Ultra-wide 4D LIDAR、Stronger performance、New Creature of Embodied AI" under "Infinite Revolution" with |
Mobile web
42PoorThe phone experience as a first-class citizen.
12- Email footer link — The only actionable element is a small, gray mailto link — no primary CTA button exists on the page.
- Mission statement block — Value statement ends with no action beneath it, leaving visitors nothing to tap.
Value props
44PoorTitle, subtitle, hero — do they sell the product's true value?
Philon’s headline vague
Building open-source general-purpose robots capable of performing unsafe, repetitive or boring tasks.
Working
- Names real pains: unsafe, repetitive, boring
- Open-source stance is a clear differentiator
- YC + founder backing adds credibility
Could improve
- No subhead or specifics on use cases
- No image showing a robot doing work
- "Building" describes activity, not outcome