3 ms·
The parent comment is downvoted (pretty heavily, since an upvote still didn't un-grey it) as I reply, but it's absolutely correct. I was doing latency optimiza
by nostrademons 8y ago
The parent comment is downvoted (pretty heavily, since an upvote still didn't un-grey it) as I reply, but it's absolutely correct.
I was doing latency optimization for Google in 2009. There was a strong negative correlation between latency and click-through rate - enough that the additional latency of adding JQuery (~140ms IIRC) would've cost us about $150M, and just moving the ads above the results in document order was estimated at $50M (the latter figure turned out to be wrong when I ran the experiments in 2010 - broadband penetration had made the latency difference in document order negligible - but that was the figure Marissa Mayer got in 2002 when most users were on dialup, extrapolated out to Google's 2010 revenues). 2 seconds was absolutely too long; our target was 250ms for the whole search to come back, including all backend calls.
If anything webpages have gotten slower today, with the rise of SPAs with lots of Javascript. Some of that is compensated for by faster Internet (though not a lot; in most of the U.S, speeds haven't budged much since 2009), but a lot is just that people have given up on the sort of marginal use-cases like amusing themselves that they used the web for in the 00s, and now tend to use it only for important things where they're willing to put up with slowness.
- andrewflnr 8y agoIt's technically correct but irrelevant to the point the article is trying to make, which is more about tolerance of users for sub-par performance than about where the goal should be set. Granted, you don't have to be relevant. There's plenty of room for making side points as long as you don't try to present them as a takedown of the OP.