Goodbye KeyCDN! Hello Gitlab!

Well the site had been hosted on KeyCDN for about weeks before I couldn't bear the waiting time for even a minor file.
See the result below:

That lagging time is not worth the money, I decided to try on Gitlab cause there's no need to spend much on other CDNs, whose SSL support is SNI and SAN support is rather expensive.

After a while of cloning and pushing and assign SSL, I ran the tests below:

It's really a waste of money when it comes to KeyCDN, while Gitlab is an amazing choice, though the SSL things need manually updating on Gitlab.

Goodbye KeyCDN! Hello Gitlab!

I've just been using Gitlab for a while and begin to love it! All I need to do is write and update and the rest procedures r automatically done by the runner!

To make things better, I just used CloudFlare's CDN for it, the speed has improved dramatically, which is well worth the loss of the old browser users, meaning I am finally back to CloudFlare CDN!

2016-12-30: Just made some tests between Gitlab Pages and Github Pages about the speed. They were both sped up with Cloudflare. No need in uploading those things, 'cause it's basically about data.

On the same image 33 kb, in Stockholm Github pages performed better with the time of 450 ms while Gitlab spent 995 ms, in Melbourne Github did it again with 497 ms while Gitlab spent 1.54 s. Globally, Github is faster.

Just moved to Github.

2018-01-12: To migrate from a server to another, I have to restore my backup. Then today I tried Gitlab to backup and restore. Everything worked like a charm fastly and conveniently with a free gitlab private (which I hadn't really care about when switching from Gitlab Pages to Github pages) repository in which there exists several branches. Then I realized how long I hadn't used Github since the last time. Also, with Netlify, the cert will look much more decent and be auto-renewed. So I just migrated the blog to Gitlab. After speedtest, I finally couldn't stand the speed loss again. 184.8kB in 2s or so almost everywhere. Is a Netlify page really using CDN? For the speed, I moved the blog back to Github PAGES + Cloudflare again.

2018-01-14: Moved to Google Firebase. It's not as fast as Github pages + Cloudflare, but the SSL time beats the CF. I can have enough privacy with my files.

2018-01-15: No way. It's a shared cert on Firebase. After the comparation below, I decided to move back to Gitlab+Cloudflare, 'cause I know I value more about privacy now. Gitlab+CloudFlare has an okay speed for larger files.

Repeated Views Load Time Of a 220.7 kB image (With CloudFlare CDN):

San Jose300ms49ms
New York374ms173ms

More about Gitlab+CF:

San Jose2ms22ms23ms1ms268ms6ms322ms
New York0ms79ms114ms1ms105ms150ms451ms

More about Firebase+CF:

San Jose2ms34ms34ms0ms6ms6ms49ms
New York0ms58ms77ms1ms22ms72ms230ms

About first-time view? The difference is larger. For instance, in Australia, Gitlab is 1.2s and Firebase is 58ms.

Also, just made a comparation between Gitlab, Github and Firebase on larger files:

The First of Repeated Views Load Time Of a 4.8MB image (With Cloudflare CDN):

San Jose342ms1.27s839ms
New York659ms1.17s677ms


San Jose2ms24ms25ms0ms247ms68ms366ms
New York2ms47ms49ms1ms146ms459ms705ms


San Jose2ms30ms30ms0ms866ms373ms1.30s
New York3ms61ms63ms1ms634ms468ms1.23s


San Jose0ms30ms31ms0ms321ms486ms868ms
New York0ms39ms41ms0ms112ms523ms715ms

2018-01-20: All the static assets on the site will be using the original CDN on the domain.

2018-01-21: After testing and pondering, the assets of my blog, hosted on Github are now sped up by Cloudflare.

2018-01-22: Moved the site back to Github, whose speed lures me into doing so. I'll consider moving back to Gitlab once the size reaches the limit.