And that's beside a whole rake of issues from having http and https on the same domain. It's just easier to have https everywhere.
And that's beside a whole rake of issues from having http and https on the same domain. It's just easier to have https everywhere.
For what it's worth, this was not true ten (or maybe even five) years ago.
I'd say it's true today, for most websites, but it's worth keeping in mind that it's a relatively recent phenomenon that HTTPS is now pretty easy to set up, use, and maintain. That wasn't always the case!
To a first order approximation, yes, and for small and medium sites, that's pretty accurate. But for very large sites, there can be additional complications and expenses, and that situation has improved over the last several years. Don't underestimate the effect that the downward price of bandwidth over the years has had - at very large scale, those pennies can really add up.
There's a reason why sites like Google, Facebook, Reddit, Tumblr, etc. took so long to add SSL to everything Or why some sites like Comcast still don't provide it. It's not (always) that they simply don't care or don't have knowledgeable engineers; it's that the logistics of managing[0] SSL at that scale are non-trivial. Arguably worth it, yes, but it's not so straightforward.
[0] heck, the logistics of paying for - even with a CDN, the marginal cost of adding SSL is not cheap.