Post

I'm not sure how I feel about this part of Etsy's results: "About 1 in 14 prefetch requests was navigated to by the user." The performance improvements are superb, but a 7% hit rate doesn't sound great for server usage and bandwidth. What do you think, #PerfNow? What's the right balance?

I thought the same and questioned @stoyan.me on this! It also sounds like a LOT so wonder why do high if accurate. It means users are on average hovering over 14 questions and clicking on one. Or 14 users are hovering over links and only one is clicking. Both sounds suspiciously low to me.

On other hand, if users are hovering over items and then not clicking, then they may be clicking later (e.g. Search for "shoes", deciding between two—or more—search results, click one, then go back, and click the other). That may still show as an "unused prefetch" even if it was eventually used.

0 reposts1 like

Thanks Barry, I was curious to hear your thoughts on this. Did you have an 'ideal' activation rate in mind while setting the behaviour for the likes of moderate vs eager? (Side note: very cool to see the mobile viewport heuristics in your talk.)

I think it very much depends on the site. A 25kb edge-cached, long-lived, static HTML page that is cheap to prefetch for both site owner and user can be speculated a lot more aggressively IMHO than a 250kb origin server-side rendered for every request doc without caching.