
Lighthouse 100 isn't a flex, it's a commitment
Author
Zdeny
Date Published
“We've got a green Lighthouse” sounds like a marketing line. For us it's a hard CI gate — a pull request that drops the score below the minimum simply doesn't get merged. Here's why we take it this seriously.
Accessibility 100 is a moral commitment
Performance can be justified by business: a faster site means more conversions. Accessibility is a different league. When a site isn't accessible, you exclude people with visual, motor, or cognitive impairments. That's not a technical trade-off — it's an ethical decision.
Accessibility 100 always, no exceptions. If a change makes accessibility worse, we don't do it — no matter how good it looks.
Core Web Vitals in the green zone
LCP under 2 seconds, INP under 200 ms, CLS under 0.1. We don't measure these metrics once before launch — we track them in real operation (RUM) at the p75 percentile, because what matters is the experience of real users, not a lab ideal.

How we enforce it
The performance budget is part of the build. Initial JS bundle under 150 KB, hard limit. Fonts self-hosted via WOFF2. Images AVIF first, WebP fallback. And on top of it all, Lighthouse CI watching every merge.
It isn't a flex. It's a commitment we make to every client — and one we can back up with a number, not promises.

Upřímný pohled na to, proč jsme po pěti letech opustili WordPress a postavili vlastní Engine. Rychlost, bezpečnost a vlastnictví kódu.

Connection storms, cold starts, Jobs Queue. Three technical reasons why we chose Railway over Vercel for Payload CMS.
