Using cost-effective bandwidth is everyone’s desire, hosts look forward to lesser bills, mobile users don’t want to go above their limits and no one looks forward to needless bytes. The good thing is that the web is jam-packed with opportunities which are designed to save bandwidth namely, pages served without gzip, stylesheets and JavaScript served unminified and unoptimized images.

While the web is full of the above opportunities, the question is why isn’t it already optimized for bandwidth? And if these savings are good for everyone why haven’t they been employed yet? As such, web designers should “save for web” in the course exporting their artwork but sad to point out that most of them don’t always remember that.

Another easy resolution for web users is to make use of an optimizing proxy, such as Chrome’s; when a user selects this service, their HTTP traffic will go via Google’s proxy, which optimizes their page loads and cuts bandwidth usage by 50%. This is a good initiative for users but sad in the sense that it’s limited to people who are using Chrome who turn the feature on thereby failing to optimize HTTPS traffic.

Everyone will benefit through Optimize for Bandwidth and these include users of other browsers, secure sites, desktop users, and site owners who want to bring down their outbound traffic bills.
Simply put in the PageSpeed module on your Apache or Nginx server and activate Optimize for Bandwidth in your configuration. PageSpeed will perform the rest the moment you are done.