4 ms·
If the page is just 'simple html', why does the overhead matter? I would imagine that the overhead of fetching data from a database, talking to the network, et
by nickpresta 15y ago
If the page is just 'simple html', why does the overhead matter?
I would imagine that the overhead of fetching data from a database, talking to the network, etc, would outweigh the cost of doing an SSL handshake if you bundle your resources correctly.
- ComputerGuru 15y agoYou're contradicting yourself here. If it's plain HTML, there's none of the database/intranet/etc going on and so every bit of overhead is noticeable... which is the point the GP was trying to make. Not that I share that opinion. I think the whole world needs to move on SSL, even though it's kinda broken in the current method where a select few companies make a crazy killing selling their SSL certs (although there are cheap alternatives).
- nickpresta 15y agoMy two points were unrelated. If it's a simple HTML site - who cares? A simple HTML site with < 100KB of content and < 15 resources to fetch isn't a bit deal anyways. Two or three seconds to a user on a mobile device isn't unreasonable. If the site is more complex, the SSL handshake most likely isn't your bottleneck. I found this[1] to be an interesting read. [1]: http://www.semicomplete.com/blog/geekery/ssl-latency.html http://www.semicomplete.com/blog/geekery/ssl-latency.html