Worked examples wikipedia.org
Is wikipedia.org vibe coded?
Built to be read, on any device, forever. 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.
www.wikipedia.org
Hand-written
Somebody sat down and made decisions. Several of them were opinions.
- Vibe tells
- 1
- Craft tells
- 3
- Confidence
- medium
Enough signal to have an opinion.
Where the score came from
- Platform fingerprintsnone
Artefacts of the tool, not of taste
- Colour, type and surfacenone
The visual defaults, applied unedited
- Layout and architecture1 hit
The shape a page takes when nobody asks what it needs to say
- Copy tellsnone
How the words were written
- Leftoversnone
Scaffolding never cleaned up
- Source and buildnone
What is visible in the shipped code
- How it behavesnone
Weight, mobile, accessibility, SEO — where the money leaks
- Human craft3 hits
Evidence of deliberate decisions
Evidence
4 findings- −9
Deliberate social preview
Open Graph title and image were both authored.
- +7
Everything centred
17 centred blocks. Long centred text is measurably harder to read, and with no left-aligned anchor the hierarchy flattens.
- −7
No utility-class soup
Not one Tailwind utility class in the markup.
- −6
CSS custom property system
483 CSS custom properties — a real token layer.
What we read
- title
- Wikipedia
- generator
- —
- server
- ATS/9.2.15
- status
- 200
- html
- 117.5 KB
- words
- 867
- fetched in
- 622 ms
Reading this score
wikipedia.org landed on 8/100, which puts it in the hand-written band. That number is not a percentage and not a probability — it is strength of evidence: 4 points of tells, damped by craft, less 22 points of deliberate decisions, mapped through one logistic curve.
What pushed it up
- Everything centred +7 — 17 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.
- No utility-class soup −7 — Not one Tailwind utility class in the markup.
- CSS custom property system −6 — 483 CSS custom properties — a real token layer.
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-written ARIA
- Semantic landmarks
- Self-hosted typography
- Hand-authored stylesheet
- Canonical URL
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.