Is webflow.io vibe coded?

Reading this score

webflow.io landed on 23/100, which puts it in the human, ai-assisted band. That number is not a percentage and not a probability — it is strength of evidence: 70 points of tells, damped by craft, less 55 points of deliberate decisions, mapped through one logistic curve.

What pushed it up

• Large language model house style +16 — 2 stock LLM marketing phrases.
• Gradient clipped headline text +13 — The headline is a gradient clipped to text. It was a flourish; it became a reflex.
• Statistics nobody measured +13 — Round, unsourced, and identical across thousands of sites. Nobody measured any of it.
• The standard landing page skeleton +12 — 5 of the seven stock sections are present. Hero, logo bar, three features, stats, testimonials, pricing, FAQ, CTA, footer — every section present, none earning its place.
• Links that go nowhere +10 — 26 anchors point at href="#".
• Glowing orbs behind a permanently dark page +8 — 2 glow surfaces over a permanently dark ground. Learned from crypto and AI launch pages, where it was atmosphere. Here it decorates nothing.
• Comments explaining the obvious +8 — Humans comment where the logic is surprising. Models comment everywhere.
• Dependency sprawl +8 — 12 third-party asset hosts and 19 script files. Each sub-problem got whatever library was most popular in the training data, and nothing was ever consolidated.

What pulled it down

• Deliberate social preview −9 — Open Graph title and image were both authored.
• Skip-to-content link −9 — A keyboard skip link exists. Generators do not do this.
• prefers-reduced-motion honoured −8 — Motion preferences are respected in inline styles.
• Hand-written ARIA −7 — 150 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 — 43 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.

• 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.