CDN integration in Wordpress - Mini Project: Build & Apply

CDN integration

📖 Scenario: Your WordPress site loads slowly for international visitors because all assets are served from a single origin server. You need to integrate a CDN to serve static assets from edge servers worldwide.

🎯 Goal: Set up CDN integration for a WordPress site by rewriting asset URLs in functions.php and configuring cache headers.

📋 What You'll Learn

Define a CDN URL constant in functions.php

Create a filter function to rewrite upload URLs to the CDN

Hook the filter to WordPress content and attachment filters

Add cache-control headers for static assets

💡 Why This Matters

🌍 Real World

CDN integration is essential for WordPress sites serving global audiences, reducing load times by 50-80% for international visitors.

💼 Career

WordPress developers frequently set up CDN integration for client sites to improve performance and handle traffic spikes.

1

Define CDN URL constant

In functions.php, define a constant CDN_URL with the value 'https://cdn.yoursite.com'.

Wordpress

<?php
// functions.php

// Define a constant for your CDN domain
// Your code here

Hint

Use define('CDN_URL', 'https://cdn.yoursite.com') to create a PHP constant.

2

Create URL rewrite function

Create a function called rewrite_cdn_urls that takes $content as a parameter. Inside, get the site URL with get_site_url(), then use str_replace to replace the site's upload path with the CDN upload path. Return the modified content.

Wordpress

<?php
// functions.php

define('CDN_URL', 'https://cdn.yoursite.com');

// Create function to replace origin URLs with CDN URLs
// Your code here

Hint

Use str_replace() to swap the origin upload path with the CDN upload path.

3

Hook filters for content and attachments

Use add_filter to hook rewrite_cdn_urls to both 'the_content' and 'wp_get_attachment_url' filters so that post content and media URLs are rewritten to the CDN.

Wordpress

<?php
// functions.php

define('CDN_URL', 'https://cdn.yoursite.com');

function rewrite_cdn_urls($content) {
    $site_url = get_site_url();
    $content = str_replace(
        $site_url . '/wp-content/uploads',
        CDN_URL . '/wp-content/uploads',
        $content
    );
    return $content;
}

// Add filters for content and attachment URLs
// Your code here

Hint

Use add_filter('the_content', 'rewrite_cdn_urls') and repeat for 'wp_get_attachment_url'.

4

Add cache headers for static assets

Create a function add_cdn_cache_headers that hooks into 'send_headers'. Inside, use header() to set Cache-Control to 'public, max-age=31536000' for requests whose URI contains wp-content/uploads.

Wordpress

// Create function to add cache-control headers for uploads
// Hook it to 'send_headers'
// Your code here

Hint

Check $_SERVER['REQUEST_URI'] for upload paths and set cache headers with header().

Practice

1. What is the main purpose of integrating a CDN with a WordPress site?

easy

A. To disable all plugins for better performance

B. To increase the size of the WordPress database

C. To replace the WordPress hosting server completely

D. To speed up content delivery by caching static files globally

Solution

1. Step 1: Understand CDN function

   A CDN stores copies of static content like images and scripts on servers worldwide to reduce load time.

2. Step 2: Connect CDN purpose to WordPress

   Integrating a CDN with WordPress speeds up site loading by serving cached content from nearby servers.

3. Final Answer:

   To speed up content delivery by caching static files globally -> Option D

4. Quick Check:

   CDN speeds up delivery = A [OK]

Hint: CDN caches static files worldwide to speed up sites [OK]

Common Mistakes:

• Thinking CDN increases database size
• Believing CDN replaces hosting server
• Assuming CDN disables plugins

2. Which of the following is the correct way to configure a CDN URL in WordPress settings?

easy

A. Use a plugin or theme option to specify the CDN URL for static files

B. Add the CDN URL in the WordPress Reading Settings

C. Set the CDN URL in the WordPress General Settings under Site Address (URL)

D. Replace the WordPress Admin URL with the CDN URL

Solution

