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




| Trust read | |
|---|---|
| Canary | "Backed by Y Combinator" badge above the headline |
| Customer logo strip: Lifesum, CoinTracker, Orangetheory Fitness, Fanatics, Figma | |
| "Trusted by leading engineering teams." logo wall with Retool, Notion, Webflow, Bilt, Collectors, GPTZero | |
| No visible trust signal identified. | |
| "Test Runs" dashboard screenshot showing real run numbers, agent findings, and linked PRs (#1611, #1431) | |
| "Trusted by organizations including…" logo wall (Brex, Dropbox, Notion, CoreWeave, LaunchDarkly, Wealthsimple) |
CTA
72FairCopy, size, verb, cost-feel — does the primary CTA earn the click?




Problems
- payoff unclear to first-timers
- competes with Start Demo pill
- assumes agent-workflow knowledge
- nav Book a Call splits intent
Information hierarchy
76FairDoes the design help or inhibit what the page is trying to say?
123- BOOK A CALL button — Same yellow weight as the hero CTA, splitting the primary action between two competing conversions.
- Start Demo pill — A third floating action hovers between the CTA and terminal, pulling attention from Copy the Prompt.
- Headline overlap glitch — Ghosted text fragments collide behind 'COPILOT WRITES Canary's CODE.', muddying the first line visitors read.
Mobile web
76FairThe phone experience as a first-class citizen.
123- Clipped Claude Code tab — Tab label wraps and clips mid-word with a second orphaned icon cut off at the screen edge.
- Stray HELP fragment — Orphaned green 'HELP' text renders half-hidden behind the CTA button, signaling a layout bug.
- Start Demo pill — Floating pill overlaps the terminal content and competes with the primary CTA as a second tap target.
Value props
84StrongTitle, subtitle, hero — do they sell the product's true value?
Copilot writes your code. Canary tests it.
Canary is the independent tester for code your agents write. It runs your app, tries to break every change, and reports what would have reached production.
Working
- Sharp contrast vs. tool users already know
- Names the fear: bugs reaching production
- Hero demo shows real diff, not decoration
Could improve
- Zero numbers or proof stats in fold
- "Independent tester" needs a why
- CTA "Copy the prompt" assumes context
