Common sense says-is HTTPS really slow? NO!

1 is a certificate required?

The certificate is required and https needs to be encrypted with the password in the certificate.

It must be installed on the server, but not on the client.

The client automatically downloads the certificate on the server, so it has no special effect on the client.

Process:

When the client accesses through https, the server sends the certificate (only the public key) to the client, and the client determines whether the certificate is trusted in the installed CA. If it is not trusted, there will be a warning, of course, you can also ignore the prompt to continue to visit.

Ssl certificate function: data encryption and authentication.

2 HTTPS is too slow?

The first connection is about 10% slower, and once a valid HTTPS connection is established, there is little difference between the two protocols.

3 HTTPS may be faster than HTTP?

This can happen in the internal Lans of some large companies, because typically, the company's gateways intercept and analyze all network traffic. However, when it encounters a HTTPS connection, it can only be released directly, because the HTTPS cannot be interpreted. It is precisely because of the lack of this interpretation process that HTTPS becomes faster.

Also attached:

Seven misunderstandings of HTTPS: http://www.ruanyifeng.com/blog/2011/02/seven_myths_about_https.html

Detailed analysis shows:

Analyzing HTTPS Performance Overhead

Https://www.keycdn.com/blog/https-performance-overhead/

Why is HTTPS faster than HTTP?

Https://samrueby.com/2015/01/26/why-is-https-faster-than-http/

Speed comparison Test of HTTP and HTTPS

Https://www.httpvshttps.com/