To CDN or not to CDN? Why do you need to choose?

  • Gérald Barré

The loading time of a page is an important factor for the user experience. To speed up this one, CDNs (Content Delivery Network) propose to host the static files (CSS, JS, Images) on their servers. This allows to :

  • Reduce response times: CDNs have servers distributed around the world, so there is a server close to the user.
  • Reduce download time: Files used by multiple sites using the same CDN will only be downloaded once. Then they will be placed in the cache, which avoids re-download. This is especially true for commonly used libraries such as jQuery, Bootstrap, FontAwesome, and so on.
  • To reduce the number of requests on our server: it has more time to answer the "real" requests.
  • Reduce the time of sending the request (often negligible): the domain of the CDN is different from that of our site, the browser does not have to send cookies.

On the other hand, our application becomes dependent on the CDN. If this one is unavailable, the files necessary for our application can not be downloaded anymore and thus the application does not work. In general, this case is not acceptable.

For JavaScript and CSS files it is possible to use a CDN and in case of a problem to serve files from our site. So when the CDN is not available, the loading time of the page is a bit longer but the website still works. Let's see how to do that.

#JavaScript files

The first step is to add the script with the address of the CDN:

<script src="//"></script>

Then we will check the proper loading of the script. For that, we identify an object or a function defined by the script and we check that it exists. If this is not the case, we add a new script tag to the document. This new tag is added only if necessary and points to the file placed on our server. In our case we can verify that the angular object exists:

<script src="//"></script>
if (!window.angular) {
    document.write("<script src=\"angular.js\"><\/script>"); // Load local file

Depending on the needs the verification can be more complex, but the principle remains the same.

#CSS files

As for JS files we start by adding a link tag pointing to the CDN:

<link rel="stylesheet" href="//" />

Then you have to check that the style defined in the CSS exists. For this, we add a tag with a class defined in the CSS file. For FontAwesome we can for example use the class fa:

<link rel="stylesheet" href="//" />

<meta id="FontAwesomeTest" name="x-stylesheet-fallback-test" class="fa" />

We then check that the style applied to this tag is the right one with some lines of JavaScript. For example for FontAwesome we can check that the font-family is well defined to FontAwesome for the class fa:

<link rel="stylesheet" href="" />

<meta id="FontAwesomeTest" name="x-stylesheet-fallback-test" class="fa" />

var element = document.getElementById("FontAwesomeTest");

var style = document.defaultView && document.defaultView.getComputedStyle ?
    document.defaultView.getComputedStyle(element) :

if (style && style["font-family"] !== "FontAwesome") {
    document.write('<link rel="stylesheet" href="font-awesome.min.css" />'); // Load local file

It's a bit more complicated than for JavaScript, but it's still quick to put in place.


ASP.NET Core provides what you need to easily add fallbacks:

<link rel="stylesheet"
      asp-fallback-test-value="absolute" />

<script src="//"

It will automatically add the code shown in the previous sections. So, it's much easier to use.

#Security considerations

You cannot trust the CDN provider. They can tamper files they serve for many reasons (a bug, an attacker gains control of the server, etc.). You can prevent that by using SRI. Subresource Integrity (SRI) is a security feature that enables browsers to verify that resources they fetch (for example, from a CDN) are delivered without unexpected manipulation. It works by allowing you to provide a cryptographic hash that a fetched resource must match.

<script src=""

<link href="" rel="stylesheet"

You can use Content Security Policy to configure your server to mandate that specific types of files require the use of Subresource Integrity. Do this using the require-sri-for directive in your CSP header. For example:

Content-Security-Policy: require-sri-for script style;


As we can see it is very simple to use a CDN without being dependent on it. Just add a check for each remote resource. However, be careful to always use the same version of the scripts on the CDN and your server…

Do you have a question or a suggestion about this post? Contact me!

Follow me:
Enjoy this blog?Buy Me A Coffee