CoArenaYC S26 landing page report.
← Back to YC S26

Your landing page’s weakest score is Trust.

Fix Trust

Score over time

807570656055Chatbot Arena (LMArena) 62 on Jun 30 (Wayback)Chatbot Arena (LMArena) 63 on Jul 15 (Wayback)Chatbot Arena (LMArena) 62 on Jul 24 (Wayback)Chatbot Arena (LMArena) 63 on Aug 6 (Wayback)Chatbot Arena (LMArena) 66 on Aug 24 (Wayback)Chatbot Arena (LMArena) 63 on Sep 5 (Wayback)Chatbot Arena (LMArena) 66 on Sep 20 (Live)WebDev Arena 62 on Sep 21 (Live)Design Arena 73 on Jun 16 (Wayback)Design Arena 69 on Jun 26 (Wayback)Design Arena 72 on Jul 11 (Wayback)Design Arena 66 on Aug 5 (Wayback)Design Arena 74 on Aug 19 (Wayback)Design Arena 72 on Sep 9 (Wayback)Design Arena 70 on Sep 21 (Live)CoArena 66 on Aug 15 (Wayback)CoArena 67 on Sep 20 (Live)Aug 15Sep 20
Past reportsShow past reportsHide past reports
  1. Sep 20, 202667LiveOverall +1 · Mobile web +8 · Value props −5Viewing
  2. Aug 15, 202666First tracked report — strongest Information hierarchy 76, weakest Trust 44View →

Trust

48Poor

Proof that the product is real, competent, and safe to try.

CoArena
Design Arena
Chatbot Arena (LMArena)
Trust read
CoArena"Backed by Y Combinator" badge above the headline
Chatbot Arena (LMArena)Live "Ask anything…" prompt box with Battle/Auto mode controls showing real product UI
WebDev Arenaimplicit context WebDev Arena may benefit from pre-existing familiarity among its target audience.
Design Arena"6.6M+ users" count beneath the headline

Value props

58Fair

Title, subtitle, hero — do they sell the product's true value?

CoArena’s headline undersellsWatch two computer-use agents work on your fact-check.

Working

  • Literal, product-specific verb: "Watch two agents"
  • Placeholder prompt is a vivid concrete example
  • Rotating task word shows breadth of use cases

Could improve

  • No subhead explaining why two agents compete
  • Zero numbers or proof points in the fold
  • Desktop rotator truncates mid-word ("data pu.")

Information hierarchy

72Fair

Does the design help or inhibit what the page is trying to say?

Information hierarchy annotations on the desktop capture1234
  1. Animated rotating headline word — The cycling word ('data pu…' caught mid-transition) renders the core promise unreadable at a glance and momentarily garbled.
  2. Header nav links — Leaderboard, Benchmarks, Blog and Sign in offer four exits before the visitor reaches the Send prompt.
  3. Send button — Small footprint tucked in the composer corner; it reads as a form control, not the page's primary action.
  4. Terms consent line — Two underlined legal links sit directly under the CTA, adding exits and legal friction at the decision point.

CTA

78Fair

Copy, size, verb, cost-feel — does the primary CTA earn the click?

CoArenain-product action
Chatbot Arena (LMArena)in-product action
WebDev Arenain-product action
Design Arenain-product action

Problems

  • 'Send' promises no payoff
  • placeholder runs 20 words
  • no free/no-signup reassurance

Mobile web

78Fair

The phone experience as a first-class citizen.

Mobile web annotations on the mobile capture12
  1. Uncollapsed nav row — Desktop link row (Leaderboard, Benchmarks, Sign in) crammed across the top instead of a hamburger, and the Blog link is silently dropped.
  2. Three-line legal disclaimer — Dense Terms/Privacy paragraph sits directly under the Send button, adding visual noise around the primary action.

Competitors

inferred from product, audience, and value prop