Knowledgebase

Our CDN is a powerful, free content distribution network (or content delivery network) that uses physical, highly optimised servers across the world to cache the content of
your websites served from the UK2 platform.

Cached content of the data is stored at multiple CDN nodes so global customers will connect directly to CDN nodes instead of directly to our local network, resulting in content being served faster and your websites loading quicker.

What are the benefits of a CDN?

• Content is actively cached: Every global CDN node actively caches static files. This offers an enhanced and consistent user experience to visitors everywhere - at the same time, page speed is improved and you'll deliver better-performing sites to your users.

• Latency is reduced: The 20iCDN has highly connected CDN nodes globally - this means your users will always reach a node close to them, reducing latency and improving website load times.

• Improved SEO: With the 20iCDN, you’ll get a Website Acceleration Suite which gives you the tools to help get your Google PageSpeed Score to 100/100. You’ll be able to select the One Click Optimisation section to add the recommended settings which should add the ideal, safe settings to improve website load times. Because page speed is a direct ranking factor for your websites ensuring these options are selected within the 20i control panel can help ensure your websites are optimised for SEO.

Understanding the CDN

The CDN itself is used to cache static content. By default, the following file types are cached for 1 day before being purged automatically.

This type of cache is referred to as our Edge Caching as it's cached at our network edge __(a.k.a the CDN nodes).

This cache can be purged at any time from the Edge Caching section within StackCP

Head down to the Purge Cache section to clear all the cached static content from all CDN nodes.

You can also change the amount of time Image, CSS and JavaScript cache is kept on our edge from the Edge Caching section or directly from within StackCache in the WordPress admin area.

What is Dynamic Cache?

Dynamic caching is when content that is generated dynamically on the website is cached. This can be content that is generated from scripts on the website.

A copy of that content is stored and is then served to subsequent users who request the same content until the cache expires. Our Dynamic Cache provides the ability to cache any resource like this at our edge by using public Cache-Control and Expires headers.

For websites using our StackCache plugin (Available for Wordpress Hosting packages), this gives you full page dynamic content caching ensuring rapid TTFB times for all resources regardless of visitor location.

You can cache any other dynamic content using public Cache-Control and Expires headers via a .htaccess file - however, this is recommended only for advanced users only.

How to check your website is being cached

The easiest method to check that your site is being cached is to use Google Chrome's console to view your website's response HTTP headers.

In Google Chrome, follow the steps below:

• Using Chrome, visit your website, right-click and select Inspect to open the Developer Tools.

• Select the Network tab.

• Reload the website and the select any HTTP request from the left panel. The HTTP headers will be displayed in the right panel.

You'll be looking for the x-cdn-cache-status response to determine if the website has been cached. Please see the table below for the various responses
you may see.

Note: If you have other caching plugins such as W3 Total Cache or WP Super Cache these may interfere with the CDN and cause a cache MISS. These plugins can be disabled. 

Do we perform cache warming

Yes. The our CDN performs cache warming to ensure cached pages are served as frequently as possible, to as many users as possible.

When a user requests a web page, a cached copy is stored at the 20iCDN node closest to where they made the request.

If another user requests the same web page and uses the same CDN node they’ll be served the ‘warmed’ cache generated by the first user. This ensures that they get a cache HIT on their first visit, meaning that the website will load faster.