3 ms·
Those figures are for Google's services, so all those services can do TLS, but some of the clients don't. However the step change for HTTPS over the wider web
by tialaramex 6y ago
Those figures are for Google's services, so all those services can do TLS, but some of the clients don't.
However the step change for HTTPS over the wider web is mostly a bunch of related mutually enabling changes:
* Let's Encrypt launches
* Google slightly penalizes plaintext HTTP in search
* Browsers (Chrome, Safari, Firefox at least) stop offering new features outside Secure Context (so HTTPS for public sites) and begin deprecating or reducing scope of some older features outside that context.
On smaller sites also don't underestimate
* Prevalence of browsers/ devices without SNI falls a lot so...
* Many bulk hosting sites begin offering cheap or free HTTPS virtual hosting, with SNI, where previously they only offered IP hosting for HTTPS at higher prices.
In 2005 if I wanted my new one-joke web site to have HTTPS that's a bunch of extra money, for one corny joke, it's not worth it. Today, it's zero extra effort, if I make a new site it has HTTPS by default of course. If I see somebody whose host is trying to charge them money for this, these days it's rarely worth chipping in "You are being ripped off" because somebody else will be typing that already.