LYTMS
Kieran Flanagan's testimonial nails what Loom is — the hero doesn't, and it's buried in a carousel.
“The page leads with 'One video is worth a thousand words' and AI-powered team productivity — framing that assumes visitors already want an async...”
Add one line before the scroll — something that confirms Loom records your screen on Mac, Windows, and mobile — so solution_aware visitors know they're in the right place before you pitch the bigger value. The enterprise vision can still follow immediately after.
Get the ship-ready rewrite →Your page opens by selling the vision — async video as a productivity layer for teams — before it's confirmed you can do the thing these visitors searched for. Over half your traffic (53.99% solution_aware) arrived asking 'how do I record...
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 two completely different buyers with one message, and it's converting neither cleanly.
▸ Read the full takeCollapseThe hero targets a self-serve individual ("Get Loom for free," "the easiest screen recorder you'll ever use") while the body pivots to enterprise signals — SSO, SCIM, custom data retention, a dedicated Enterprise section, and testimonials from a Chief People Officer and a Co-CEO. A solo user who lands on "free" and "easy" reads three sections before hitting enterprise security copy and loses the thread of what they signed up for. An enterprise buyer who lands on the page sees "free" and "easiest screen recorder" and wonders if this is a serious tool for their org. Split the page into two distinct paths above the fold — a self-serve entry and a team/enterprise entry — or pick the primary buyer and build the page for them, with the secondary path as a secondary CTA.
The hero headline, "One video is worth a thousand words," positions Loom as a generic communication upgrade rather than the specific category it actually owns.
▸ Read the full takeCollapseEvery async video tool, every Vidyard, every Zoom clip feature, every Slack huddle could run this headline without changing a word. The page has a real positional claim available — Loom is the tool that replaces the meeting you were about to schedule, the email chain that was about to take three days — but the hero buries it in the subheadline behind "AI-powered" and "supercharge productivity," two phrases that appear on competitors' pages verbatim. Kieran Flanagan's testimonial ("Begin writing an email. Get to the second paragraph and think 'what a time suck.' Record a Loom instead.") is the sharpest articulation of Loom's actual value on the entire page, and it's sitting in a carousel. Move that specific behavior — the moment of switching from email to video — into the hero, because that's the word Loom should own: the replacement.
The AI bug report feature is introduced as "New!
“The page leads with 'One video is worth a thousand words' and AI-powered team productivity — framing that assumes visitors already want an async video messaging tool. But 53.99% of inbound search volume is solution_aware traffic searching for 'how to screenshot on mac', 'how to screen capture windows', and 'how can i r”
“The page has one primary CTA ('Get Loom for free') and one secondary enterprise path ('Learn more') with no routing logic between them. The use-case section lists Sales, Engineering, Customer Support, and Design — but none of those links lead to a differentiated landing experience. Every path collapses into the same fu”
“Easily record and share AI-powered video messages with your teammates and customers to supercharge productivity”
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.
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.
" in the body with its own "Learn more" link, but it's positioned as a product announcement rather than a reason to choose Loom over anything else. This is the most differentiated thing on the page — no competitor is offering automatic Jira ticket population from a screen recording — and it's treated like a changelog entry. A developer or engineering lead who lands on this page and is evaluating Loom against Zoom's built-in recording or Slack clips would have no idea this feature exists until they scroll past the hero, past the "easiest screen recorder" section, past the editor features. Pull the bug report capability into the hero or into a dedicated above-the-fold proof point aimed at engineering buyers, because right now the page's most defensible claim is hidden behind generic copy.
The testimonials are named and credible — HubSpot, Typeform, Meta — but they're all deployed in a carousel, which means most visitors see one or two before moving on, and the page never uses them to answer a specific objection.
▸ Read the full takeCollapseKatie Burke's quote about connecting personally without "75 different one-on-one calls" directly addresses the meeting-replacement use case. Erica Goodell's quote about "hundreds of hours" directly addresses ROI. David Okuinev's quote about executive communication directly addresses the enterprise buyer. None of these are placed adjacent to the claim they support — they're pooled together in a rotating strip that treats all proof as interchangeable. Anchor each testimonial to the section it validates: put the hours-saved quote next to the productivity claim, put the executive quote next to the Enterprise section, put the meeting-replacement quote in the hero.