One possible way of dealing with huge libraries on the client side is to create a preloader, a hyper-optimized tiny page with all the CSS/JS embedded (so one re

One possible way of dealing with huge libraries on the client side is to create a preloader, a hyper-optimized tiny page with all the CSS/JS embedded (so one request). It displays some basic progress bar and preloads all the JS / CSS / images / JSON your app needs. Then you start your actual framework, render and swap the load screen to your app. All of this creates an illusion of speed, and people are generally fine waiting, as long as they are shown the progress bar.