Chrome back and forward button performance to improve in 2020

Martin Brinkmann
Feb 28, 2019
Google Chrome
|
17

Google is working on a new cache for its Chrome browser to improve the performance of back and forward operations on the desktop and on mobile.

Called bfcache, short for back/forward cache, it is designed to cache pages in memory when users navigate to another page, e.g. by activating links, entering URLs manually, or through other means.

The cache will store a copy of the page the user left, including JavaScript and the DOM state, in order for Chrome to load it from memory when the user decides to use the back or forward button in the browser.

It is like putting pages into hibernation in memory to wake them up when the page is revisited during the session. Chrome will store a finite number of entries in the new cache, likely to avoid too big of an impact on the browser's memory use.

chrome back forward

Chrome caches content already so that the content loads faster than on first visit of a a page not visited previously.

The current implementation requires Chrome to parse and render the page again and perform other computations to display the page again to the user.

Basically, the only thing that really changes right now when accessing previously visited pages is that Chrome does not need to establish as many networking connections if cached content is available.

It may come as a surprise to some, but Chrome is trailing Firefox and Safari in this regard. The two web browsers support similar functionality, Mozilla even calls it bfcache as well, for over a decade.

Back and forward operations represent significant activity on the desktop and mobile according to Google; Google metrics indicate that desktop Chrome users revisit 10% of pages while mobile Chrome users 19%. Making back and forward operations faster is therefor beneficial to the user experience on desktop and on mobile.

Google published two videos that demonstrate the difference between the performance of back and forward buttons in current versions of Chrome and in prototypes that use an early version of bfcache already.

Google Chrome desktop

Google Chrome mobile

The bfcache speeds up the loading of already visited pages but it does not affect new pages visited in the browser.

Google says the implementation is not trivial as Google engineers will have to make major changes to Chrome's non-rendered process components, navigation stack, and handling of page-related tasks. Google notes that there is privacy to take into account as well.

Google aims for a 2020 release in the Stable version of the Chrome browser on desktop and on mobile. The company wants to limit the number of cache entries in the beginning and increase it gradually. One reason for that is likely that it wants to monitor the impact the feature has on memory use of the browser.

Now You: Do you use back and forward often in your browser?

Summary
Chrome back and forward button performance to improve in 2020
Article Name
Chrome back and forward button performance to improve in 2020
Description
Google is working on a new cache for its Chrome browser to improve the performance of back and forward operations on the desktop and on mobile.
Author
Publisher
Ghacks Technology News
Logo
Advertisement

Previous Post: «
Next Post: «

Comments

  1. John Fenderson said on March 1, 2019 at 7:26 pm
    Reply

    “Now You: Do you use back and forward often in your browser?”

    Yes, constantly!

  2. ULBoom said on March 1, 2019 at 2:50 pm
    Reply

    “Now You: Do you use back and forward often in your browser?”

    Well, yeah, always. If only a few chrome users utilize the back button, maybe those are the users who understand how the browser works!

    I suppose with that stupid omnibar flashing you whenever a character is entered, many users would click anything to make it stop. I’d be surprised if most users have explored chrome’s features vs. just taking what google says they want.

    My chromium goes back/forward through many pages without perceptible delay, so I don’t know what this is about beside today’s chromedrama “We’re doin’ a lot of work now, guys; big challenge, all that work!”

  3. supergirl said on March 1, 2019 at 11:18 am
    Reply

    This line made me laff…

    “Google notes that there is privacy to take into account as well.”

    Thats right !
    They dont want to make any mistakes that might allow you to have any….

    no??

    1. supergirl said on March 3, 2019 at 4:08 am
      Reply

      Yes that makes sense now. Don’t you think.

  4. 99 said on March 1, 2019 at 11:02 am
    Reply
  5. pd said on March 1, 2019 at 10:13 am
    Reply

    LOL

    Welcome to Firefox, circa 2009, Chrome users :)

    1. Heimen Stoffels said on March 2, 2019 at 9:40 pm
      Reply

      LOL

      Welcome to the old Opera, circa 2006, Firefox users :)

  6. Henny John said on March 1, 2019 at 10:12 am
    Reply

    Chrome is good. I still use it 5 years!!!

  7. gwacks said on March 1, 2019 at 5:23 am
    Reply

    “Now You: Do you use back and forward often in your browser?”

    Yes. And not more often than First Party Isolation and Temporary Containers.

  8. Chris said on February 28, 2019 at 9:21 pm
    Reply

    There goes Chrome following Firefox again!

    1. Heimen Stoffels said on March 2, 2019 at 9:39 pm
      Reply

      You mean: there goes Google following Firefox following the old Opera again! ‘Cause the old Opera (before they switched to the Chromium base) had it first, you know…

  9. Jojo said on February 28, 2019 at 8:52 pm
    Reply

    Say what? The Google team couldn’t find any more UI elements to eliminate or make more difficult to find? Couldn’t eliminate SOMETHING that would gain another 5 pixels of space in the browser window (oh wow!) while making the users day-to-day life more difficult?

  10. zakius said on February 28, 2019 at 5:45 pm
    Reply

    isn’t firefox doing it since ever?

    1. Martin Brinkmann said on February 28, 2019 at 6:12 pm
      Reply

      Yes it is.

  11. LTL said on February 28, 2019 at 3:01 pm
    Reply

    Good old Opera used to have that already eons ago. Being missing it ever since.

    1. Eric said on March 1, 2019 at 2:18 am
      Reply

      I thought the same! I used to love the almost instantaneous back function.

    2. Vítor I said on February 28, 2019 at 11:29 pm
      Reply

      Opera ≤ 12 RIP :-(

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.