LYTMS
The page pitches riders, drivers, and enterprise buyers in one scroll — none of them get a clear path.
“Riders say 'cheap ride,' 'surge pricing,' 'wait time.' Drivers say 'earnings per hour,' 'cash out,' 'acceptance rate.' Enterprise buyers say...”
Pull the top 10 phrases from App Store reviews (riders and drivers) and G2/Capterra reviews (enterprise). Map each phrase to the segment it belongs to. Replace at least three body sentences per segment with verbatim or near-verbatim buyer language.
Get the ship-ready rewrite →The page speaks to three audiences simultaneously and uses none of their actual words. Riders, drivers, and enterprise buyers each have a distinct vocabulary — none of it appears here.
Not five scoring areas. Five questions, asked in sequence. The page is judged on how many it answers before the visitor gives up.
The page is trying to convert three completely different buyers at once — riders, drivers, and enterprise procurement teams — and ends up converting none of them cleanly.
▸ Read the full takeCollapseThe hero says "Go anywhere with Uber" (rider), the body immediately pivots to "Drive when you want, make what you need" (driver), then pivots again to "Uber for Business is a platform for managing global rides and meals" (enterprise). These are three separate purchase decisions made by three separate people with three separate reasons to be on the page; stacking them in a single scroll forces every visitor to wade through two irrelevant pitches to find their own. The move is segmentation above the fold: a three-path entry point (Ride, Drive, Business) that routes each visitor to a page built for them, rather than a single page that hedges across all three.
The subheadline "Explore what you can do with Uber" is the page's only attempt at a positioning statement, and it says nothing.
▸ Read the full takeCollapseUber is one of the most recognized brands in the world; the visitor already knows what Uber does. The page wastes the one sentence that could do strategic work — naming why Uber over Lyft, why now, why this version of the product — on a phrase that functions as a placeholder. Lyft's homepage makes the same non-claim. The page has a genuine differentiation story available (one platform for rides, meals, deliveries, and corporate travel that no single competitor matches end-to-end) and buries it in the body as a subordinate clause about Uber for Business. Move that multi-service consolidation claim to the hero; it's the only thing on this page that Lyft cannot say.
The primary CTA is "See prices," which is a research behavior, not a commitment behavior.
▸ Read the full takeCollapse“Riders say 'cheap ride,' 'surge pricing,' 'wait time.' Drivers say 'earnings per hour,' 'cash out,' 'acceptance rate.' Enterprise buyers say 'expense reconciliation,' 'travel policy,' 'receipt management.' The page uses none of these phrases. The copy is Uber's internal language, not the buyer's language.”
“Uber has millions of reviews on the App Store, Google Play, and aggregator sites. None of that proof appears on the homepage — no star rating, no '5M+ riders this month,' no named enterprise customer. Three modules silenced because the page has no proof signals to evaluate.”
“LP says "Go anywhere with Uber" / "Explore what you can do with Uber"; lyft.com says "The world awaits. No matter where you're headed, we'll help you get there." Both heroes make the same generic mobility promise. Meanwhile, Uber's actual multi-service + corporate platform claim — "Uber for Business is a platform for m”
Every finding named, quoted, and paired with the rewrite — that’s how Lytms reads a page. Run it on your own site to see all of yours, free.
Hero value, conversion-killing sentences, cliché density, awareness fit, buyer-language gap, competitive differentiation.
Proof architecture, named-customer recognition, imagery authenticity, claim-vs-evidence gaps.
A live feed of what the category is moving toward, with a drafted response for the moves worth responding to.
Pick one competitor on Pro. Same scoring this page is held to. Same-day alert when they ship a homepage change.
Mine reviews, transcripts, support, social. Ranked, attributed, matched against the homepage.
Accept, edit, ship. An action queue tied to a CMS or copied straight to clipboard.
Lytms reads any B2B homepage the same way — verdict, five scores, every line that costs the visit. Free to run. Full report and drafted rewrites on Pro.
A visitor who already knows Uber and has a destination in mind doesn't need to see prices — they need to book. The ride booking interface with pickup and dropoff fields is already on the page, which means the actual conversion surface exists, but the CTA above it points away from it toward a pricing lookup. The page is directing motivated buyers into a consideration loop they've already completed. Remove "See prices" as the primary CTA; let the booking interface be the CTA, and make the label on the submit action "Get a ride" or the equivalent direct verb.
The safety section — "Turn on and schedule your safety preferences, all in the Uber app" — appears as a single sentence in the body with no specifics, no named features, and no proof.
▸ Read the full takeCollapseSafety is the single most-searched objection in ride-hailing; it's the reason enterprise procurement teams require policy controls and the reason solo riders choose one platform over another at night. The page acknowledges safety exists and immediately drops it. The Uber app has named safety features (RideCheck, PIN verification, trusted contacts, live location sharing) that competitors have not matched at the same depth. Name them on this page, above the fold for the rider path, with a one-line description of what each one does. A sentence that says "safety is in the app" is not a safety argument; it's a deflection.