4 ms·
It's the opposite, I recommend you check out the work of Steve Souders, his blog and his books (http://stevesouders.com/ http://stevesouders.com/). The general
by isleyaardvark 16y ago
It's the opposite, I recommend you check out the work of Steve Souders, his blog and his books (http://stevesouders.com/ http://stevesouders.com/). The general idea is that the server is going to be speedier (through a combination of hardware than caching) than the user's machine. And there are a lot of old machines out there.
Souders estimates that around 80-90% of a site's slowness has to do with the time it takes for the browser renders the page, js slows that down.
- dhimes 16y agoThanks for the link. Browsing "Even Faster Web Sites" he cited 14 rules from the first book ("High Performance Web Sites") in the preface. Rule 1: Make Fewer HTTP Requests. I guess this is what I had in mind. I have a request get the data, but how I allow user to render it different ways. So the local rendering is done in JS. I'm still building, but it look like I better give this a second look. I'm also in the education space, so where there are crappy machines there are also likely crappy networks.