| > Can there be a way the browsers do that on download as a step rather than expecting every website owner to do it. Browsers perform far more downloads than site admins do uploads/pushes, so it makes sense to do it on the server. Especially since these approaches are reasonably heavyweight, unlike e.g. gzip or SSL, which browsers already spend time running. I suppose the frustration is that the majority of sites won't implement this (just statistically; nothing against the projects!), and the same can be said of many other technologies (e.g. Google's pagespeed server plugins). I can see two ways to get the most 'bang for your buck' in this sense: - Run these techniques in a caching proxy, like squid, and point your browsers at that. This way, you can get the boost yourself, without imposing it on others; plus it's cached and shared across browsers/machines. - Encourage commonly-used Web site infrastructure, like WordPress, Drupal, Apache, etc. to implement these things as seamlessly as possible (e.g. an admin page tickbox), and update/comment-on/etc. popular guides and tutorials for these programs to mention that these options exist. In fact, there's probably much more low-hanging fruit to be had by optimising popular CMSs in general (especially popular themes!) |