My mobile browser lag disappeared after I toggled these buried Chrome settings

by · Android Police

Google Chrome may offer the fastest performance of any Android browser on paper, but it doesn't always feel that way. Slow page loading, stuttering animations, and unresponsive interactions are hallmarks of the browser.

Add Android Police on Google Add as Preferred Source

Then there's the battery problem. Chrome can use up hours of battery life, but it doesn't have to be this way. Here's how I created a lag-free Chrome browsing experience that doesn't kill my battery life.

Related

I switched from Chrome to Firefox on Android; extensions are the reason I'm staying

Chrome on mobile doesn't need to be this bad

Posts 2
By  Jon Gilbert

Preloading pages slowed Chrome down and drained my phone's battery

But it isn't a guaranteed fix

Chrome's Preload pages setting tries to predict which web pages you visit most and loads them before you open them.

For example, I usually check the news through my mobile browser, not an app. So when I open Chrome, it preloads my most-visited website.

When I open that website, it loads instantly. At least, on paper.

In practice, I found that this led to a severe slowdown when I opened Chrome. After a few minutes, it returned to the speed I expected, but until then I encountered a much slower browsing experience than I expected.

If I used my phone for extended browsing sessions, I would consider the feature worthwhile. However, I don't normally use Chrome for more than a few minutes at a time.

Then there was the battery problem. After I turned Preload pages off, I noticed that I had gained almost an hour of extra battery life on my Google Pixel 10 Pro.

For extended browsing sessions on Chrome, keep Preload pages on. But to improve the app's opening speed and save battery life, turn it off.

GPU rasterization can dramatically improve page loading speeds

Always monitor performance after toggling this setting on older devices

I discovered the GPU rasterization feature when setting up my MacBook Neo. I was experiencing abnormally slow page loads, and after some research, I found the culprit.

On most devices, Chrome uses the CPU to turn website information into textures, then sends them to the GPU to display as pixels on the screen. This process is called rasterization.

I found that, likely due to poor optimization in Chrome, my MacBook Neo's CPU couldn't handle the rasterization process.

I fixed this problem by forcing the laptop to use its GPU for the entire process. It turns out that this wasn't an Apple-exclusive problem.

I tested GPU rasterization on every other device I owned that could run Chrome. Whether it was my Windows PC, Chromebook, Pixel phone, or Samsung tablet, enabling GPU rasterization dramatically improved Chrome's performance.

This feature is found in Chrome's secret settings menu:

  1. Enter chrome://flags in the address bar.
  2. Search for razteriz.
  3. Toggle the GPU rasterization setting to Enabled.

  4. Toggle the Zero-copy rasterizer setting to Enabled.

This final step lets Chrome send data to the GPU rather than writing it to memory first. This small change further improves performance and battery life.

A regular cache clearout returns Chrome to working order

Don't save data Chrome doesn't need

Every Android app stores temporary data that can help speed up loading times. However, over time, this data cache fills with unnecessary data.

Chrome uses cached data to speed up page loading times. However, it also stores data from websites you visited only once.

Clearing this cache doesn't delete user data like login details. Some websites may take a little longer to load the first time after you clear the cache, but overall Chrome should run faster.

This process also saves storage space. In the three months since I last cleared its cache, Chrome had saved 622MB of data it didn't need.

Chrome has an internal setting to clear cached data, but it's better to clear it using your Android phone's Settings app.

To clear Chrome's cached data, go to Android's Settings app.

  1. Open the Settings app.
  2. Search for Chrome.
  3. Tap Storage and cache.

  4. Tap Clear cache.

Check that the Experimental QUIC protocol is enabled

This hidden setting is vital for sites with heavy web traffic

QUIC is an experimental protocol developed as an alternative to TCP, HTTP/2, and TLS/SSL. It speeds up browsing by skipping the need for a response from servers.

QUIC's biggest disadvantage is that it makes network and traffic issues harder to troubleshoot while using the protocol. However, this isn't a concern for anyone who doesn't handle network admin tasks.

Like GPU rasterization, QUIC is also found in the chrome://flags menu. Search for Experimental QUIC protocol and toggle it to Enabled.

No Chrome setting is universally useful

After making any of the changes I recommend in this article, keep a careful eye on performance and consider how you use Chrome.

For example, if you use Chrome for extended periods, you may want to keep Preloading pages enabled.

I recommend making changes one at a time so you can easily identify where problems come from.