Switched on HTTPS and HTTP/2 for all hosted websites

Switched on HTTPS and HTTP/2 for all hosted websites


We at deZillium believe that all clients should get the same service, regardless of their yearly bill. We have therefore decided to switch on HTTPS and HTTP/2 support for all the websites that are hosted on our servers. You don't need to change anything on your behalf, just test and let us know if something isn't working as expected :-)


HTTPS stands for Hyper Text Transport Protocol Secure. It was also known as SSL (Secure Socket Layer) or in more recent years as TLS (Transport Layer Security). TLS has superseded SSL.

In simple English: It's the padlock you see in your browser when you visit a secure website (like a bank, or our website :-)). It ensures that data transmitted between your computer and our servers is protected from eavesdropping, like your username and password when you log in. That means that your Wordpress login credentials are no longer transmitted in the clear (in case you didn't have an SSL Certificate on your blog).

We believe everyone deserves the right to a secure website, whether that is a simple blog or an e-commerce website. We have therefore turned on HTTPS support for ALL websites that are hosted on our servers.

If you have already bought an SSL Certificate from us, that certificate will still be used until its expiration date, and you will then be switched to the free certificates, as everyone else. That means you will be saving money in the future since you no longer need to purchase SSL certificates :-).


HTTP/1.1 has served us for a couple of decades already. It's on old protocol, with severe limitations when you consider today's technology in relation to the past. In 2015, HTTP/2 was standardized. Not so late to the party, are we? Support in all major browsers has now been implemented, so there was nothing more left for us but to turn on support of it on our servers.

HTTP/2 offers plenty of advantages, such as header hashing and compression tables, but also multiple requests per connection. Previously your computer would open as many connections as it was permitted by your Operating System (usually 6) when requesting a website. That means that if your website contained 24 images, it would take a lot longer to get them than the 6 concurrent connections allowed, since each new connection carries with it TCP (Transmission Control Protocol) overhead. And that's not even counting other files (HTML code, CSS, javascript...). HTTP/2 allows for your computer to open a single connection to our servers, request as many files as the website needs, and our servers prioritize and send them accordingly, using that single connection. The benefits of that are faster websites, especially when you are on high latency networks, such as 3G or other wireless networks).

It also offers advantages to the developers. You no longer need to split files (CSS, javascript, images) to get better response times for your websites. Our servers take care of prioritizing them accordingly, and send them as fast as the client can pull them.

We hope you enjoy these improvements :-)

As always, if you have any questions or issues please let us know.