The "predict network actions" option you mention is indeed the option to disable prerendering. [0] If you use a third-party client-side analytics package, they

The "predict network actions" option you mention is indeed the option to disable prerendering. [0] If you use a third-party client-side analytics package, they've probably added support for the Page Visibility API [1] already, and you don't need to do anything. Server-side analytics will have problems, both with this and with HTML5 prefetching in recent versions of Firefox. I'd like to see opt-out available through an HTTP header (or even just a header to let the server know the page is being prefetched), but that's not anywhere in the spec right now. [0]: http://code.google.com/chrome/whitepapers/prerender.html http://code.google.com/chrome/whitepapers/prerender.html [1]: http://code.google.com/chrome/whitepapers/pagevisibility.html http://code.google.com/chrome/whitepapers/pagevisibility.htm...