LYTMS
Netlify lists five buyer types in the tabs and commits to none of them in the headline.
“Push your ideas to the web”
Rewrite the headline around what makes Netlify the better choice for developers already in the market — something grounded in the instant-preview-to-production workflow or the scale numbers (60M+ apps, 99.99% uptime) that the rest of the page earns. The subheadline is doing the work your headline should be doing.
Get the ship-ready rewrite →Your headline is written for someone who has never deployed anything — a person with vague "ideas" who needs encouragement. But the developers landing here already know what deployment is and are actively comparing you to Vercel or...
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 has no differentiated position.
▸ Read the full takeCollapseNetlify's hero says "Push your ideas to the web" and the body promises "one platform to build and ship" — and Vercel's homepage says almost exactly the same thing, down to the AI-to-deploy workflow, instant previews, and global CDN. The page lists every capability Netlify has (AI apps, Git push, drag-and-drop, edge functions, background jobs, image optimization) without committing to the one thing Netlify wins on. A developer who lands here after reading Vercel's homepage cannot tell which platform they're on or why it matters which one they choose. Pick the axis Netlify actually wins — whether that's the breadth of deployment paths, the framework-agnostic infrastructure, or the 10M-developer ecosystem — and build the entire page around defending that single claim. Everything else is noise until that decision is made.
The testimonial is doing the wrong job.
▸ Read the full takeCollapseJeffrey Sica's quote — "I can push a change, and within 30 seconds the site is completely rebuilt" — proves speed, which is table stakes in this category. Every competitor claims fast deploys. The quote doesn't prove that Netlify is the right choice over Vercel or Railway; it proves that Netlify is a deployment platform, which the visitor already knows. Netlify has 10M developers and 60M deployed apps — somewhere in that base are customers who switched from a competitor and can name what changed. A quote that says "we moved from Vercel and our preview workflow got simpler" or "we consolidated three tools into Netlify and cut our deploy overhead" does real positioning work. Replace the current quote with one that names the before-state and the specific outcome, not just a speed metric.
The page tries to speak to five different buyers simultaneously and converts none of them cleanly.
▸ Read the full take“Push your ideas to the web”
“'Start building' is the only action available. A developer who wants to compare pricing, read a case study, or explore the API has nowhere to go except away from the page. No secondary CTA for 'See pricing', 'Read docs', or 'View demo' exists in the hero or body.”
“Start building — sole CTA on the page; no secondary link to pricing or plan comparison anywhere in hero or body”
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.
Call-to-action clarity, visual weight, offer strength, form friction, CTA-to-page match.
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.
The use-case tabs — AI apps, Marketing sites, SaaS apps, Ecommerce, Internal tools — signal that the page knows it has multiple audiences but hasn't chosen a primary one. The hero copy ("Push your ideas to the web") is broad enough to address all five, which means it's written for none of them specifically. A developer building an internal tool has a different fear than a founder shipping an ecommerce site; the page never names either fear, so it never earns either buyer's trust. Either commit the homepage to the highest-value ICP (fullstack developers at startups building production apps) and move the other use cases to dedicated landing pages, or restructure the page so the hero names the primary buyer and the tabs are positioned as "also works for" rather than equal alternatives.
The page has no failure scenario.
▸ Read the full takeCollapseEvery section describes what Netlify does; none of them name what goes wrong when a developer doesn't use it. The body lists capabilities — "connect APIs, manage data, optimize images, add AI features" — but never says what the developer is currently suffering through that makes those capabilities matter. Netlify's own blog from 2016 makes a sharper case for static sites than the current homepage makes for the platform. The developer who lands here is probably managing a fragmented deploy stack, dealing with slow preview cycles, or stitching together three tools to do what Netlify does in one. Name that situation above the fold — not as a feature list, but as the specific operational pain the developer is living with — and the rest of the page becomes evidence that Netlify solves it.