1. Step 1: Identify where CDN URLs are set

   CDN URLs are usually set via plugins or theme options that rewrite static file URLs.

2. Step 2: Understand WordPress settings roles

   General Settings and Reading Settings do not control CDN URLs; Admin URL is unrelated.

3. Final Answer:

   Use a plugin or theme option to specify the CDN URL for static files -> Option A

4. Quick Check:

   CDN URL set via plugin/theme = C [OK]

Hint: CDN URLs are set via plugins or theme options, not general settings [OK]

Common Mistakes:

• Trying to set CDN URL in General or Reading Settings
• Replacing admin URL with CDN URL
• Not using a plugin or theme for CDN integration

3. Given this WordPress plugin configuration snippet for CDN integration:

define('WP_CONTENT_URL', 'https://cdn.example.com/wp-content');

What will be the effect on loading static files like images and CSS?

medium

A. Static files will load from the original server URL

B. Static files will load from the CDN URL https://cdn.example.com/wp-content

C. Static files will fail to load due to URL mismatch

D. Only CSS files will load from CDN, images from original server

Solution

1. Step 1: Understand WP_CONTENT_URL constant

   This constant overrides the URL for the wp-content directory, where static files reside.

2. Step 2: Effect on static file loading

   Setting WP_CONTENT_URL to the CDN URL causes static files like images and CSS to load from the CDN domain.

3. Final Answer:

   Static files will load from the CDN URL https://cdn.example.com/wp-content -> Option B

4. Quick Check:

   WP_CONTENT_URL sets static file base URL = A [OK]

Hint: WP_CONTENT_URL changes static file base URL to CDN [OK]

Common Mistakes:

• Assuming static files load from original server
• Thinking only CSS or images load from CDN
• Believing URL mismatch causes failure

4. A WordPress site integrated with a CDN shows broken images after setup. What is the most likely cause?

medium

A. The hosting server is down

B. The WordPress database is corrupted

C. The CDN URL is incorrectly configured or missing in the plugin settings

D. The site theme is incompatible with WordPress version

Solution

1. Step 1: Analyze broken images cause

   Broken images after CDN setup usually mean static file URLs are incorrect or unreachable.

2. Step 2: Identify CDN URL misconfiguration

   If the CDN URL is wrong or missing, the browser cannot load images from the CDN, causing broken links.

3. Final Answer:

   The CDN URL is incorrectly configured or missing in the plugin settings -> Option C

4. Quick Check:

   Broken images = CDN URL misconfigured [OK]

Hint: Broken images often mean wrong CDN URL setup [OK]

Common Mistakes:

• Blaming database corruption for image issues
• Assuming theme incompatibility causes broken images
• Thinking hosting server downtime causes only images to break

5. You want to optimize a high-traffic WordPress site using a CDN. Which combination of strategies ensures best performance and security?

hard

A. Use a CDN with SSL support, enable caching for static and dynamic content, and configure cache purging on content updates

B. Use a CDN without SSL, disable caching, and rely only on WordPress caching plugins

C. Use CDN only for images, keep CSS and JS on original server, and disable HTTPS

D. Avoid CDN and upgrade hosting server hardware instead

Solution

1. Step 1: Identify performance and security needs

   High-traffic sites need fast delivery (caching) and secure connections (SSL).

2. Step 2: Choose CDN features for optimization

   Using CDN with SSL ensures encrypted delivery; caching static and dynamic content improves speed; cache purging keeps content fresh.

3. Step 3: Evaluate other options

   Options without SSL or caching reduce security and speed; partial CDN use or no CDN misses benefits.

4. Final Answer:

   Use a CDN with SSL support, enable caching for static and dynamic content, and configure cache purging on content updates -> Option A

5. Quick Check:

   SSL + caching + purging = best CDN practice [OK]

Hint: Combine SSL, caching, and cache purging for best CDN use [OK]

Common Mistakes:

• Ignoring SSL support in CDN
• Disabling caching reduces performance
• Using CDN only partially limits benefits