Caching - Kinsta and WP Rocket

Caching improves site performance by storing optimised, pre-built versions of your pages, scripts, and styles. KIJO websites use a combination of Kinsta’s server-level caching and WP Rocket’s front-end optimisation to achieve fast loading times and strong Google Lighthouse scores.

If you don’t see your changes on the live site, one of these caching layers usually needs clearing.

🧊 Kinsta Caching

Kinsta handles high-level caching at the server and CDN level. This includes page caching, object caching, and asset caching. WooCommerce checkout and account pages automatically bypass caching so users always receive real-time data.

🔄 Clearing Kinsta Cache

If changes aren’t showing:

In the WordPress Admin Bar (top), click Kinsta Cache.
Select Clear Cache.

This flushes the server-side cache and forces Kinsta to regenerate fresh page versions.

When to Clear Kinsta Cache

After updating Elementor templates or global styles
After layout or structural changes (headers/footers)
After WooCommerce template edits
After plugin updates affecting front-end output

When to Check With KIJO

If you’re unsure whether an issue is cache-related or something deeper, check with KIJO before making assumptions.

⚡ WP Rocket (Performance & Front-End Optimisation)

WP Rocket provides the browser-side and front-end optimisation layer and is a core tool KIJO uses to help achieve high Google Lighthouse scores.

It handles page caching, CSS/JS optimisation, lazy loading, preload rules, and various performance improvements.

1️⃣ Clear WP Rocket Page Cache

If content updates aren’t appearing but the layout looks correct:

Admin Bar → WP Rocket → Clear Cache

This clears WP Rocket’s HTML page cache.

2️⃣ Clear / Regenerate “Used CSS”

WP Rocket analyses each page to determine which CSS is actually required, improving performance and reducing layout bloat.

If styles appear broken or not updating:

Admin Bar → WP Rocket → Clear Used CSS

Or via dashboard:

Settings → WP Rocket → File Optimization → Remove Unused CSS → Clear Used CSS

This forces a rebuild of the optimised CSS used across the site.

Use this after:

Elementor template updates
Styling or spacing changes
Adding/removing widgets or sections
Plugin updates that affect design

3️⃣ Other Optimisation Features (CSS, JS, Media, Preloading)

WP Rocket may also optimise:

Minification of CSS and JS
File combination (where appropriate)
Deferring/delaying JavaScript
Lazy-loading images, videos, and iframes
Preloading critical files
Database optimisation
CDN integration (if enabled)

These features contribute to faster loading times and improved Lighthouse scores.

Only adjust settings if you understand the impact, as some optimisation changes can interfere with Elementor, WooCommerce, LearnDash, or dynamic content.

🛑 When to Check With KIJO

Check with KIJO before modifying optimisation settings, especially if you’re working on:

JavaScript delay/defer settings
CSS/JS optimisation options
Preload or prefetch rules
WooCommerce-specific caching behaviour
LearnDash lesson or quiz loading
Anything affecting dynamic content (CPT archives, filters, AJAX, etc.)

Clearing caches is safe.

Changing optimisation configuration should be checked with KIJO first.