https incurs a heavy performance penalty for everyone. Server load isn't the problem; a large increase in latency for every single connection is.
Your typical blog is probably going to suffer even more from enabling https globally when compared to major sites because not as much effort has been put into combining js, css, and images into sprites.
I wish I could uprate you with more than one vote.
Seriously, https performance sucks from start to finish. If the average user doesn't care about https, but does care about performance, who are they going to go with - you or your faster competitor?
Probably depends on if their account gets hijacked at your site or the site of your fastest competitor.
I agree that anonymous or non-logged-in activity has no need of HTTPS, but anything that's transferring cookies, passwords, or other important user or session information should be HTTPS.
Google is currently working on something called "False Start" to reduce the number of roundtrips for an SSL connection to reduce latency. I believe there is already code in Chrome for this.
Comments
https incurs a heavy performance penalty for everyone. Server load isn't the problem; a large increase in latency for every single connection is.
Your typical blog is probably going to suffer even more from enabling https globally when compared to major sites because not as much effort has been put into combining js, css, and images into sprites.
I wish I could uprate you with more than one vote.
Seriously, https performance sucks from start to finish. If the average user doesn't care about https, but does care about performance, who are they going to go with - you or your faster competitor?
Probably depends on if their account gets hijacked at your site or the site of your fastest competitor.
I agree that anonymous or non-logged-in activity has no need of HTTPS, but anything that's transferring cookies, passwords, or other important user or session information should be HTTPS.
Google is currently working on something called "False Start" to reduce the number of roundtrips for an SSL connection to reduce latency. I believe there is already code in Chrome for this.
The main detractor is inability for intermediate parties/networks to perform caching.
You can't cache something that's encrypted!