If you wanted to use the compression proxy that Google introduced in mobile versions of Chrome some time ago on the desktop, you had to use a third-party extension until now to do so. The extension enabled the compression proxy on desktop versions of Chrome so that you could use it to speed up your Internet browsing by redirecting it through Google servers.
The system compresses data, images and textual contents for example before they are sent to the browser which speeds up the loading time of websites thanks to the reduced size of the data.
The concept itself is not entirely new though as Opera Software has been using Opera Turbo in its desktop browser and mobile clients for years.
Today, Google released Data Saver to the Chrome Web Store. It implements the data compression technology for desktop Chrome in similar fashion as the third-party extension Data Compression Proxy does.
Google labels the extension beta currently. While that is the case, I did not notice any issues while using it. Having said that, I only had the chance to test the extension for a short period of time. Google notes on this help page that users may experience issues when Data Saver is enabled. This includes issues locating the user, image fuzziness or internal sites that may not load properly because of it.
Data Saver adds a button to Chrome's address bar that you can click on to display information about the compression. The proxy is enabled by default which means that all connections that you make from that moment on use it except for two.
Chrome won't use the proxy for HTTPS connections or websites opened in the browser's Incognito Mode (private browsing).
The interface of the extension displays a graph highlighting the saved bandwidth over time. There you also find listed how effective the compression technology was in reducing the transferred data size, and an option to turn the feature off.
The official extension has no whitelist currently unlike the third-party extension Data Compression Proxy. A whitelist can be useful as it allows you to block the proxy from running on specific sites, for instance on sites where its use causes issues on.
Since both use the same technology, you should not see much of a difference when comparing their effectiveness.
Google's extension is less flexible than the third-party extension. While that may not be a problem for all users, as you can disable the compression if you need to access sites were it causes issues on, a whitelist is certainly the comfortable solution. Still, there is a chance that Google will introduce this option in a future update.
As far as gains are concerned, they can be huge depending on what you do on the Internet. While you won't see a difference when watching videos, you may experience faster loading times on many websites thanks to the compression technology used.
Privacy is a concern obviously as you route most of your traffic through Google servers with the proxy enabled.
Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.
We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats (video ads) or subscription fees.
If you like our content, and would like to help, please consider making a contribution:
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.