A haircut chain beats every developer tool here
greatclips.com and rotorooter.com both score 92 — higher than stripe.com (85), vercel.com (88) and github.com (78). Sites built to be found by customers tend to do the boring things well.
Benchmarks
Measured on 2026-07-31. The analyzer is deterministic — it reads the page a visitor receives and applies fixed rules — so you can paste any host below into the free audit and get the same number back. That is the point of publishing it.
greatclips.com and rotorooter.com both score 92 — higher than stripe.com (85), vercel.com (88) and github.com (78). Sites built to be found by customers tend to do the boring things well.
franklinbbq.com and github.com both score 78. A Texas barbecue joint and the largest code host on earth, on the same 28 checks.
danluu.com scores 47, the lowest in the corpus, and it is one of the most widely read engineering blogs there is. The audit measures what a page gives a visitor and a crawler, not whether the writing is worth reading.
| # | Website | Score | Band |
|---|---|---|---|
| 01 | greatclips.com | 92 | Strong |
| 02 | rotorooter.com | 92 | Strong |
| 03 | sive.rs | 90 | Strong |
| 04 | mrhandyman.com | 88 | Strong |
| 05 | vercel.com | 88 | Strong |
| 06 | jiffylube.com | 86 | Strong |
| 07 | midas.com | 86 | Strong |
| 08 | mozilla.org | 86 | Strong |
| 09 | sweetgreen.com | 86 | Strong |
| 10 | go.dev | 85 | Strong |
| 11 | shopify.com | 85 | Strong |
| 12 | stripe.com | 85 | Strong |
| 13 | basecamp.com | 83 | Strong |
| 14 | netlify.com | 83 | Strong |
| 15 | nodejs.org | 83 | Strong |
| 16 | python.org | 83 | Strong |
| 17 | cloudflare.com | 80 | Strong |
| 18 | gusfriedchicken.com | 80 | Strong |
| 19 | franklinbbq.com | 78 | Promising |
| 20 | github.com | 78 | Promising |
| 21 | kentcdodds.com | 76 | Promising |
| 22 | linear.app | 76 | Promising |
| 23 | pikeplacefish.com | 75 | Promising |
| 24 | rust-lang.org | 75 | Promising |
| 25 | katzsdelicatessen.com | 69 | Promising |
| 26 | airbnb.com | 66 | Promising |
| 27 | jvns.ca | 66 | Promising |
| 28 | overreacted.io | 66 | Promising |
| 29 | simonwillison.net | 66 | Promising |
| 30 | magnoliabakery.com | 64 | Promising |
| 31 | hattieb.com | 63 | Promising |
| 32 | news.ycombinator.com | 61 | Promising |
| 33 | wikipedia.org | 61 | Promising |
| 34 | tailwindcss.com | 56 | Promising |
| 35 | tartinebakery.com | 54 | Needs work |
| 36 | danluu.com | 47 | Needs work |
Each site is fetched once, as a browser would, and the returned HTML is checked against 28 fixed rules across performance readiness, structure, trust signals, discoverability and mobile handling. The score is simply the proportion that passed. There is no model and no opinion in it.
Because the rules are fixed, two people auditing the same page get the same score. That is what makes these numbers checkable rather than merely stated — and it is why every finding in a report quotes the evidence it was based on, so you can search for it in your own source.
Scores drift as sites are rebuilt, which is why the measurement date ships alongside the data. A score here is a reading taken on 2026-07-31, not a permanent property of the site.
A high score does not mean a site is beautiful, useful or successful, and a low one does not mean the opposite. It measures what the page hands a visitor and a crawler on arrival — nothing more.
Same 28 checks, same scoring, no account and no email. It takes a few seconds.
Audit a website