![]() ![]() The bfcache is a snapshot of the entire page in memory (including the JavaScript heap), whereas the HTTP cache contains only the responses for previously made requests. ![]() The "cache" used by bfcache is different from the HTTP cache (which is also useful in speeding up repeat navigations). With bfcache enabled, browsers could eliminate the data transfer and time spent loading for billions of web pages every single day! How the "cache" works # In the video above, the example with bfcache is quite a bit faster than the example without it.īfcache not only speeds up navigation, it also reduces data usage, since resources do not have to be downloaded again.Ĭhrome usage data shows that 1 in 10 navigations on desktop and 1 in 5 on mobile are either back or forward. How many times have you visited a website and clicked a link to go to another page, only to realize it's not what you wanted and click the back button? In that moment, bfcache can make a big difference in how fast the previous page loads: With the entire page in memory, the browser can quickly and easily restore it if the user decides to return. bfcache basics #īfcache is an in-memory cache that stores a complete snapshot of a page (including the JavaScript heap) as the user is navigating away. Since version 96, bfcache is enabled for all Chrome users across desktop and mobile. In subsequent releases, additional support slowly rolled out. Starting in version 86, Chrome enabled bfcache for cross-site navigations on Android for a small percentage of users. Browser compatibility #īfcache has been supported in both Firefox and Safari for many years, across desktop and mobile. It significantly improves the browsing experience for users-especially those with slower networks or devices.Īs web developers, it's critical to understand how to optimize your pages for bfcache across all browsers, so your users can reap the benefits.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |