“Prebrowsing” (short for “predictive browsing” — a word made by Steve Souders) is simply loading a file before browser needs it, to provide a fast and instant user experience. You can decide on which content to prefetch by analysing your users behaviour, and try to predict which resources they will need ahead of time.
Browser cache isn’t enough
One might argue that “we already have browser cache!, we don’t need prefetch!”. But Steve Souders points out in one of his prebrowsing article, browser cache offers no help in many situations:
first visit — The cache only comes into play on subsequent visits to a site. The first time you visit a site it hasn’t had time to cache any resources.
cleared — The cache gets cleared more than you think. In addition to occasional clearing by the user, the cache can also be cleared by anti-virus software and browser bugs. (19% of Chrome users have their cache cleared at least once a week due to a bug.)
purged — Since the cache is shared by every website the user visits, it’s possible for one website’s resources to get purged from the cache to make room for another’s.
expired — 69% of resources don’t have any caching headers or are cacheable for less than one day. If the user revisits these pages and the browser determines the resource is expired, an HTTP request is needed to check for updates. Even if the response indicates the cached resource is still valid, these network delays still make pages load more slowly, especially on mobile.
revved — Even if the website’s resources are in the cache from a previous visit, the website might have changed and uses different resources.
The three big techniques
Browsers can analyze patterns to predict where users are going to go next, and start DNS resolution and TCP handshakes as soon as users hover over links. But to get the most out of these improvements, we can enable prebrowsing on our web pages, with three techniques at our disposal:
- DNS prefetching
- Link/resource prefetching
DNS is the protocol that converts human readable domains
http://www.google.com into computer readable IPs
http://126.96.36.199. DNS prefetching is an attempt to resolve domain names before a user tries to follow a link.
To improve the speed of redirects, content authors can add the following tag to their page:
<link rel="dns-prefetch" href="//host_name_to_prefetch.com">
<html> <head> <link rel="dns-prefetch" href="//www.domain1.com"> <link rel="dns-prefetch" href="//www.domain2.com"> </head> <body> <img src="www.domain1.com/image1.jpeg"> <script src="www.domain2.com/script1.js"></script> </body> </html>
Link prefetching is a browser mechanism, which utilizes browser idle time to download or prefetch documents that the user might visit in the near future. A web page provides a set of prefetching hints to the browser, and after the browser is finished loading the page, it begins silently prefetching specified documents and stores them in its cache. When the user visits one of the prefetched documents, it can be served up quickly out of the browser’s cache.
Standard link prefetching (executed by most modern browsers):
<link rel="prefetch" href="/css/style.css"> <link rel="prefetch" href="/js/scripts.js"> <link rel="prefetch" href="/img/big.jpeg">
Prerendering extends the concept of prefetching. Instead of just downloading the top-level resource, it does all of the work necessary to show the page to the user—without actually showing it until the user clicks. Prerendering behaves similarly to if a user middle-clicked on a link on a page (opening it in a background tab) and then later switched to that tab. However, in prerendering, that “background tab” is totally hidden from the user, and when the user clicks, its contents are seamlessly swapped into the same tab the user was viewing. From the user’s perspective, the page simply loads much faster than before.
You can trigger prerendering by inserting a link element with a rel of “prerender”, for example:
<link rel="prerender" href="http://example.org/index.html">
Situations in which prerendering is aborted:
- The URL initiates a download
- HTMLAudio or Video in the page
- POST, PUT, and DELETE XMLHTTPRequests
- HTTP Authentication
- HTTPS pages
- Pages that trigger the malware warning
- Popup/window creation
- Detection of high resource utilization
- Developer Tools is open
Inject prefetch hints at runtime
You can trigger the prefetch hints when you predict that a user action will require the download of additional content:
var hint =document.createElement("link") hint.setAttribute("rel","prerender") hint.setAttribute("href","next-page.html") document.getElementsByTagName("head").appendChild(hint)
Internet Explorer 9 supports DNS pre-fetching, but calls it prefetch. In Internet Explorer 10+, dns-prefetch and prefetch are equivalent, resulting in a DNS pre-fetch in both cases.
Preconnect, prefetch, prerender
- Prebrowsing - Steve Souders
- Link prefetching - Wikipedia
- DNS Prefetching - The Chromium Projects
- Pre-Resolve DNS - Google Developers
- Web Developer’s Guide to Prerendering in Chrome - Google Developers
- Link prefetching FAQ - Mozilla Developer Network
- Controlling DNS prefetching - Mozilla Developer Network
- One Step Ahead: Improving Performance with Prebrowsing - A List Apart
- Resource hints - W3C