That’s the reload with a fully primed HTTP cache from that initial load. Loads pretty quickly, doesn’t it? The Smashing team has done a lot to make a fast website, so even a fresh load (though this experiment may not be a completely fresh load if you came to this article from the home page). Especially if you navigate from another page on the site. Loading with an empty cache or a completely primed cache are the two extremes, but the reality is that you might have a semi-primed cache with some but not all of the resources cached already. As an aside, that repeat view will likely not be fully representative anyway. But it still takes a little time, even if all the resources are being served from the cache. So, running your site through WebPageTest will show the initial load takes some time, but the repeat view should be faster. WebPageTest is one of the few web performance testing tools that actually tests a reload of the page using a primed HTTP Cache - most of the other tools just flag if your HTTP resources are not explicitly set to be cached. Similarly, before the Back/Forward Cache came along, being able to reuse these assets if going back to the home page was a good gain - even if it wasn’t instant.ĭownloading resources is a slow part of browsing the web no doubt, but there is a lot more to do as well as that: parse the HTML, see and fetch what resources you need (even if they can be gotten relatively quickly from the HTTP Cache), parse the CSS, layout the page, decode the images, run the oodles of JavaScript we so love to load our pages with… etc. There are likely lots of shared resources (site-wide CSS and JavaScript, logos, other images, etc.), so reusing them from that home page visit is a good saving. Going back to the example of visiting a home page and then going to an article page.
#Brave search engine crashes after restoring pages download#
Using the HTTP Cache can avoid the need to download the same resources over and over again. Sadly, however, it is not yet universal, but there are plenty of other articles written about that. Ensuring your website caches most of its assets for future uses has long been touted as essential for web performance. Didn’t The HTTP Cache Do All That Anyway?īrowsers have lots of caches, the most well-known of which is the HTTP Cache that stores copies of downloaded resources on a local drive for later reuse. All those navigations can benefit from the Back/Forward Cache to instantly restore the page. Similarly from cross-site navigation - think Google search results or the like and then clicking back. Think about the number of times you visit a home page, click on an article, then go back to the home page to view another article? Or you click back, then realize you forgot to make a note of something on that article, so click forward again. With that caveat out of the way, let’s get to the guts of the article: What is the Back/Forward Cache and why does it matter so much? As its name implies, this is a special cache used to remember the web page as you browse away from that web page, so if you browse back to it later, it can load a lot quicker. Edge, Opera, Brave) will now also have gotten this functionality too. Not to mention the many other Chromium-based browsers (e.g. Plus, they’ve created some more transparency about this, both in documentation and tooling. However, as the world’s most popular browser and the only browser feeding back the Core Web Vitals information for any search ranking boasting, Chrome getting this (finally, some might say) is important. So, let’s learn a little bit more about the Back/Forward Cache (aka bfcache), and what you can do to test if your website is compatible with it.įirst of all, it would be remiss of me to give the Chrome browser all the credit here, when the other two main browsers (Safari and Firefox) have had this concept for quite some time now, though there are some subtle differences in all three implementations. At the end of 2021, the Chrome team shipped some functionality that has the ability to make or break sites meeting the Core Web Vitals.
0 kommentar(er)
