HttpWatch, maker of an HTTP debugging tool, writes about web performance, HTTPS adoption, HTTP/2, and browser connection behavior.
Commenters cite it for HTTPS and HTTP/2 speed comparisons and for explaining what query strings expose over HTTPS.
It isn't just the network load. If you are on a small device the RAM use is not entirely insignificant.
The CPU load too, though I think the use of animation/video in adverts is more of a problem in that respect than the overhead of using jQuery instead of modern DOM APIs directly.
Even just considering network load, you need to be careful about the cache control headers that you send to ensure that all common browsers will cache content (see http://blog.httpwatch.com/2011/01/28/top-7-myths-about-https/ amongst other references) and you have to be careful not to accidentally indicate that it is OK to cache something sensitive (which is why some servers send blanked "don't cache" headers for HTTPS responses unless explicitly ordered otherwise, it is the safest default).
It's actually IE7 and IE8, and only for CSS file URLs (as opposed to URLs in CSS files). Details of protocol-relative URLs here:
http://blog.httpwatch.com/2010/02/10/using-protocol-relative-urls-to-switch-between-http-and-https/
...and the unfortunately double-loading bug for CSS files in IE7/8 here:
http://www.stevesouders.com/blog/2010/02/10/5a-missing-schema-double-download/
Yes. Just email the self-signed certificate to yourself, then open it up on the iOS device. You can also create a personal CA and install it the same way, if you plan on connecting to more than one host.
A quick search turned up some more instructions here: https://blog.httpwatch.com/2013/12/12/five-tips-for-using-self-signed-ssl-certificates-with-ios/
There seems to be, yes. Surprisingly little information to be had though.
http://blog.httpwatch.com/2015/01/16/a-simple-performance-comparison-of-https-spdy-and-http2/
I don't think server push was used in this benchmark, it's arguably a poor mans way to achieve part of what's discussed in the referenced paper (serving early dependencies...early).
For me, the possibility of faster page loads with HTTP/2 is the main selling point, plus the usual TLS advantages of guaranteeing the integrity of page content, etc.
Plenty of info on speed out there, here's one example: https://blog.httpwatch.com/2015/01/16/a-simple-performance-comparison-of-https-spdy-and-http2/
text-only version:
http://webcache.googleusercontent.com/search?q=cache:NotzT671SLkJ:https://blog.httpwatch.com/2014/07/07/google-has-given-https-a-huge-boost/&hl=en&gl=us&strip=1
the image:
https://blog.httpwatch.com/wp-content/uploads/2014/07/chart.png