DNS prefetching just resolves domain names before a user tries to navigate, so that there will be no effective user delay due to DNS resolution. The most obvious example where prefetching can help is when a user is looking at a page with many links to various unexplored domains, such as a search results page. Google Chrome automatically scans the content of each rendered page looking for links, extracting the domain name from each link, and resolving each domain to an IP address. All this work is done in parallel with the user's reading of the page, hardly using any CPU power. When a user clicks on any of these pre-resolved names to visit a new domain, they will save an average of over 250ms in their navigation.
Source: The Chromium Blog
Check that ‘…save an average of over 250ms…’!
Is that true? Can users verify that?
How to view Google Chrome’s DNS Prefetching records?
Of course we can. All you got to do is type ‘about:dns’ into Google Chrome’s address bar and hit Enter. You should be able to see Google Chrome’s DNS Prefetching records and the savings that it has given you after that.
Google Chrome hates Proxy Servers
Now, I also learned something new from The Chromium Blog today. Something that could explain why some users are not happy with Google Chrome, all because they failed to enjoy the super fast browsing experience that other users like me are enjoying. Poor blokes! :-)
Take a look around and see if you are behind or using a proxy. If you are behind or using one, then I’m afraid that you won’t be able enjoy Google Chrome like the rest of us. This is because proxy servers resolve domain names for you and they are doing a very bad job at it.
If you really want to enjoy Google Chrome, do not use proxy servers to connect to the World Wide Web. Go for a direct internet connection, only then you can see why most users are extremely happy with Google Chrome. :-)
DNS Prefetching (or Pre-Resolving)