3 ms·
I have a hard time believing 100ms is a serious issue unless the page is already over 1 second to be in a "ready" state. I think the rarely discussed "time to
by ck2 15y ago
I have a hard time believing 100ms is a serious issue unless the page is already over 1 second to be in a "ready" state.
I think the rarely discussed "time to first render" (for lack of a better word in my head - NOT domcontentloaded) is critical and part of that is the penalty for DNS cache miss which can already be up to 400ms in some cases.
Basically when people click, they want the browser to "do something already".
If you want easy ways to make your page to feel faster then stop loading javascript by default and do it after the page is loaded and don't load images below the fold by default - do all that in the background afterward.
All the CDN in the world won't help you if you have 10+ external javascripts, multiple stylesheets, and dozens of images loading on the page.
- jacques_chester 15y agoYou're right, but notice that adopting a CDN was the last thing on the Yahoo list they'd left undone. That list includes reducing the number of file loads, paying attention to DNS overhead and so on. From this I deduce that SO has already taken your advice.
- mzl 15y agoWhile it is hard to believe that 100ms will actually matter, it is precisely what both Amazon and Google found out when they studied latency sensitivity in users. Research is not only about confirming what we already believe, sometimes one actually gets surprising results :) Read the studies linked from the article for more details.