Create my own CDN, with my Subdomain

Hello, I would like to know if with the conditions that InfinityFree gives me I can create a CDN with a subdomain that I just created since using a subdomain for static files can improve the performance and speed of my website in certain situations. By using a separate subdomain for static files, I can take advantage of browser parallelism and reduce page load time. Now how do I do it?:eyes:
Could it be implemented with WP SUPER CACHE in your CDN section?

Just upload the static files to the subdomain?

InfinityFree is not a CDN, nor can it be used as one. A CDN is defined as a group of geologically distributed and interconnected servers. As all the free servers are housed in the same place, you can’t create a real CDN on free hosting.

Also, hosting the static files on a subdomain will not make the page load time any faster then if you host them on the main domain.


Well, I can understand a part, I understand that it is not possible in InfinityFree (and I respect it) @Admin , (and excuse me for being so sincere) but explain to me why you think that having files for example: js and css in my subdomain with symbolic links (which I just realized that they can’t be created either) won’t it optimize the loading of my website if you can take advantage of the parallel loading of the browser?

Of course InfinityFree is not a CDN but I was talking about trying to do the same thing with the subdomain. I really love these kinds of debates because that way we all learn something. If @admin can give his word from his experience, that would be great. Thank you!!

In fact, I just found a link to a website where this is better explained, what using a terminal from
our Cpanel I think it is not possible

These are not possible on free hosting




First of all, we don’t allow hotlinking on our hosting, and this includes to different domains on the same account or subdomains of each other. So creating two subdomains, having WordPress on one of them and static files on the other is just not going to work because our servers block it.

Also, the article even says it: doing this defeats the purpose of a CDN, because there is no delivery network. The only potential benefit is domain sharding, and while this was a great idea 10-15 years ago, nowadays the concurrency limits on browser is so much higher that the additional overhead of DNS lookups, TLS handshakes, and things like HTTP/2 making it a net negative anyways.

The article is a fun experiment, but it will be a pain to make it work here if it works at all, and if it does it will not help with performance.

If you want a CDN, get a CDN. If you don’t have one, no biggie, your website will work fine without it.


This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.