This won't make it any faster to visit new websites, but Google says that this kind of back-and-forth navigation is nonetheless pretty common, accounting for 19 percent of pages viewed on Chrome for Android, and 10 percent for Chrome on PCs.

It sounds like a simple enough feature, but there are challenges involved in getting it right. Privacy, for one, as bfcache would have to ensure there's no JavaScript running on pages that aren't actually there. And while the feature might have some benefit for battery life, as a suspended page is less intensive to reload than rebuilding it, it will likely be a fairly memory intensive process, which has traditionally been a problem for Chrome.

As such, Google is aiming to build it into Chrome in 2020, following tests this year. Safari and Firefox have been using a similar kind of caching for years -- Safari since 2002 and Firefox since 2005 -- so Chrome is playing catch-up here. But given the increasing focus around privacy and tech performance, it clearly wants to make sure it gets it right.