-
Notifications
You must be signed in to change notification settings - Fork 779
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Axe-core file size #2357
Comments
I've discussed this with @dylanb, he is on board with introducing the size budget. To address this, I propose we do the following:
To reach the size budget, we may decide to create a new .js file from which deprecated features and polyfills are removed. This will be a one-time thing, features deprecated after this file is introduced will be included to avoid breaking changes. We are looking for input on what would be a preferable maximum GZipped file size for axe-core. |
I propose we should aim for axe-core to be no larger than 100kB gippzed. |
Note: I tried switching to terser and didn't see any improvement to our minified / gzip file size using the same options as uglify. |
I'm going to call this done. Axe-core went down from 138k in 4.0 to 108kb in 4.1. We'll still have to define a size budget as per #1930. Pushing that one out to the 4.2 release. |
Below is a table of the sizes of
axe.min.js
for the last few releases since v3.0.If we were to release axe-core v4.0 today (which is not feature complete), we would add ~160 kB (~30 kB gzipped) to the minified file size over v3.4.1 which broke Lighthouses budget when they tried to update to it. From v3.5.0, that's an increase of ~90 kb (~12 kB gzipped).
Once v4.0 is feature complete, we will probably add another another 5 kB gzipped (just a guess). What this means is we've doubled the size of axe-core since releasing the last major release v3.0.
We should figure out some way to at least slow our rate of file size increase, if not figure out a max size we want the library to be.
The text was updated successfully, but these errors were encountered: