Worked examples replit.com
Is replit.com vibe coded?
An IDE that became a site builder. 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.
replit.com
Hand-written
Somebody sat down and made decisions. Several of them were opinions.
- Vibe tells
- 3
- Craft tells
- 6
- 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 tells1 hit
How the words were written
- Leftoversnone
Scaffolding never cleaned up
- Source and build1 hit
What is visible in the shipped code
- How it behavesnone
Weight, mobile, accessibility, SEO — where the money leaks
- Human craft6 hits
Evidence of deliberate decisions
Evidence
9 findings- +14
Replit fingerprints
Replit hosting artifacts are shipping with the page.
- −9
Deliberate social preview
Open Graph title and image were both authored.
- +8
Dependency sprawl
0 third-party asset hosts and 113 script files. Each sub-problem got whatever library was most popular in the training data, and nothing was ever consolidated.
- −7
Hand-written ARIA
18 explicit accessibility attributes.
- −7
Self-hosted typography
Fonts are self-hosted rather than pulled off a CDN.
- +6
The rule-of-three cadence
8 triplet lists and 0 “not just X — it's Y” constructions. Rhythm borrowed from marketing prose, with none of the content.
What we read
- title
- Replit – Build apps and sites with AI - Replit
- generator
- —
- server
- cloudflare
- status
- 200
- html
- 627.4 KB
- words
- 1,425
- fetched in
- 150 ms
Reading this score
replit.com landed on 9/100, which puts it in the hand-written band. That number is not a percentage and not a probability — it is strength of evidence: 24 points of tells, damped by craft, less 39 points of deliberate decisions, mapped through one logistic curve.
What pushed it up
- Replit fingerprints +14 — Replit hosting artifacts are shipping with the page.
- Dependency sprawl +8 — 0 third-party asset hosts and 113 script files. Each sub-problem got whatever library was most popular in the training data, and nothing was ever consolidated.
- The rule-of-three cadence +6 — 8 triplet lists and 0 “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.
- Hand-written ARIA −7 — 18 explicit accessibility attributes.
- Self-hosted typography −7 — Fonts are self-hosted rather than pulled off a CDN.
- Semantic landmarks −6 — 4 landmark elements instead of a pile of divs.
- CSS custom property system −6 — 2409 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.
- Structured data
- Skip-to-content link
- prefers-reduced-motion honoured
- 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.