Welcome to WebmasterWorld Guest from 220.127.116.11
HTTPS is an added cost that many small websites just can't afford
5.7% of the top 10,000 sites
5% of the top 100,000 sites
3% of the top 1 million sites
<0.1% of the entire internet
Google made it easier for smart white hats to abuse serps
joined:May 27, 2015
An HTTPS connection will often just be forwarded as a simple TCP connection through the proxy because HTTPS traffic cannot be intercepted.
I don't know about the rest of you but for over a decade I spent most my time publishing tools, articles and everything else I could think of that would help my visitors be successful. Today, I spend most of my website time tweaking to the latest Google preference. Description tags, page layout, moving AdSense ads around, adopting https, mobile readiness, more links, removing links, disavowing links, title tags, and so on for minimal if not any gain.
joined:Apr 30, 2015
For anyone that doesn't understand the performance cost check out this research paper by Dave Naylor [cs.cmu.edu...]
This so called report is filled with nonsense, HTTPS does not cache... I did not waste another minute reading.
Myth #7 – HTTPS Never Caches
People often claim that HTTPS content is never cached by the browser; perhaps because that seems like a sensible idea in terms of security. In reality, HTTPS caching is controllable with response headers just like HTTP.
As of 2010, all modern, current-ish browsers cache HTTPS content by default, unless explicitly told not to.
It is not required to set cache-control:public for this to happen.
[edited by: goodroi at 11:52 pm (utc) on Jun 30, 2015]
Major sticking point seems to be SNI not working for IE on Windows XP.