Worked examples base44.com
Is base44.com vibe coded?
One of the newer entrants, and one we fingerprint directly. We fetched the homepage on 29 August 2026 and ran all 86 detectors over the raw HTML — the same scan you get from the box on the front page, frozen here so the numbers can be argued with.
base44.com
Shipped straight from the chat window
This went from prompt to production without stopping to look around.
- Vibe tells
- 4
- Craft tells
- 7
- Confidence
- high
Plenty of signal to work with.
Where the score came from
- Platform fingerprints1 hit
Artefacts of the tool, not of taste
- Colour, type and surfacenone
The visual defaults, applied unedited
- Layout and architecturenone
The shape a page takes when nobody asks what it needs to say
- Copy tells2 hits
How the words were written
- Leftoversnone
Scaffolding never cleaned up
- Source and buildnone
What is visible in the shipped code
- How it behaves1 hit
Weight, mobile, accessibility, SEO — where the money leaks
- Human craft7 hits
Evidence of deliberate decisions
Evidence
11 findings- +24
Base44 SDK wired to the page
The Base44 SDK is talking to Base44's backend straight from the browser.
- −9
Deliberate social preview
Open Graph title and image were both authored.
- +8
Em dash density
33 em dashes across 9162 characters (3.6 per 1k).
- +8
Fixed pixel widths that will overflow a phone
Hard pixel widths wider than a phone. Layouts break at sizes nobody prompted for, because desktop was the only viewport that got looked at.
- width: 767px
- min-width: 768px
- width: 1099px
- min-width: 1100px
- −8
prefers-reduced-motion honoured
Motion preferences are respected in inline styles.
- −7
Hand-written ARIA
38 explicit accessibility attributes.
What we read
- title
- Vibe Coding Platform for Building Apps and Websites | Base44
- generator
- —
- server
- cloudflare
- status
- 200
- html
- 179.9 KB
- words
- 1,533
- fetched in
- 391 ms
Reading this score
base44.com landed on 82/100, which puts it in the shipped straight from the chat window band. That number is not a percentage and not a probability — it is strength of evidence: 38 points of tells, damped by craft, less 47 points of deliberate decisions, mapped through one logistic curve.
What pushed it up
- Base44 SDK wired to the page +24 — The Base44 SDK is talking to Base44's backend straight from the browser.
- Em dash density +8 — 33 em dashes across 9162 characters (3.6 per 1k).
- 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 — 7 triplet lists and 1 “not just X — it's Y” constructions. Rhythm borrowed from marketing prose, with none of the content.
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 — 38 explicit accessibility attributes.
- Self-hosted typography −7 — Fonts are self-hosted rather than pulled off a CDN.
- Structured data −6 — JSON-LD is present — somebody thought about search.
- Semantic landmarks −6 — 6 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.
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.