Does accessiBe slow down a store?
In 7IT’s test of 367 US online stores, accessiBe ran on 36 of them (9.8%). On the median store that loads it, it downloaded 237 KB and kept the phone busy for 0.16 s before the page could respond.
9.8%of 367 US stores run it
237 KBmedian download on stores that load it
0.16 smedian time the phone spends running it
Stores with it and without it.
| Stores | Median score | Main content | Blocking time | Apps on the page | |
|---|---|---|---|---|---|
| With accessiBe | 36 | 34 | 11.9 s | 1066 ms | 20 |
| Without | 331 | 34 | 11.6 s | 1312 ms | 20 |
Stores that run accessiBe had a median score of 34, against 34 for stores without it. App counts are similar on both sides (20 and 20), so the comparison is fairer than most. On this sample there is no score penalty that can be pinned on it.
One in four stores that load it download more than 241 KB of it, and spend more than 0.20 s running it. Median Google phone-lab results, home pages only, September 2026. Method and limits in the study.
If you run accessiBe.
- Accessibility overlays add a large script to every page and do not make a site accessible on their own. Fix accessibility in the theme and code instead: labels, contrast, focus, alt text.
- If it must stay, load it after the page is interactive.