Yes, of course I have evidence. Refer to Google's experience in 2010 when they switched Gmail to HTTPS by default [1]:
> 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.
> If you stop reading now you only need to remember one thing: SSL/TLS is not computationally expensive any more.
> 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.
> If you stop reading now you only need to remember one thing: SSL/TLS is not computationally expensive any more.
1. https://www.imperialviolet.org/2010/06/25/overclocking-ssl.h...