Chrome beta for Android review: Fast and furious

Chrome beta for Android review: Fast and furious

Summary: Google has done a good job with the Chrome browser on mobile platforms. The beta version rivals the desktop experience on Android and is lightning fast, which is shown on video.

Chrome ZDNet
Chrome beta for Android -- All images credit: James Kendrick/ZDNet

I am a strong supporter of the Chrome browser experience and use it on every platform and device I use. The Android version of Chrome is a good browser, and the beta version expands on that and is a superb mobile browser on Android.

Chrome for Android does a great job providing a desktop browsing experience with significant improvements. It is fully touch optimized and Google's attention to detail make using it on Android a good experience. It handles full web sites with ease, turning the mobile device into a portable desktop web browsing system. 

Chrome NYT

What sets it apart from the mobile browser field is the little touch optimizations that Google has incorporated into the app. The standard touch gestures are fully supported, e.g. pinch/zoom and double tap to expand a column. The way the top menu bar slides off the screen when scrolling down the page, and how nudging the page up brings it back, are completely natural on a mobile device.

Google made sure that Chrome for Android handles any size device, and flipping it between portrait and landscape orientation works very well on all of them. The most complicated, busy web sites can be viewed nicely even on phones.

As good as Chrome for Android has become, Google has a beta version of the browser where new features are tested. I recently installed it on both my Galaxy Note 2 phone and Note 8.0 tablet, and it is fantastic.

Chrome Techmeme

Super speed

The Chrome beta for Android has been out for a while but I held off installing it as there were serious known issues for both my devices. That's the risk of using beta software and you should use betas with caution. Fortunately, Google addressed the known issues with my phone and tablet in a major update earlier this month so I installed it on both a few days ago.

Not only have I experienced no issues with the current Chrome beta for Android, it is the fastest mobile browser I have ever used. Web pages load rapidly, rivaling and in some cases surpassing Chrome on the desktop. Simple web sites can load in a second, and sites that even load slowly on the desktop appear in just a few seconds.

This speed is largely attributable to two advanced settings in Chrome beta. One, which is available in the standard version of Chrome for Android, preloads web pages to speed things up. When you load a web page, Chrome searches for links on the page to sites that you might want to visit and loads them in the background. This happens with no noticeable impact on the browsing speed for the currently active web page. With pages loaded in the background, when you hit a link the new page often loads immediately. This has a tremendous impact on browsing.

The Chrome beta for Android also has a new setting that plays a big role in not only speeding up browsing, and can reduce your bandwidth on cellular connections. Located under the menu Settings | Advanced | Bandwidth Management | Reduce Data Usage, this can be activated by turning on the toggle switch at the top of the page.

Phone tabs
Tabs on a phone

According to the Chrome help, this setting causes web pages to be compressed by Google's servers before appearing on the local device so that pages load using less bandwidth. The purpose is to reduce data charges on mobile devices. From Google's help page:

The browser uses Google's servers to condense image file sizes and perform other optimizations to reduce bandwith consumed by the page. When you use this feature, Chrome also encrypts your browsing session and uses safe browsing technology to protect you from malware and phishing attacks. If you browse to a known malware or phishing site Chrome will warn you before you enter the site.

If this sounds like the Amazon Kindle Silk browser feature, it's because it works the same way. Some may be concerned about web pages being rendered on Google's servers but I have no problem with that. It's not like our online activities are really private anyway. It is something to think about before activating the feature.

With the setting enabled to reduce bandwitch usage, Chrome beta monitors the savings in bandwidth thanks to the compression. Mine currently reads a 17 percent reduction, even though I've been on wi-fi the entire time since installing the beta. Of course, this is Google's reporting so take that with a grain of salt.

What has surprised me is how this setting speeds up web browsing. I have tested disabling/enabling it a lot and it's clear to me that the data reduction has a noticeable impact on loading web pages. So far doing the compression on Google's servers does not impact browsing on the local device in any noticeable way. It's a marked improvement and I suggest giving it a try if you run the Chrome beta for Android.

There are a number of features in Chrome beta that are not in the standard version. Most notable are new tilt controls and the support for WebGL. You can find complete information from the Chromium web site.

