Slashdot Mirror

← Back to Stories (view on slashdot.org)

Google Prefetching for Mozilla Browsers

Posted by Zonk on from the two-great-tastes-that-go-great-together dept.

kv9 writes "A post on GoogleBlog reveals that Google has enabled results prefetching for Mozilla based browsers, which means that the top results of queries are being loaded in the background and pages will load faster. More info on the Mozilla Prefetching FAQ and the Google Webmaster FAQ"

18 of 424 comments (clear)

  1. Watch for this... by grub · · Score: 5, Insightful

    I can see employees being confronted for browsing pages they never actually looked at. An obvious example: innocently searching for info on the silly Vin Diesel movie "XXX" turns up a nice mix of Vin and pr0n in the top results. Presumably a mix of both are loading up in the background

    --
    Trolling is a art,
    1. Re:Watch for this... by Juvenall · · Score: 5, Funny

      To be fair though, it's never appropriate to search for Vin Diesel.

    2. Re:Watch for this... by argent · · Score: 5, Insightful

      You get people upping bandwidth costs and slowing down browsing time because the site maintainer THINKS they'll go to some next page but the site design actually ENCOURAGES them to go to some other, unrelated page.

      There are extensive studies from third parties on what people look at and do when they search on google. And you know what, they found people tend to look at and go to the top result, and don't even glance below the top few results most of the time.

      I'd expect that a company with the means to do the necessary research wouldn't go about implementing this kind of hackish "feature set" until it had thought things through a little better.

      I'd expect that Google has better figures on where people go to from Google's search pages than anyone else.

    3. Re:Watch for this... by bfields · · Score: 5, Insightful
      Prefetching is one of those things that seems like a really great idea on paper, but doesn't hold up so well in practice.

      The page you cite in support appears to be an argument specifically against prefetching pages with the rel=next attribute. As you say:

      The problem is that you have things like 'rel=next' that expect the user to go to some next "logical" page, but no structure to a site to encourage that logic.

      That's a flaw in firefox's prefetching logic, not in site-designers' use of rel=next, which was never intended to be used to indicate links the user was most likely to follow.

      In any case, google is actually using rel="prefetch", which *is* intended for that purpose. And google's use looks pretty sensible: "This tag is only inserted when it is likely that the user will click on the first link." From experimenting it appears that it's only used on some searches; e.g. the example they give is the first hit on a search for "stanford". So presumably they have fairly good evidence that a user is actually likely to click on such a link--I suspect they have enough data on this that they don't need to just guess.

      In OSS, a lot of the maintainers and coders are just "hackers" or college kids contributing bits and pieces of less broad knowledge over a bigger project team, not real software engineers who have been trained to really think through the consequences of certain design decisions.... I could see why someone at Google might think this is a good idea, but I'd expect that a company with the means to do the necessary research wouldn't go about implementing this kind of hackish "feature set" until it had thought things through a little better.

      I think you're making some huge generalizations here based on very little evidence.

      --Bruce Fields

    4. Re:Watch for this... by anethema · · Score: 5, Informative

      So turn it off in about:config, nothing lost.

      --


      It's easier to fight for one's principles than to live up to them.
    5. Re:Watch for this... by smallpaul · · Score: 5, Insightful

      Your post is confusing. First you say that prefetching doesn't work that well in practice and present a link to Simon Willison's blog. But the blog says that prefetching is an "excellent feature" except for a couple of quirks in Mozilla's implementation. Google does not trigger those quirks so they are irrelevant.

      Then you go off on a tangent about how "real software engineers" think through their design decisions more than "open source hackers". This is totally contrary to my experience. I would more highly rate the software engineering of Mozilla against Internet Explorer, Unix versus Windows or Apache versus IIS. I could go through a long list of brutal design decisions in commercial software that did not hold up in the real world but I'll just mention Clippy and the Windows registry as two high-profile examples.

      Finally, it is Google, a commercial software services company that is the topic of the article. So your whole argument is self-defeating. Either Google doesn't conform to your vision of real software engineering or the feature is not really at odds with real software engineering.

    6. Re:Watch for this... by switcha · · Score: 5, Funny

      Hi there. I just came across your post. I was searching for "Vin Diesel" on Google...

      --
      You know what? ... A little club soda *did* get that out!
  2. MSIE/MSN by mirko · · Score: 5, Insightful

    Does somebody knows whether MSIE and MSN collaborate the same way?
    Anyway it could be obvious that Google tries to establishes such alliances against his main concurrent (besides Yahoo).

    --
    Trolling using another account since 2005.
  3. Padding? by Quixote · · Score: 5, Interesting

    Would prefetching pad the click count for the ads that Google shows along the side? I know, the client (Moz) adds a
    X-moz: prefetch
    header, but how many server admins log this?

  4. Link is broken by KinkifyTheNation · · Score: 5, Informative

    Replace the %23 with a # and the url will work.

  5. This is Potentially Dangerous by cyranoVR · · Score: 5, Insightful

    Ever heard of the concept "one click and you're guilty?" Users of this feature who unknowingly perform a search that returns results containting offensive/illegal content may find themselves being prosecuted by local, state or Federal authorities...

    Proof of concept: Google caught in anti-Semitism flap. Replace "anti-semitism" with "child pornography" and you'll understand what I'm getting at...

  6. Yes - from the page with the bad link by slash-tard · · Score: 5, Informative

    1. Type "about:config" the address bar.

    2. Scroll down to the setting "network.prefetch-next" and set the value to "False".

  7. Comments by hendridm · · Score: 5, Informative

    3. I want to block/ignore prefetch requests. What should I do?

    To block or ignore prefetch requests (from Google and other web sites), you should configure your web server to return a 404 HTTP response code for requests that contain the "X-moz: prefetch" header.

    Sucks for those of us on shared providers, I guess, who don't want this so our bandwidth costs don't increase.

    I wish they had an option in the Google preferences to disable this, as I don't need a slower connection. Fortunately, you can disable it:

    Yes, there is a hidden preference that you can set to disable link prefetching. Add this line to your prefs.js file located in your Mozilla profile directory:

    user_pref("network.prefetch-next", false);

    It would be nice if there was an option in Firefox prefs to do this so I don't have to remember it every time I reload.

  8. Result, not results, and then still not always by Anonymous Coward · · Score: 5, Informative

    Only when google is confident that the top result is the one you want - the one link that the vast majority of people actually click - do they include the prefetch link for that one resource. Go and try it for yourself, and look for prefetch in the source. For the vast majority of searches, it isn't there. Only when looking for the authoritive resource (such as stanford.edu for "stanford") is the prefetch link actually there.

    Sure, their metrics might be off at times, but the way this has been implemented is definitely a good way, and will be very helpful for users of all browsers implementing prefetching (which currently is gecko-based only afaik, but could easily enough include opera and safari and such as well in the near future).

  9. How to turn it off yourself by dave7e9q · · Score: 5, Informative

    Type about:config ... then scroll down to network.prefetch-next ... double click it to "false" ... all done.

  10. This is great! by Slashcrap · · Score: 5, Insightful

    Unless :

    You have an ADSL line with a really stingy cap (for instance BT in the UK offer a cheap service with a 1GB/month cap). I'm sure their customers will be happy about downloading pages they won't read.

    You're a web admin that pays a lot for bandwith. I bet they'll be really happy that lots of people will be downloading their pages without ever looking at them.

    You're at work surfing through a proxy that does filtering / logging and there are some dubious sites that get pre-fetched for you. Enjoy getting sacked for something you didn't do!

    Well, I don't know about you, but I'm struggling to see any drawbacks to this great new technology!

  11. Re:But usually the top links on google by md27 · · Score: 5, Informative

    You do have this chance to vote, if you find a useful page clicking the "More like this" link, not only gives you pages tuned closer to that page, but it also tells Google that's what you wanted to see when you searched in the first place.

  12. Re:google tracks clicks sometimes by red+tiger · · Score: 5, Informative

    Actually the tilde-feature is properly documented.

    It is called synonym search and it really does some dictinary lookup, as it doesn't search for just the term entered but also its synonyms.

    Seems quite useful to me... To be honest, I had never heard of it before I read this thread here :)