Your landing page’s weakest score is Trust.

Fix Trust
67Growth scoreupdated

category scores

category scoresShowHide

Trust

42Poor

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

Kea
PolyAI (Restaurant Answering)
Hostie
restaurantaireceptionist.com
Loman AI
Trust read
Kea"Activate in 30 minutes or less" setup-speed claim (mobile)
restaurantaireceptionist.com"CALL THE HOSTESS DEMO (916) 545-9316" live demo phone number
Slang.ai"Setup in as little as 30 mins, delivering at least 20x ROI" benefit claim
Loman AIProduct UI mockup showing "Loman's Pizza" dashboard with "Menu updated 3 hours ago" and "Featured Upsells" panel
HostieCustomer logo strip: Tonchin, Chubby Group, Flour + Water, RDG, Slanted Door, Bacchus Management Group
PolyAI (Restaurant Answering)Customer logo strip (Mattel, Office Depot, Brightree, AdaptHealth, Whitbread)

Information hierarchy

72Fair

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

Information hierarchy annotations on the desktop capture1234
  1. Book a Demo button — Same orange primary styling as the hero's Get Started, splitting the fold between two equal-weight actions.
  2. Nav link row — Four nav links plus Log In and Sign Up give seven exits before the visitor reaches the hero CTA.
  3. Six-line subheadline block — Large monospace paragraph wraps to six lines, slowing the scan between headline and CTA row.
  4. Special Instructions caption — Italic orange caption matches CTA color and pulls the eye away from the Get Started button.

CTA

72Fair

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

Kea

How Kea compares

Recommended rewrites

Value props

72Fair

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

Kea’s headlineThe Best Voice AI for RestaurantsDinner rush brings unlimited calls but your team has a limit. Kea is the best voice AI for restaurants: it answers every call, takes orders, and never burns out.

Working

Could improve

Mobile web

76Fair

The phone experience as a first-class citizen.

Kea mobile capture for Mobile web

What works

What to improve