Is cloudflare.com vibe coded?

Reading this score

cloudflare.com landed on 17/100, which puts it in the hand-written band. That number is not a percentage and not a probability — it is strength of evidence: 50 points of tells, damped by craft, less 46 points of deliberate decisions, mapped through one logistic curve.

What pushed it up

• Statistics nobody measured +13 — Round, unsourced, and identical across thousands of sites. Nobody measured any of it.
• shadcn/ui class signatures +12 — 33 shadcn/ui utility signatures in the markup.
• hover:scale-105 on everything +9 — 4 elements grow when you look at them.
• Cards inside cards +8 — 2 card surfaces sitting inside other card surfaces. Everything gets a box, everything gets equal emphasis, and nothing reads as primary.
• Exactly three feature cards in a row +8 — Features arrive in threes, as tradition demands — regardless of how many things the product actually does.
• Fixed pixel widths that will overflow a phone +8 — Hard pixel widths wider than a phone. Layouts break at sizes nobody prompted for, because desktop was the only viewport that got looked at.
• Backdrop blur everywhere +7 — 48 blurred surfaces.
• Everything centred +7 — 15 centred blocks. Long centred text is measurably harder to read, and with no left-aligned anchor the hierarchy flattens.

What pulled it down

• Deliberate social preview −9 — Open Graph title and image were both authored.
• prefers-reduced-motion honoured −8 — Motion preferences are respected in inline styles.
• Hand-written ARIA −7 — 63 explicit accessibility attributes.
• Structured data −6 — JSON-LD is present — somebody thought about search.
• Semantic landmarks −6 — 5 landmark elements instead of a pile of divs.
• CSS custom property system −6 — 469 CSS custom properties — a real token layer.
• Canonical URL −4 — Canonical link is set.

Craft we looked for and did not find

These are the actionable half of the report. None of them are hard, and every one of them would have moved the number.

• Skip-to-content link
• Self-hosted typography
• Hand-authored stylesheet
• No utility-class soup

What this scan cannot see

One request, no JavaScript executed. So everything below is invisible to us, and a page can be excellent or awful at all of it without moving the score:

• Domain registration age — needs WHOIS.
• Whether the nav's /about and /pricing actually resolve — needs a crawl, not one fetch.
• package.json dependency count, orphaned code, clashing abstractions, test coverage — needs the repo.
• Backend security shortcuts: string-built SQL, verify=False, missing auth on endpoints — needs the source.
• Whether row-level security or Firebase rules are actually switched on — needs the project.
• Console errors, hydration warnings and runtime 404s — needs a browser executing the page.
• Real Lighthouse numbers and horizontal scroll at 375px — needs a rendered viewport.
• Whether a JS-handled form posts anywhere — needs a submitted request.