We have made the switch to SPDY and when HTTP/2 is available for more browsers will start using that too. One of the pro:s of using HTTP/2 is that combining/concatenating assets is not needed anymore (the browser can download many assets from the same domain at the same time). And that will open the possibility for all small CSS/JS file to have individual cache times and in best case, only re-cache them when they are changed.
There's a lot that needs to be done and analyzed to make that happened but first start look at this example where we access the Wikipedia Facebook page first with an empty cache and then pre-populated with the Main_Page.
- By stop concatenating assets, will we kill the performance for browsers using HTTP1.1? How many users will be affected? And what will the effect be? Is there away way to minimize the loss?
- What kind of positive effect will we see (speed, bytes, requests)
- Is the Main_Page test a good example or should we pre-populate the cache by another page?
- How much work is it in the backend to change the resource loader and what needs to be done to be able to cache assets longer?