Worked examples berkshirehathaway.com
Is berkshirehathaway.com vibe coded?
Untouched since the nineties, and entirely deliberate about it. 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.
berkshirehathaway.com
Hand-written
Somebody sat down and made decisions. Several of them were opinions.
- Vibe tells
- 0
- Craft tells
- 1
- Confidence
- low
Thin page. Treat this as a shrug.
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 architecturenone
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 craft1 hit
Evidence of deliberate decisions
Evidence
1 findings- −7
No utility-class soup
Not one Tailwind utility class in the markup.
What we read
- title
- BERKSHIRE HATHAWAY INC.
- generator
- MSHTML 8.00.6001.18828
- server
- Sucuri/Cloudproxy
- status
- 200
- html
- 5.4 KB
- words
- 186
- fetched in
- 451 ms
Reading this score
berkshirehathaway.com landed on 12/100, which puts it in the hand-written band. That number is not a percentage and not a probability — it is strength of evidence: 0 points of tells, damped by craft, less 7 points of deliberate decisions, mapped through one logistic curve.
Nothing pushed it up. Not one stack fingerprint, aesthetic default, copy tell or leftover fired on this page — which is rarer than it sounds.
What pulled it down
- No utility-class soup −7 — Not one Tailwind utility class in the markup.
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.
- Deliberate social preview
- Structured data
- Skip-to-content link
- prefers-reduced-motion honoured
- Hand-written ARIA
- Semantic landmarks
- Self-hosted typography
- CSS custom property system
- 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.