Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The latency issue is only present once, the initial page load. After that the resources are cached. Second to that, if you're following best practices for page speed, the user will not notice at all because a snippet of CSS that provides the initial layout and styles will be sent with the HTML body. Amongst dozens of other things you can do to make this a non-issue.


>>The latency issue is only present once, the initial page load.

The initial page load is also one of the most important things to optimize for things like, you know, conversion of visitors to paying customers. I've given up on subscribing to new products and services simply because their pages weren't performing well, and I'm sure many others here have done the same.


I've given up subscribing because pages don't work (as in don't render anything at all) with JS disabled.


i've given up subscribing because pages look like shit in telnet:80

:D


Cached per browser, though, which is significantly different than cached per request.

Even if you're caching/serving static content efficiently it still adds load to a server.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: