dmmearns
posted this
17 August 2022
I tried UnCSS and PurgeCSS with the --safelist options listed by @cimperia and found that there were still problems with the menu bar, with the selected page not highlighted.
I was weighing up the reduction of nicepage.css from ~1.3MB to ~133kB against time to test and fix similar issues and started wondering what the outcome would be with gzip.
Turns out gzip reduced nicepage.css to ~110kB with a decompression time of 10ms on my machine. To me, that is a win, as it is good enough for my use cases and I don't have to worry about whether I've deleted classes that I actually need.
But still, Nicepage, it would be good to have a tree shaking feature to get rid of the unused code and compress further (to ~23kB!).
I tried UnCSS and PurgeCSS with the --safelist options listed by @cimperia and found that there were still problems with the menu bar, with the selected page not highlighted.
I was weighing up the reduction of nicepage.css from ~1.3MB to ~133kB against time to test and fix similar issues and started wondering what the outcome would be with gzip.
Turns out gzip reduced nicepage.css to ~110kB with a decompression time of 10ms on my machine. To me, that is a win, as it is good enough for my use cases and I don't have to worry about whether I've deleted classes that I actually need.
But still, Nicepage, it would be good to have a tree shaking feature to get rid of the unused code and compress further (to ~23kB!).