-
Notifications
You must be signed in to change notification settings - Fork 9
Large assets #92
Comments
I moved the CSS to a separate file and minified it, so it is now slightly better:
|
Are the seven icons in the menu the only place where Font Awesome is used? If this is the case, we could replace Font Awesome with seven small svg files or include them as inline svg in a css file. |
It is used in the menu, but also on markers (with Leaflet.awesome-markers). But yes, we only use a small number of icons, so we should either replace them or only extract the icons we need from FontAwesome. |
I used fontmin-webpack to only keep the icons we are actually using. Now the only remaining problem is that |
Did you already gzip this file? https://css-tricks.com/snippets/htaccess/active-gzip-compression/ |
Yes it is served gzipped, which means only ~180 KB are transferred to the browser instead of the full ~700 KB. |
I tried to optimize
fa-solid-900.svg
with image-webpack-loader but it is still quite large.As for the JS bundles, we probably need to split them in smaller bundles.
The text was updated successfully, but these errors were encountered: