Diagnose on real-user data
Field data from Chrome UX Report and your own monitoring, split by device, network, and page. Fixes target the pages and visitors that miss, not the lab score.
Fast for everyone. Usable by everyone.
Core Web Vitals and WCAG 2.2 AA — diagnosed on real-user data, fixed in production, and locked in with CI budgets. Built for European Accessibility Act readiness.
Two halves, one engagement
Speed and access, fixed in your code.
Slow pages and inaccessible pages lose the same people: anyone not on a fast laptop with a mouse. We fix both in one pass.
Images, fonts, and scripts
Modern formats sized per breakpoint, subset fonts with tuned fallbacks, and third-party tags loaded after consent and content.
AVIFFont subsettingConsent-gated
Tested by people
Keyboard-only passes and screen-reader testing on NVDA, VoiceOver, and TalkBack. Scanners miss focus order, announcements, and meaning.
NVDAVoiceOverTalkBackKeyboard
WCAG 2.2 AA audits, fixes shipped
Every failure logged against its success criterion, then fixed in your repository through pull requests. Including the four AA criteria new in 2.2.
Budgets that fail the build
Lighthouse, bundle size, and automated accessibility checks run on every pull request. A change that breaks a budget does not merge.
European Accessibility Act readiness
The EAA has applied since 28 June 2025 to many consumer-facing digital services sold in the EU, including e-commerce. We map your obligations and close the gaps.
Performance
Measure real users, not the lab.
Google assesses the three Core Web Vitals — LCP, INP, and CLS — at the 75th percentile of real visits. A perfect Lighthouse score on a fast laptop says little about a mid-range phone on mobile data. We start from field data and fix what it shows.
- Real-user monitoring in place before the first fix, so every change is measured.
- Budgets per page type: a product page and a blog post need different limits.
- Cohorts by device, network, and country, because fixing the median can hide the tail.
- Lab tests in CI for regressions, field data in production for truth.
Accessibility
Test with a keyboard and a screen reader.
Automated scanners catch only part of WCAG. Whether a button’s label makes sense, whether focus lands in the right place, and whether a dialog traps the keyboard all need a person. We test the key flows by hand and fix what we find.
- Key flows tested end to end: sign-up, search, checkout, and account settings.
- Every issue logged with its WCAG criterion, severity, and the fix.
- Fixes shipped as pull requests in your repository, not left in a report.
- Automated checks added to CI so fixed issues stay fixed.
1.5 s
LCP budget we build to, at the 75th percentile
WCAG 2.2 AA
Standard every audit and fix is measured against
Every PR
Performance and accessibility checks before merge
By hand
Keyboard and screen-reader passes on every key flow
We had a long scanner report and no idea where to start. They fixed sign-up and checkout first, then added the checks that stop the same problems coming back.
Questions
What buyers ask us first.
Does the European Accessibility Act apply to us?
It covers many consumer-facing products and services sold in the EU, including e-commerce, banking, and e-books, and it has applied since 28 June 2025. Microenterprises providing services are exempt. We help you map your scope; for a legal opinion, involve your counsel.
Which standard do you audit against?
WCAG 2.2 level AA. The EAA’s harmonised standard, EN 301 549, currently references WCAG 2.1 AA, and 2.2 AA covers everything 2.1 AA asks for.
Can’t we install an accessibility overlay instead?
Overlays add a widget on top of the page without fixing the underlying code. Screen-reader and keyboard users still meet the same barriers. We fix the source.
Do you only report issues, or fix them too?
We fix them. Audit findings become pull requests in your repository, reviewed by your team, with tests that keep them fixed.
How is it priced?
An audit and fix sprint is quoted as a fixed scope after we see the site. Ongoing monitoring and fixes run as a monthly retainer.
Ready when you are
Send us a URL. We’ll show you where it’s slow and where it’s blocked.
A 30-minute call. We’ll run a field-data check and a keyboard pass on your top page while we talk.