You can install Chrome beta from Android from the Google Play Store. Note that it doesn't replace regular Chrome if installed on your device, allowing you to try it and get rid of the beta if you have problems. Again, this is beta software and while stable on my devices you may have problems.

I am impressed with the page loading speed of Chrome beta for Android. This is impossible to convey properly in an article like this, so this short video below demonstrates how fast web pages load in the beta.

See also:

Topics: Mobility, Android, Browser, Google, Reviews, Smartphones, Tablets

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • while i liked chrome on android

    it just seemed more sluggish than other browsers. My current favorite has been firefox for most uses, and opera for its 'off road' data compression mode. I will try chrome beta now.
    • yes it is fast

      mostly because of the data compression mode, as you mentioned. At my workplace, the wifi is extremely laggy. The chrome beta with compression mode on alleviates this condition quite well.
      • If it's only getting 17% compression then while it saves time and bandwidth

        for the current page it doesn't sound like it's enough bandwidth to outweigh the extra bandwidth wasted by the pre fetching of the linked pages that you're never going to look at. That could eat up your data plan right quick. Also uncompressing probably drains your battery quicker so there'd be a trade off there too.
        Johnny Vegas
        • some things to keep in mind, thanks

          But I doubt those things you mentioned will be of any practical issue for me. I don't browse that much on the phone anyway and I've only used over 2GB twice in the year I've had the data plan, due to being on vacation. Of course its unlimited anyway, so I don't care.
        • Speed isn't just from compression - it makes Google a CDN

          A lot of the speed comes from the way Google becomes a de facto CDN for a lot of static content from the websites you access -- same concept as Silk, where Amazon caches an image, then the next 1,000 users to access it get it right from Amazon's cache - but Google has edge servers really really optimized, to every major region of the world (even more so than Amazon, by some accts).
  • Boat Browser

    I've tried many android browsers..default best one is Boat browser (not boat mini). Why ?
    - It excels at scaling text to make it readable without having to wear reading glasses.
    - You can position the menu bar at the bottom of the screen which DRAMATICALLY reduces the need to reach with your arm to navigate.
    - The tool bar can be customized with various icons.
    - You can toggle full screen mode which hides the menu bar but preserves the toolbar for navigation.
    - When you do a strong vertical scroll , a button pops up to allow you to go directly to the bottom of the page if desired.

    Something that is missing from all browsers and android in general would be to have a button that you can push to page down EXACTLY one page/screen that would reduce the amount of scrolling that you have to do. It's a glaring omission in touch navigation.
    • button that you can push to page down EXACTLY one page/screen

      sure that would be a great feature, along with the arrow that opera has to shoot to the top or bottom while scrolling. I hope chrome adds that and text reflow.
  • chromes the best browser on android by far

    it goes in this order for my use on both my android phone and tablet and use them all daily
    1 chrome
    2 firefox
    3 opera
    4 my stock samsung browser
    5 maxathon
    6 next browser
    7 uc browser
    8 boat browser
  • And the URL is ...

    Shouldn't that have been in the article?
    I didn't have much luck finding this by searching the App store. Lots of things about Google Chrome Beta, some of which don't even seem vaguley related.
    The proper link was on one of the blogs you referenced.
    • for some reason chrome beta

      didn't show up in my phone's play store. I found it in the browser based store and just clicked 'install' there.
  • Must have a slow desktop.

    "The beta version rivals the desktop experience on Android"

    Must have a slow "desktop on Android."

    My desktop works great.

    And it just came out on Android? Wow. I've had it on an iPhone for a while. Curious that they put it on iPhone before they put it on their own Android.
    • Chrome Beta for Android has been around for years

      And the IOs version doesn't have all the bells and whistles that Android has.
  • Lacking Flash

    Disappointing in that respect, and might be on of the reasons my next tablet will have a Windows OS.
  • Uses unnecessary data

    The Chrome for Android Browser will use unnecessary data because it will ONLY start while loading the last page you visited. You can't define a homepage. You can't even define a blank start page. You can create a link that will start chrome on the page you want but it just loads the desired page in a new tab while loading the last page visited in the 1st tab. How many people REALLY want chrome to start on the last page visited in their History? I suspect not many and I can't imagine developing the browser to start on a blank page (or even the root of your bookmarks) any more difficult than reading the History and starting on a page from there.