Learn · Position
Why a public score
A score is a contract you can run.
The /score engine is not a marketing widget. It is a verifier that returns the same letter grade for any URL, including the one it lives on. This article is the short version of why we made that choice — and what it costs.
The four reasons
A private score is not a score
A score kept inside a tool, a team, or a vendor dashboard is a metric. A score that anyone can run against any URL — including the one that published the score — is a contract. The first one can drift; the second one cannot.
The same checks grade everyone
The 23-check engine that scores your site scores designesy.org. The same thresholds. The same letter grade. The same honest SKIPs when a browser path is not enabled. If we ever fail our own contract, the score says so on the same surface.
A grade is comparable; a diff is not
Visual regression returns a pixel delta that only means something against a baseline. A letter grade returns a number that means the same thing at nike.com, stripe.com, and designesy.org. Comparability is the whole point of a public score.
It forces the contract to be publishable
You cannot publish a score against a contract you cannot publish. The score is downstream of the contract. Making the score public required making the contract public first — which is the larger commitment the score is a proxy for.
What it costs
We give up
We get
The honest SKIP
Transparency rule
When the engine cannot run a check — when a browser path is not enabled on the deployment, or when a public API quota is exhausted — it returns a SKIP with a diagnostic string. It does not silently pass. A public score that hides its gaps is worse than no score.
This is why the audit endpoint returns honest SKIPs until env vars are set, and why the static score never claims a check it did not run. The grade is only as good as the visibility behind it.