rlange - 2:08 pm on Aug 9, 2011 (gmt 0)
Some more information on prefetching/prerendering: [code.google.com...]
In the "Detecting when your site is being prerendered" section their only suggestion is the Page Visibility API. There is this interesting bit, though:
If your site includes a third-party script for analytics or advertising, in many cases you shouldn't have to make any modifications to your site—the third party will simply modify the script they provide slightly to make use of the Page Visibility API. You should contact the third party directly to see if their scripts are prerender-aware.
Situations in which prerendering is aborted
In some cases while prerendering a site Chrome may run into a situation that could potentially lead to user-visible behavior that is incorrect. In those cases, the prerender will be silently aborted. Some of these cases include:
Note: This is not an exhaustive list. Last updated 6/13/11.
Plugins such as Flash will have their initialization deferred until the user actually visits the prerendered page.
Now, the prefetching is supposed to only trigger from the SERPs in those magical "high-confidence" situations, so the impact on both bandwidth and statistics may not be signficant, but still...