Speeding up your website with CDN
Find out how to improve your website by reducing loading times on a Web Hosting plan using the CDN
Find out how to improve your website by reducing loading times on a Web Hosting plan using the CDN
Last updated 23rd December 2021
If you want to improve user experience by speeding up your website, the most effective technique is to enable the CDN (Content Delivery Network) option. This allows you to cache static files, such as images, CSS and JavaScript, on the closest servers to your visitors.
This guide explains how to manage the CDN option on your Web Hosting plan.
How does a CDN work?
The CDN (Content Delivery Network) is literally a network dedicated to delivering content. It uses several servers around the world to display your website. The closer these servers are to your users, the faster your website performs for them.
In order for this to work, each server stores a part of your website in its cached memory. It is generally advised that you include so-called "static" files: images, JavaScript files and CSS, that help your website to run but are rarely modified.
The CDN option is already included in the "Performance" Web Hosting plans.
Log in to your OVHcloud Control Panel and select Web Cloud
in the top navigation bar. Click on Hosting plans
, then choose the relevant Web Hosting plan. Click on ...
to the right of "CDN option", then on Order a CDN
or Activate option
if the CDN option is already included in your hosting.
If you have a CDN option from before 11/19/2020, you can order the new Shared CDN offer by clicking Upgrade CDN to a later version
.
You will be redirected to a page where you can generate a purchase order. Once the order is paid, the service will be available within a few minutes.
Log in to your OVHcloud Control Panel and select Web Cloud
in the top navigation bar. Click Hosting plans
, then choose the relevant Web Hosting plan. On the Multisite
tab, click on ...
to the right of the Multisite entry, then click on Modify domain
.
Select the "Activate the CDN" option, click Next
and then Confirm
.
If an external (not registered with OVHcloud) domain name has been added to the Web Hosting as Multisite, you must enter the CDN’s IP address in the domain name’s DNS zone.
Check the IP address list for Web Hosting clusters to find the specific IP address for your cluster’s CDN.
Why is it not possible to use a geolocated IP with the CDN option?
The CDN uses the principle of "IP Anycast". You do not request the same server depending on your geolocation, which is very efficient for reducing the loading time of your static files. Therefore, a geolocated IP address is not needed.
In terms of SEO (search engine optimisation), the website loading speed is more important that the geolocation of the IP addresses.
The Shared CDN option is already included in all "Performance" Web Hosting plans, and has been available to order since 11/19/20. For older versions, please refer to the section Managing your Business CDN.
It is sometimes useful to clear the CDN cache, particularly when you modify static files - for example, when launching a new version of your website. You can clear the cache for each of your Multisite entries.
Go to the Multisite
tab for your Web Hosting plan, click on ...
to the right of the Multisite entry, then select Clear CDN
.
Go to the Multisite
tab for your Web Hosting plan, click on ...
to the right of the multisite entry, then on Modify the CDN
.
Some options are locked on the Basic solution and require you to sign up to CDN Security or CDN Advanced.
Always online: Allows CDN data to be kept online in the event of a server failure.
HTTP/2: Protocol that enables your website to perform better in terms of security and latency.
Dev-mode: Allows you to disable the cache during your website development.
Brotli: Compression type that optimises the size of your cached files.
Cache rule: Create up to 5 rules. They will set the cache refresh rate for specific resources on your site (see section below).
Once you have chosen your options, click Apply configuration
, then Confirm configuration
in the next window.
To add a cache rule on one of your website’s elements, go to the Multisite
tab for your Web Hosting plan, click on ...
to the right of the multisite entry, then Modify CDN
.
Under Cache rule, click the Add a rule
button.
Rule name: Give your rule a name.
URI: Enter the subset of resources for your website via its path in your website’s directory. For the CDN Basic and CDN Security offers, you can only enter a file extension.
Lifespan: specify the caching time for the chosen resource.
Order: Order your rules by execution order (lowest to highest).
Once you have made your choices, click the Create the rule
button.
Rules will appear in the list. You can modify a rule by clicking on ...
, then on Modify rule
or delete it by clicking Delete the rule
.
Once you have configured your rules and chosen your options, click Apply configuration
, then click Confirm configuration
in the next window.
To have a higher quota of rules and more settings available than creating cache rules, you can choose the Advanced CDN option.
Go to the Multisite
tab for your Web Hosting plan, click on ...
to the right of the multisite entry, then Modify the CDN
.
The options explained below require a subscription to CDN Security or CDN Advanced.
Cross-Origin Resource Sharing (CORS): In the list, enter the external domain names that will be authorised to access your website’s resources for the purpose of sharing them.
Once you have enabled this feature, click Edit list of external resources
to add the domain names that are authorised to share your resources.
Once you have completed your list, click Confirm
.
When you enable the CORS option without specifying any domain names in the list, all domain names will be allowed to use your website's resources.
HTTPS-Redirect: Protect all traffic to your website by redirecting it to the HTTPS protocol temporarily or permanently.
Once you have enabled the feature, click the drop-down menu to choose between Permanent redirection (301)
or Temporary redirection (302)
.
HTTP Strict Transport Security (HSTS): Force HTTPS access to your website. This way, your hosting is secure against downgrade (or rollback) attacks.
Once the feature is enabled, determine the lifetime for which the browser will apply HSTS on your website.
When you enable the HSTS feature on your website, it will enforce the use of the HTTPS protocol on your browser until the end of the period known as maximum age
, even after disabling the feature in your Control Panel. However, when the cache is cleared on the browser that has already visited your site, the browser will apply the new HSTS status.
Mixed content: Enforce the integrity of all your web pages's content. Pages will be loaded securely, contributing to an optimal user experience. All of your website’s internal and external resources must be available in HTTPS, to avoid a browser error.
Application firewall: The Web Application Firewall (WAF) protects your website from fraudulent attacks such as code injections, illegitimate requests or data theft. It covers the main known vulnerabilities on the web by filtering requests and packets transmitted (the list of vulnerabilities is managed by OVHcloud and regularly updated).
For the installation of an OVHcloud 1-click module, the WAF must be disabled in order to prevent the installation of the module from being blocked.
WAF is fully managed by OVHcloud and the list of vulnerabilities is regularly updated.
Go to the Multisite
tab for your Web Hosting plan, click on ...
to the right of the multisite entry, then on Modify the CDN
.
The options presented below require a subscription to CDN Advanced.
Geolocation HTTP Header: Determine the country of the visitor to customise the proposed experience. The country code is automatically added in the header of each request to be handled by your original server. The identification elements in the header are called Geo-Country-Code
, Geo-Country-Name
, Geo-Region
, Geo-City
.
Prefetch: Anticipate the next resource being loaded. Preload it automatically in the CDN cache using your website’s header link. This mechanism is mainly used to load CSS, JavaScript, images, favicons or web fonts that are required by the website theme.
In the example below, when the current page is displaying 'Hello', a subquery triggers the preloading of the resource /cache/style.css
.
<?php
header("Link: </cache/style.css>; rel=prefetch");
print 'Hello'
?>
Mobile redirect: Automatically redirect "Mobile" visitors to an optimised website. Choice: redirect systematically to the root of another website, or keep the URL by replacing only the domain (or subdomain).
Advanced Purge: Customise your purge by choosing which elements of the cache to clear: the entire site, a folder, a URI, a file extension, or using a custom regular expression.
In the Multisite
tab, click on the ...
button to the right of the multisite entry, then on Purge CDN
.
Query String: Content caching management, based on the parameters (also called Query String) of the URL query. Depending on your configuration, choose the behaviour of the CDN cache:
Prewarm: Force permanent caching of your critical resources. The CDN automatically anticipates and refreshes the cache, without waiting for a user request. This function applies only to static content, with a TTL greater than 0, and the resource must not exceed 1 GB. A gauge tells you the level of resource consumption in Prewarm, depending on your URL list. The total resources called by these URLs must not exceed 1 GB.
To define the list of URLs that should be in Prewarm, click Edit URL List
.
Using the Protocol
, Domain Name
, and Resource Path
fields, type one of the links to a resource that you want to add to the Prewarm function, and then click Add
.
A list is created in the lower frame, with all the links you have listed, you can delete the link of your choice by selecting it, then clicking Remove
.
Cache rule: Create up to 100 rules. They set the cache refresh rate for specific resources on your site. Continue reading the guide in the next step for more information.
Once you have chosen your options, click Apply configuration
, then Confirm configuration
in the next window.
To add a cache rule on one of your website’s elements, go to the Multisite
tab for your Web Hosting plan, click on ...
to the right of the multisite entry, then on Modify the CDN
.
Under Cache rules, click the Add a rule
button.
Once you have made your choices, click the Create rule
button.
Rules appear in a list. You can edit a rule by clicking ...
to the right of the rule, then Edit Rule
. You can delete it by clicking Delete Rule
.
Once you have configured your rules and chosen your options, click Apply configuration
, then Confirm configuration
in the next window.
In the Multisite
tab of your hosting, under the table, you can view the statistics of your CDN, indicating the number of requests per minute measured on it.
The CDN option is already included in the "Performance" Web Hosting plans or plans ordered before November 19th, 2020.
It is sometimes useful to clear the CDN cache, particularly when you modify static files - for example, when launching a new version of your site. In this case, you can completely clear the CDN cache.
Log in to your OVHcloud Control Panel and select Web Cloud
in the top navigation bar. Click Hosting plans
, then choose the relevant Web Hosting plan. Click on ...
to the right of "CDN option", then on Clear cache
.
Using a CMS
The main CMSs distribute several plugins that allow static files to be cached so that they are automatically included by the CDN. Others automatically configure static files by enabling an integrated caching to the CMS. For further information, please refer to the official documentation for the CMS or plugin that you use.
Without using a CMS
If you are not using a CMS, you can also use the CDN cache. To do this, you must add headers to the HTTP requests. There are several ways in which you can add these headers. One of the easiest ways is to define rules within a .htaccess file according to the file extensions.
1. # Cache images for 1 week
2. <FilesMatch "\.(jpg|jpeg|png|gif)$">
3. Header set Cache-Control "max-age=604800, public"
4. </FilesMatch>
5.
6. # Cache JavaScript and CSS for 1 month
7. <FilesMatch "\.(js|css)$">
8. Header set Cache-Control "max-age=2592000"
9. </FilesMatch>
Caching by using HTTP headers results in caching within the CDN but also within your users’ browsers. Therefore, to prevent your visitors from seeing an older cached version, it is recommended that you rename the files with every new version.
This action allows you to deactivate the CDN for one or more of your Multisite entries without removing the CDN option from your Web Hosting.
Log in to your OVHcloud Control Panel and select Web Cloud
in the top navigation bar. Click Hosting plans
, then choose the relevant the Web Hosting plan. On the Multisite
tab, click on ...
to the right of the Multisite entry, then click on Modify domain
.
Untick "Activate the CDN", click Next
and then Confirm
.
This action will remove the CDN option from your entire Web Hosting solution.
Log in to your OVHcloud Control Panel and select Web Cloud
in the top navigation bar. Click Hosting plans
, then choose the relevant the Web Hosting plan. Click ...
to the right of "CDN option", then on Cancel the CDN
.
Click Confirm
to continue with the cancellation.
You will receive an email containing the CDN closure procedure. Please follow the instructions in the email in order to confirm or cancel the request.
You can confirm that the CDN is active on your domain name via a terminal with the following command:
curl -i http://yourpersonaldomain.ovh/
If your domain name is being processed by the CDN, you will receive a result like the one below:
HTTP/1.1 200 OK
Date: Mon, 01 Jan 2020 00:00:00 GMT
Content-Type: text/html; charset=UTF-8
Set-Cookie: SERVERID12345=123456; path=/; max-age=900
Vary: Accept-Encoding
X-Request-ID: 123456789
X-CDN-Pop: rbx1
X-CDN-Pop-IP: 00.111.22.333/44
X-Cacheable: Cacheable
Accept-Ranges: bytes
Transfer-Encoding: chunked
X-IPLB-Instance: 12345
The "X-CDN" headers confirm that the domain is running through the CDN.
If the domain name is not running through the CDN, you will receive a result similar to the following:
HTTP/1.1 200 OK
Date: Mon, 01 Jan 2020 00:00:00 GMT
Content-Type: text/html; charset=UTF-8
Set-Cookie: SERVERID12345=123456; path=/; max-age=900
Server: Apache
X-Powered-By: PHP/7.1
Vary: Accept-Encoding
X-IPLB-Instance: 12345
The absence of the "X-CDN" header shows that you are not using a CDN.
Join our community of users on https://community.ovh.com/en/.
Please feel free to give any suggestions in order to improve this documentation.
Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.
Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.
Thank you. Your feedback has been received.
Access your community space. Ask questions, search for information, post content, and interact with other OVHcloud Community members.
Discuss with the OVHcloud community