Welcome to WebmasterWorld Guest from 54.159.190.106

Message Too Old, No Replies

Google Announces Page PreFetching (again) - beta

   
5:27 pm on Jun 14, 2011 (gmt 0)

WebmasterWorld Administrator engine is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month Best Post Of The Month



Google just announced Instant Pages which works within Chrome (Beta) to load sites almost instantly. Looks like it pre-loads the top query using pre-rendering.


Related:
Banning Google FireFox PreFetching: [webmasterworld.com...]

[edited by: Brett_Tabke at 2:11 pm (utc) on Aug 3, 2011]

5:41 am on Jun 21, 2011 (gmt 0)

WebmasterWorld Senior Member 5+ Year Member



Analytics and advertising solutions will have to be updated to take account of prerendering via the page visibility API. In most cases the end site owner shouldn’t have to make any modifications to his page; the 3rd party will simply make a minor change to the javascript that is pulled into publishers’ pages. You should check with your analytics or advertising providers to check if their scripts are prerendering-aware.


Google on How Instant Pages Affect Analytics [webpronews.com]


CPM advertising services better be all over this or the burn-through rate for advertiser money could get scary!


Amazing! Google pushes something without an option for webmasters to opt out of it and expects the whole world to follow their order...
6:38 am on Jun 21, 2011 (gmt 0)

WebmasterWorld Senior Member tedster is a WebmasterWorld Top Contributor of All Time 10+ Year Member



There are some features for developers in the works, but they don't sound very simple or easy, at least not yet. And they are not standardized, either. From the Chromium blog:

The page visibility API [w3.org] - which is in the early stages of standardization in the webperf working group - can help developers understand the visibility status of their page: whether it's in a foreground tab, a background tab, or being prerendered. This is still an experimental implementation and it may change or even be removed in the future, which is why for the time being we've prefixed the property names with "webkit." Although the page visibility API is useful for detecting prerendering, it also has many other applications--for example, allowing a site to pause expensive physics calculations when the page isn't visible.

To learn more about the page visibility API and prerendering, check out the Using the Page Visibility API [code.google.com] and Web Developers' Guide to Prerendering in Chrome [code.google.com] articles.

Pre-rendering in Chrome [blog.chromium.org]


I added the bold red style for emphasis.
7:34 am on Jun 21, 2011 (gmt 0)

WebmasterWorld Senior Member 5+ Year Member



Google are in a hurry to speed up the display of other people's site but the bottleneck when clicking a search result often seems to be google url redirector itself which can take a few seconds.
10:31 am on Jun 21, 2011 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Amazing! Google pushes something without an option for webmasters to opt out of it and expects the whole world to follow their order...

... and why not ?
It's been going on for years. Each time Google sneezes webmasters jump backwards through burning hoops to please it.
3:50 pm on Jun 22, 2011 (gmt 0)

WebmasterWorld Senior Member 5+ Year Member



well you are right staffa.
3:23 pm on Aug 2, 2011 (gmt 0)

redhat



The following 4 messages were cut out to new thread by engine. New thread at: google/4347171.htm [webmasterworld.com]
3:17 pm on Aug 3, 2011 (utc +1)
This 96 message thread spans 4 pages: 96
 

Featured Threads

Hot Threads This Week

Hot Threads This Month