Is lovable.dev vibe coded?

Reading this score

lovable.dev landed on 21/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: 52 points of tells, damped by craft, less 41 points of deliberate decisions, mapped through one logistic curve.

What pushed it up

• Lovable fingerprints +24 — The page loads assets from Lovable's own domain. That is where a Lovable build serves from, but it is also what linking to the product looks like.
• Gradient clipped headline text +13 — The headline is a gradient clipped to text. It was a flourish; it became a reflex.
• Glowing orbs behind a permanently dark page +8 — 29 glow surfaces over a permanently dark ground. Learned from crypto and AI launch pages, where it was atmosphere. Here it decorates nothing.
• 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.
• The rule-of-three cadence +6 — 6 triplet lists and 0 “not just X — it's Y” constructions. Rhythm borrowed from marketing prose, with none of the content.
• Spacing that doesn't keep time +5 — 5 different vertical rhythms across 6 sections, because each one was generated in its own prompt. The page reads as unfinished even to people who can't say why.
• A bento grid because bento grids exist +5 — Asymmetric tiles used as a style rather than because some tiles matter more. If shuffling them changes nothing, the grid is decoration.

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.
• Hand-written ARIA −7 — 25 explicit accessibility attributes.
• Structured data −6 — JSON-LD is present — somebody thought about search.
• Semantic landmarks −6 — 4 landmark elements instead of a pile of divs.
• 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.

• prefers-reduced-motion honoured
• Self-hosted typography
• CSS custom property system
• 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.