Feature Announcements

[Zachrulez]

HTTPS is soooo slooooooow

what?

There actually is a performance penalty so it likely is loading slower for people.

Edit: It seems that a header needs to be set with HTTPS to allow caching. I'm not sure if this was done when the change happened, but if it's not set to allow caching, that would actually explain significantly slower load times. (Since you would need to download all the content you are opening every time.) Fortunately if this is a problem, it seems to be an easily fixable one.

Edit 2: In windows you can open up PC settings, type in internet options and then from there go into the advanced tab. (In previous versions of windows it should be in the control panel.) Scroll down to security and check to see if the "Do not save encrypted pages to disk" is checked. If it is, uncheck it. MS

should cache

regardless of HTTPS if it's unchecked.

[Zachrulez]

Incidentally MS tests very low on caching.

I'm not sure what the site's situation is, but HTTP2 is still pretty new and can actually be detrimental and/or difficult to implement. Eventually there will be a benefit though I'm sure.

[Zachrulez]

I'm guessing it has to do with support and the lack of taking advantage of the features that would make it faster.

It'll be faster in the long run of things, but it's possible that it could be slower

now.

[Zachrulez]

It's actually more complicated than testing it's ability to load (lots of) images.

https://blog.fortrabbit.com/http2-reality-check

Example: It actually takes longer for an HTTP2 page to respond to a request to load, so if a page is small enough it will actually load slower in HTTP2.