The performance of your WordPress sites has and always will remain one of the top priorities for us. Because of that, we have partnered up with KeyCDN, an HTTP/2 and IPv6-enabled content delivery network with 34 locations, to turbocharge your assets and media around the globe. In our experience, a CDN typically can help offload 70% of bandwidth requests from your web host and in some cases reduce load times by up to 50%!

How to Enable the Kinsta CDN

Follow the steps below on how to enable the Kinsta CDN on your WordPress site.

Important

CDN integration is tied directly to your site’s domain. For this reason, if you expect to make changes to your site’s domain in the near future, you should wait to enable the CDN until after you’ve made these changes.

Once the CDN has been enabled, if you change your site’s domain in any way, such as switching to a new domain or migrating from HTTP to HTTPS, you will need to select the option to remove the CDN integration. Once the CDN integration has been completely removed you can add it back.

Step 1

Login to your MyKinsta dashboard and click on “Sites.”

Step 2

Click on the WordPress site on which you want to enable the Kinsta CDN. Then on the left-hand side, click on “Kinsta CDN.”

Kinsta CDN

Kinsta CDN

Step 3

Click on the “Enable Kinsta CDN” button. This will deploy a CDN cache zone for your site. This can take up to 15 minutes. A random CDN domain will be assigned to your site and will look something like this: abcd1234.kinstacdn.com.

Enable Kinsta CDN

Enable Kinsta CDN

Note: We are also working on adding the ability to use a custom CDN URL on your site, such as cdn.yourdomain.com.

You will then see an installation progress screen in which the following happens:

If for any reason this process fails please contact support. After the zone has been created MyKinsta will automatically enable the CDN for your site. All the static content, such as images, CSS, and JavaScript files will now load from cache on the Kinsta CDN.

Once the CDN is enabled you have the following options:

Kinsta CDN info

Kinsta CDN info

Testing the Kinsta CDN

After the CDN has been deployed, you can test it with a website speed test tool. You will then see your assets and media loading from your CDN URL.

Kinsta CDN HTTP requests

Kinsta CDN HTTP requests

Make sure when you are speed testing your CDN that you run it a couple times so that the media is cached. The x-cache HTTP header will show a “HIT” once it is cached. If it isn’t cached it will show a “MISS.” If you don’t do this properly it might appear as though the CDN isn’t helping speed up your site, when really you simply didn’t build up the cache first. Read more about how a CDN works and how to properly run a website speed test.

Kinsta CDN cache hit

Kinsta CDN cache HIT

Each asset loaded from the CDN will also have an x-edge-location HTTP header with its corresponding location abbreviation. This way you can determine which POP and or location your asset is loading from. For example, below we can see that the location is ussf which means the asset is loading from San Francisco, USA.

CDN location HTTP header

CDN location HTTP header

Below is a full chart of POPs and their location abbreviations for reference.

POP Location
Atlanta, USA (usat) Oslo, Norway (noos)
Chicago, USA (usch) Paris, France (frpa)
Dallas, USA (usda) Stockholm, Sweden (sest)
Miami, USA (usmi) Vienna, Austria (atvi)
New York, USA (usny) Warsaw, Poland (plwa)
Los Angeles, USA (usla) Zurich, Switzerland (chzh)
San Francisco, USA (ussf) Bangalore, India (inba)
São Paulo, Brazil (brsp) Hong Kong, China (cnhk)
Seattle, USA (usse) Istanbul, Turkey (tris)
Frankfurt, Germany (defr) Moscow, Russia (rumo)
London, UK (uklo) Singapore (sgsg)
Madrid, Spain (esma) Tokyo, Japan (jptk)
Milano, Italy (itmi) Johannesburg, South Africa (zajo)
Auckland, New Zealand (nzau) Perth, Australia (aupe)
Melbourne, Australia (aume) Montreal, Canada (camo)
Sydney, Australia (ausy) Helsinki, Finland (fihe)
Amsterdam, Netherlands (nlam) Bucharest (robu)

Important Notes

Here are some important notes regarding the Kinsta CDN integration.

Multisite Compatibility

Subdirectory and subdomain subsites work with the Kinsta CDN. This includes domain mapping as well as mapping domains to a subsite. This has been tested with the WordPress MU Domain Mapping plugin and WPMUDEV’s Domain Mapping plugin.

However, there are some important things to be aware of when running multisite:

Please keep in mind that each theme and plugin can add more complexity to the site, or do things in a different way so they may not work with the CDN as expected. If you have any questions regarding this, please reach out to our support team before enabling the Kinsta CDN.

CDN Bandwidth

Each of our hosting plans come with a generous amount of free CDN bandwidth for both new and current clients. See included bandwidth below:

If you hit your CDN limit we’ll keep your site running and simply charge you $0.10 USD for each additional GB of CDN bandwidth. You can view your CDN bandwidth usage in MyKinsta Analytics under the CDN tab.

CDN usage analytics

CDN usage in analytics

You can also monitor CDN overages in the Resource Usage widget on the main page of the MyKinsta dashboard.

Struggling with downtime and WordPress problems? Kinsta is the hosting solution designed to save you time! Check out our features
CDN overage

CDN overage

Troubleshooting CDN

We redirect all traffic to HTTPS by default, but if you are running the Autoptimize WordPress plugin, ensure you are using HTTPS under the CDN base URL in the settings. If you enter HTTP by mistake it could result in mixed-content warnings on your site. Protocol-relative URLs should also work fine. Make sure to also purge the Autoptimize cache after saving.

Autoptimize Kinsta CDN settings

Autoptimize Kinsta CDN settings

Verify CDN with Google Search Console

When using the Kinsta CDN your images will automatically be crawled and indexed by Google. However, if you want to see additional data about your images (such as the number of indexed images), you can verify it with Google Search Console. Follow the steps below.

Step 1

Go to Google Search Console and click on “Add a Property.”

Add a property in Google Search Console.

Add a property in Google Search Console.

Step 2

Select the “URL Prefix” method and Input your full Kinsta CDN domain and click “Continue”.

Add Kinsta CDN to Google Search Console

Add Kinsta CDN to Google Search Console

Step 3

Because you don’t have control over the DNS for *.kinstacdn.com, you will need to choose the HTML file upload verification method.

Download the HTML verification file for Google Search Console.

Download the HTML verification file for Google Search Console.

Step 4

Download the file they provide and upload it to the root of your WordPress site via SFTP.

GSC verification file

GSC verification file

Step 5

Click on “Verify.” You should then see a successfully verified confirmation.

KinstaCDN verified in Google Search Console.

KinstaCDN verified in Google Search Console.


If you enjoyed this tutorial, then you’ll love our support. All Kinsta’s hosting plans include 24/7 support from our veteran WordPress developers and engineers. Chat with the same team that backs our Fortune 500 clients. Check out our plans