-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
link rel prefetch #225
Comments
HTML5 Boilerplate talks about prefetch a bit in the docs |
Thats just DNS prefetching and not link prefetching |
oops sorry. I thought it also talked about link prefetching too. |
I wrote a StackOverflow answer for this a while back… and it's pretty comprehensive. tl;dr:
I would recommend to avoid it, as it is too fragmented and isn't used enough / doesn't seem to offer much advantages (browsers already do optimisation automatically anyway). OTOH, using |
@passcod's answer is basically there. A few small corrections:
There is no reason to avoid it. It's a browser hint, and it's not going to harm you: if the browser recognizes it, it may use it, if it doesn't, then no harm done. Details on Chrome implementation: |
@Raynos can you combine @passcod & @igrigorik comments to write a post on link rel prefetch? |
IE has improved its support: http://blogs.msdn.com/b/ie/archive/2013/12/04/getting-to-the-content-you-want-faster-in-ie11.aspx |
I updated my SO answer today: http://stackoverflow.com/questions/7830675/how-can-i-preload-a-page-using-html5/7830732#7830732 TL;DR: Prefetch has very good support, DNS Prefetch has near-universal support, the other three ( |
Its surprisingly hard to congruent information about it. Half of it is saying "its cool use it" and the other half says "how to break your web pages. use prefetch"
The text was updated successfully, but these errors were encountered: