Configure CDN

Once a site is created in InstaWP, you can supercharge its performance and security by enabling InstaCDN — InstaWP’s built-in content delivery network. InstaCDN delivers your site’s assets from edge locations closest to your visitors worldwide, reducing load times, improving Core Web Vitals, and protecting against malicious traffic.

In this documentation, we will explore:

1. How to Purge CDN cache
2. How to Configure Server Cache Time
3. How to Configure the Browser Cache Time

What is InstaCDN?

InstaCDN is content delivery network offered by InstaWP to its users, integrated directly into its hosting infrastructure. It is designed to make WordPress sites faster, more secure, and more scalable — without any manual setup or third-party plugins.

Here’s what the CDN offering looks like across InstaWP’s site plans:

When your site is live on InstaWP hosting, InstaCDN automatically activates and begins serving your site’s static assets (images, CSS, JavaScript, fonts, etc.) from the nearest edge server to each visitor. This reduces the physical distance data needs to travel, resulting in noticeably faster page loads.

Key Features at a Glance

How InstaCDN Works

InstaCDN operates silently in the background once your InstaWP site is live. Here is a high-level overview of the delivery flow:

• Visitor requests your site — A user anywhere in the world navigates to your WordPress site.
• Edge location identified — InstaCDN routes the request to the nearest PoP out of up to 119 global edge locations.
• Security check at the edge — Bunny Shield’s WAF and DDoS mitigation filters malicious traffic before it ever reaches your origin server.
• Assets served from cache — Static files (images, CSS, JS, fonts) are served directly from the edge cache, reducing origin server load.
• Dynamic content served from origin — Non-cacheable requests (PHP, dynamic pages) are passed back to InstaWP’s origin infrastructure seamlessly.

Bandwidth Used :  Displays the total amount of data transferred through the CDN. This includes all cached assets served to visitors from edge locations.

Requests Served: Indicates the number of requests handled by the CDN. Each request represents a file (such as images, CSS, or JavaScript) delivered to users.

Cache Hit Rate: 

• A higher percentage indicates better caching efficiency and improved performance.
• A lower percentage means more requests are being served from the origin server.

How to Purge CDN cache

Step 1: Navigate to the Sites page and select the site for which you want to purge the CDN cache.

Step 2: From the site dashboard, navigate to the left-hand sidebar and click on CDN.

Step 3: Click on Purge CDN Cache button located at the top-right corner of the CDN settings page to clear the cached content.

Configuring Server Cache Time

The Server Cache Time setting determines how long CDN edge servers cache your site’s content before checking for updates from the origin server. To configure Server Cache Time you will need to follow the steps below:

Step 1: Under Cache Settings, select Server Cache Time, open the dropdown menu, and choose either Respect origin Cache-Control to apply caching rules defined by your server or WordPress configuration, or select an override option (e.g., 1 year, 3 months, 1 week, etc.) to force the CDN to cache content for the specified duration.

Configuring the Browser Cache Time:

The Browser Cache Time setting controls how long a visitor’s browser (like Chrome, Safari, etc.) stores your website’s static files (images, CSS, JavaScript) locally. To Configure Browser Cache Time you will need to follow the steps below:

Step 1: Under Cache Settings, select Browser Cache Time, open the dropdown menu, and choose Match server cache expiration to follow the server-defined caching rules, or select an override option (e.g., 1 year, 3 months, 1 week, etc.) to set a fixed caching duration in the user’s browser.

Updated on: 25/03/2026