Standards
Website quality standards:
the numbers we build to.
The targets Altruvex builds to - speed, accessibility, security and code quality - and how each one is measured.
01 / 04
Largest Contentful Paint (LCP)Under 2.5 s
Performance: Core Web Vitals
Speed is decided by the architecture, not by a late optimisation pass. Pages are served from a global edge network, images in modern formats, with only the JavaScript a page needs - all chosen before the first screen is built. Each threshold below is a target measured on a mobile profile.
Edge deliveryModern image formatsMinimal JavaScriptOptimised fonts
- Lighthouse performance score95 or higher
- Cumulative Layout Shift (CLS)Under 0.1
02 / 04
Text contrast ratio4.5:1 or higher
Accessibility: WCAG 2.1 AA
If it is not accessible, it is not finished. WCAG 2.1 AA is the target from the first screen. Keyboard navigation, screen reader output and colour contrast are part of how each screen is built, not a pass added at the end.
Semantic HTMLWCAG 2.1 AA complianceKeyboard accessibilityScreen reader supportReduced-motion support
- Lighthouse accessibility score95 or higher
- ARIA errorsNone allowed
03 / 04
Security headers gradeGrade A or higher
Security
Security headers, input sanitisation and dependency audits are part of the build, not an afterthought. Authentication flows are built against current OWASP guidance. For stores and systems that take payments, this is the baseline.
CSP headersSecure authenticationSanitized inputsDependency audits
- High-risk CVEs in dependenciesNone allowed
- Dependency auditPart of the build
04 / 04
Lint errorsNone allowed
Code quality
Your codebase is written for the next developer who opens it. Strict TypeScript catches a class of bugs manual testing misses, and a component-based structure lets a new developer trace a feature from route to page. The code you receive at handover is the code your next hire extends.
Strict TypeScriptComponent-based architectureZero lint errorsDocumented API endpoints
- Type errorsNone allowed
- API endpoints documentedEvery endpoint
Measured
Measured on
our own shipped work.
Lighthouse results for live sites we built, taken on the date shown. Nothing here is estimated.
| Site | Performance | Accessibility | Best practices | SEO | LCP | CLS | TBT |
|---|---|---|---|---|---|---|---|
| Altruvex | 97 | 100 | 96 | 92 | 2,376 ms | 0 | 3 ms |
| Art Lighting | 84 | 86 | 93 | 91 | 4,134 ms | 0 | 20 ms |
· Lighthouse 12.8.2 (mobile, simulated throttling)
On this site
12 checks.
The targets we build to, and the checks this site runs on itself.
These are the targets Altruvex builds to. This site's own repository runs an automated version on every push and pull request: lint, type check, pricing validation, tests with a coverage threshold on the tested libraries, a production build and Lighthouse. Accessibility below 95 or SEO below 90 fails the run; performance is measured and reported.
Next step
Hold your current site to these numbers.
The technical audit measures an existing site against the same four benchmarks and returns a written list of what fails and why, before any rebuild is on the table.