When working with WordPress sites on Rocket.net, especially during migrations or major updates, you may notice that some assets such as CSS or JavaScript files still reference old URLs or display outdated styling.

This usually happens due to multiple caching layers combined with how WordPress content is migrated.

At Rocket.net, our internal migration tooling automatically performs a search and replace across the database, ensuring site URLs are updated correctly during migration. However, some users also perform their own manual or partial migrations, where URL replacements or asset regeneration may not fully complete.

In both cases, cached assets generated by page builders, the browser, or edge/CDN layers may still point to older versions of the site.

That’s why flushing caches is an important final step after any migration or major change.

Flushing your page builder cache forces WordPress to regenerate CSS, JavaScript, and dynamic assets using the correct, updated URLs.

Rocket.net Edge & CDN Caching Explained

Rocket.net uses a high-performance global CDN and edge delivery network to serve your website as close as possible to your visitors.

Instead of loading everything from a single origin server, your content is cached across 280+ global Points of Presence (POPs). This significantly improves speed and reduces latency worldwide.

What is cached at the edge?

The CDN caches only static assets, including:

• HTML (in cacheable contexts)
• CSS
• JavaScript
• Images

These assets are shared across visitors because they do not change per user.

What is NOT cached?

Dynamic content that changes per user or request is not cached, such as:

• Logged-in user sessions
• Personalized dashboard content
• Dynamic cart/checkout elements (WooCommerce, etc.)

Does the CDN modify my site content?

No. Rocket.net’s CDN (powered by Cloudflare Enterprise and edge infrastructure) never modifies your content.

If you see issues with HTML, CSS, or JavaScript not updating, and all caches have been cleared, the issue is almost always related to:

• Page builder cache
• WordPress caching plugins
• Theme optimization settings

not the CDN itself.

How CDN cache purging works

Whenever WordPress triggers a cache purge, Rocket.net’s CDN cache mu-plugin automatically sends a signal to the edge network to clear cached content.

You can also manually purge the CDN cache from:

• The Rocket.net WordPress dashboard
• The Rocket.net control panel

This ensures updated content is immediately propagated across all edge locations.

Page Builder Cache Clearing (Required Step)

Even after CDN cache is cleared, page builder caches may still serve outdated CSS/JS files. Follow the steps below based on your builder.

Elementor

1. Log in to your WordPress dashboard
2. Go to Elementor → Tools
3. Open the General tab
4. Click Regenerate CSS & Data

This rebuilds Elementor’s cached CSS files and ensures all assets use the correct current URLs.

Then clear your browser cache or test in an incognito window.

Divi

1. Go to Divi → Theme Options
2. Open the Builder tab
3. Go to Advanced settings
4. Click Clear next to “Static CSS File Generation”

Optional deeper cleanup:

• Go to Divi → Maintenance
• Click Clear All Caches

This forces Divi to regenerate all static assets.

WPBakery Page Builder

1. Go to WPBakery Page Builder → Settings
2. Open the CSS Generator tab
3. Click Rebuild Custom CSS

Clear browser cache afterward to confirm updates.

Beaver Builder

1. Go to Settings → Beaver Builder
2. Open the Tools tab
3. Click Clear Cache

This removes cached CSS and JS generated by Beaver Builder.

Avada

1. Go to Avada → Theme Options
2. Open the Performance tab
3. Click Reset Fusion Caches

Then:

• Go to Avada → Maintenance
• Click Clear All Caches

This ensures all compiled assets are rebuilt properly.

Oxygen Builder

1. Go to Oxygen → Settings
2. Open the CSS Cache tab
3. Click Delete CSS Cache

This regenerates Oxygen’s compiled stylesheets and layout data.

Common Caching Misconceptions

Sometimes users assume caching issues are caused by the CDN, but in most cases they are related to:

• Page builder cached CSS/JS
• WordPress caching plugins (e.g. WP Rocket)
• Theme optimization features

A useful troubleshooting step is temporarily renaming:
wp-content/cache → wp-content/cache1

Then re-clearing your caching plugin to force regeneration.

If issues persist, testing in an incognito window or different device can help confirm whether it is a local cache issue.

Need Help?

If you’re still experiencing outdated content after clearing all caches (page builder, CDN, and browser), our Support Team is here to help 24/7.

You can reach us anytime via live chat or by submitting a support ticket, and we’ll help you investigate and resolve it quickly.