LYTMS
Your strongest differentiation — the integrated network stack competitors can't replicate — is buried in a product catalog grid while the hero sells a category.
“The visual shows Cloudflare Pages as 'Faster' and competitors as 'Slower' with no methodology, test date, sample size, or third-party source cited...”
Link the graphic to a published benchmark page with methodology, or replace it with a specific, sourceable metric ('median TTFB of Xms across 330 cities, tested by [third party], [date]').
Get the ship-ready rewrite →Your performance comparison graphic names competitors but gives evaluators no way to verify the claim. Developers comparing you against Vercel or Netlify will Google the benchmark — and if they can't find it, the graphic works against you.
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 cannot decide who it's selling to, and that indecision is costing it both audiences.
▸ Read the full takeCollapseThe hero says "Developers, designers, and product teams can work together" — three distinct buyers with different needs, different objections, and different reasons to care about a serverless platform. A designer evaluating a collaboration tool and a developer evaluating cold-start performance are not on the same page in any meaningful sense, and this page tries to hold both. The result is that neither buyer sees themselves clearly enough to act. Pick the buyer who signs up and pays — almost certainly the developer — and build the page for them. The designer and PM angle can live in a collaboration-specific section lower on the page, not in the hero where it dilutes the primary conversion.
The page leads with what Cloudflare Pages does, not with the problem the developer came to solve.
▸ Read the full takeCollapse"Build and deploy full-stack applications instantly" describes the product; it doesn't name the situation the developer is already in. Developers landing on this page are almost certainly coming from a comparison — they're evaluating against Vercel or Netlify, they've hit a cold start problem, they've been burned by region complexity, or they're looking at a bill that surprised them. None of those situations appear in the hero. The page skips directly to the product without framing why this moment matters. Move the shift the developer is already feeling — unpredictable infrastructure costs, cold start latency, region lock-in — into the first thing they read, and let the product answer that specific frustration rather than announcing itself.
The single piece of named proof on the page — Sammi Sinno, CEO of Leagued — is doing the wrong job.
▸ Read the full takeCollapse“The visual shows Cloudflare Pages as 'Faster' and competitors as 'Slower' with no methodology, test date, sample size, or third-party source cited anywhere on the page.”
“No customer logos are present. No G2, Trustpilot, or aggregator review counts are referenced. The single testimonial is about a different product (Workers KV, not Pages). The '20% of the Internet' claim is unlinked and unsourced.”
“Connect, protect, and build everywhere. ...|... Need help selecting a Cloudflare product? Answer these quick questions to view your personalized recommendations and see plans and pricing.”
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.
The quote describes Workers KV, not Cloudflare Pages. A buyer evaluating Pages reads a testimonial about a different product. That's not proof; it's noise that erodes trust in the proof you do have. Cloudflare runs infrastructure for 20% of the internet, which means there are named customers who use Pages specifically — find one, get a quote that names the Pages experience (deployment speed, cold start absence, pricing predictability), and put it above the fold. The current quote is worse than no quote because it signals that the best proof you could find doesn't actually apply.
The performance comparison graphic — "Cloudflare Pages: Faster / Competitors: Slower" — is the kind of claim that makes a skeptical developer distrust everything around it.
▸ Read the full takeCollapseThere's no methodology, no named competitor, no benchmark source. Developers read this and immediately ask "faster at what, measured how, compared to whom." An unattributed speed claim from the vendor being evaluated is not evidence; it's marketing, and developers know it. Either replace it with a specific, reproducible benchmark (milliseconds of TTFB at a named percentile, against a named competitor, with a link to the methodology) or remove it and let the "330+ cities, no cold starts" claims carry the performance argument — those are concrete and falsifiable.