Website Cache

What website cache is and why your updates may not show

Website caching stores copies of your site pages, images, and other assets so they can load faster for visitors. Instead of generating each page from scratch, the server or browser serves a saved version.

When you update your site, you might still see the old version on another computer or device. This usually happens because:

• The server cache is still serving an older copy of the page.
• The visitor's browser cache is holding on to previously downloaded files.
• A content delivery network (CDN), if used, has not refreshed its copy yet.

Most of the time, the cache updates automatically after a short period. If you need changes to appear sooner, you can control or clear the cache from your WordPress admin.

Benefits of website caching

Caching improves the experience for your visitors and reduces load on your hosting environment. Key benefits include:

• Faster page loads and better performance
  Frequently requested pages and assets are served from cache instead of being rebuilt every time, which reduces page load time.

• Reduced server load
  Serving cached content uses fewer CPU and database resources, which helps keep your site responsive even during traffic spikes.

• Improved scalability
  Cached pages handle more concurrent visitors because fewer dynamic requests reach your WordPress application and database.

• Better user experience
  Faster sites feel more responsive, reduce bounce rates, and encourage visitors to spend more time engaging with your content.

• Positive impact on SEO and Core Web Vitals
  Search engines factor page speed and user experience metrics like Largest Contentful Paint (LCP) and First Input Delay (FID) into rankings. A well‑cached site usually scores better on these metrics, which can support your visibility in search results.

How caching works on your WordPress hosting

On WordPress Managed Hosting and Agency WordPress Hosting, caching is handled at the platform level. The platform automatically:

• Detects which responses are safe to cache (for example, public pages).
• Stores copies of these responses in a cache layer.
• Serves cached responses to visitors until the cache expires or is cleared.

Dynamic, user‑specific content (for example, logged‑in dashboards, carts, and checkouts) normally bypasses or shortens cache so that each visitor sees the right information.

Personalizing your cache behaviour

You have several ways to tune how long content stays cached and which parts of your site are cached.

Cache expiry per file type

Configure different cache lifetimes for different asset types so that static files stay cached longer than frequently updated content. Common patterns include:

• HTML pages: Shorter cache lifetime so content updates appear sooner.
• CSS and JavaScript: Medium to long cache lifetime if you use versioned file names.
• Images and media: Longer cache lifetime because these files change less often.

Shorter expiry means fresher content but more server load; longer expiry improves performance but may delay how quickly visitors see updates.

Cache behaviour and purge timing

You can control how the cache refreshes and when it clears:

• Automatic purging: Certain actions, such as publishing or updating a page or post, can trigger a purge for related pages.
• Manual purging: Use the cache clear option in the WordPress admin bar to clear cached pages on demand.
• Targeted purging: Depending on your configuration, you may be able to clear the cache for specific pages or sections rather than the entire site.

Manual purging is useful after theme changes, plugin updates that affect layout, or significant content edits where you want visitors to see changes immediately.

Excluding pages from cache

Some pages should never be cached because they are highly personalized or time‑sensitive. Typical examples:

• Account dashboards for logged‑in users
• Shopping carts and checkout flows
• Search results or forms with dynamic responses
• Pages that display real‑time data

Configure cache exclusions for these sections so that the server always generates fresh content. This avoids issues where users see other users' data or outdated information.

How to access website cache settings

You may need specific permissions to view and manage cache settings for your WordPress site. Follow these steps to get access.

How to clear your website cache

Clearing the cache forces the platform to regenerate cached pages and assets the next time visitors request them. Use this when you make important content or design changes.

When to adjust cache settings vs. clear cache

Use these guidelines to decide whether to change cache configuration or just clear it:

• One‑time major design or content change
  Clear the cache so visitors see the new version. You usually do not need to change cache durations.

• Frequent updates to specific pages (for example, homepage news)
  Shorten the cache expiry for those pages or file types so changes appear faster without needing manual clears.

• Dynamic or personalized sections behaving incorrectly
  Exclude affected pages from cache or narrow the cache scope so user‑specific content is always fresh.

If you are unsure which approach is best for your site, share your use case with support and ask for recommended cache settings for your WordPress plan.