3 ms·

The Instant Page feature sounds interesting. Has Google released any findings on bandwidth usage during typical browsing scenarios with this feature? How seve

The Instant Page feature sounds interesting. Has Google released any findings on bandwidth usage during typical browsing scenarios with this feature? How severe is this going to be for users with restrictive data plans? I don't see an obvious way to turn this feature off. There is an option to uncheck "Predict network actions to improve page load performance" but this says it is only doing dns lookups and then navigating based on IP address. I'm also curious how this will affect analytics. As a website owner, I now have to use their PageViews API to accurately track my hits from Google? Can websites opt-out of this service?

skymt 15y ago
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...
- jonknee 15y ago
  A problem with a header solution would be the user does frequently then see the requested content. Google's pre-fetching only kicks in if it believes you're going to visit, so most of the time it does end up getting shown to the user.