How to Deploy HTTPS Correctly | Electronic Frontier Foundation. This is important for web developers and managers to understand. Many times I have been told that using HTTPS is too CPU intensive and that’s why it isn’t done. Adam Langley said:

In order to do this we had to deploy no additional machines and no special hardware. On our production frontend machines, SSL/TLS accounts for less than 1% of the CPU load, less than 10KB of memory per connection and less than 2% of network overhead. Many people believe that SSL takes a lot of CPU time and we hope the above numbers (public for the first time) will help to dispel that. [emphasis in original]