The different styles of hosting systems will have more latency for sure, like shared or VM's. 3 Seconds is pretty good for SSL delivery.
I guess I was just trying to make more of a point that Let's Encrypt is disrupting the very corporate and high profitable SSL Cert system with an open source free system. The more site that are using it the valid it becomes a standard.
The clients are paying for dedicated- not VM so pages should fly. About 4 years ago I had a client who was so sold on SSL that he wanted every page delivered by SSL He changed his mind in about 48 hrs after seeing what it did to server loads for his school so I got to bill him twice.
The fact that lets encrypt does not use web standards for certificates is bothersome as well. Encryption does not replace identity verification for security.
"Let's Encrypt: the bad stuff
The biggest problem with Let's Encrypt is that it democratizes access to https for any website. Yes, on the surface, this should in fact be a positive thing that we're celebrating. Unfortunately human nature comes into play here. When most people (non-geeks/non-IT) see https, immediate and unwavering trust is implied.
Even though Let's Encrypt is merely providing encryption for your website, most people visiting it will give it the same level of trust as websites with the "green bar" https (Extended Domain Validation), which includes the company name next to the padlock in the address bar.
This means that even though identity isn't actually verified at the same level as a green bar https website, most site visitors won't really know the difference. This is terrifying and we should be concerned about this. What most people don't realize is that a secure connection to an untrustworthy website doesn't mean it's safe to use.
To add further concern, there's very little preventing malware distributors from using Let's Encrypt certificates to make malware distribution websites look more official. Not only has it happened already, worse, is the fact that Let's Encrypt's stance on this issue is quite weak.
The initiative is putting far too much trust into the general public's understanding as to how https actually works. Fun fact folks – most people are clueless about tech. And the reality is merely comparing new registrations with Google's records won't be enough. Perhaps the blame for education needs to fall with the browsers instead?"
WHich brings us full circle to you get what you pay for.