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

If the whole site takes 5 seconds to fully hydrate and load its 20megs of JS I'll gladly take a server side rendered page that has finished loading in a second.


I would rather take a server side rendered page that finishes loading in 100ms than 400ms.


Average website loading time nowadays is measured in seconds rather than milliseconds...


On site like [1] Total Real Returns running on Crystal, response time could be sub 10ms but you are fundamentally limited by latency between you and server. Which could be 150ms if you visit to US server from Valeriepieris Circle, where 50% of population lives.

[1] https://totalrealreturns.com


Now using the solution of OP, the JS loaded website now takes 5.4sec instead of 5sec, a 10% slowdown that the users have to pay, and that will increase server costs.




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

Search: