Understanding Caching Part 2: Server-Side Caching and Beyond

In Part 1 of our caching series, we explored browser caching—how it works on mobile and desktop devices, and how it helps your website load faster for returning visitors.

Now, let’s move to the next layer: server-side caching. While browser caching happens on a visitor’s device, server caching happens behind the scenes on your web host. It’s one of the most powerful tools for speeding up your site and keeping it running smoothly.

What Is Server Caching?

Server caching means storing dynamically generated content in a “ready-to-serve” format. Instead of rebuilding each page from scratch every time someone visits, the server keeps a copy ready to go. This greatly reduces processing time and server strain—especially for busy sites.

Types of Server Caching

There are several kinds of server-side caching, each with a unique purpose:

• Page Cache: Saves entire web pages so they don’t have to be rebuilt for every visitor.
• Database Cache: Stores database query results so the same data doesn’t have to be fetched repeatedly.
• Object Cache: Temporarily stores small chunks of data—like user preferences or recent posts—to reduce database requests.
• Opcode Cache: Keeps compiled PHP scripts in memory, so your server can deliver them quickly without reprocessing the code.
• Media Cache: Stores frequently accessed media files (like images and videos) to conserve bandwidth and improve load times.
  

How our partner Presslabs Handles Caching

If your site is hosted with Presslabs, here’s how their caching options are organized:

• Page: Use this when you make changes to your website’s HTML—like switching themes, adding or updating plugins, changing widgets or ad code, or making other edits that affect page structure.
• Memory: Use this after database operations such as search-and-replace, content imports, or plugin upgrades that affect the database.
• Assets: Refers to static files like CSS, JavaScript, images, fonts, and other files stored in your wp-content folder (except uploads). Use this to refresh those files when needed.
• CDN: Purges everything stored in wp-content/uploads—typically your image files, though some plugins store other assets there too.
  

(Descriptions adapted from Presslabs documentation.)

When to Manage Server Cache

Most hosting providers—ours included—have built-in caching systems to make things easier.

If you’re an admin on a Worship Times site, you can clear the cache directly:

• When you’re logged in, click “Refresh Cache” in the top admin bar on any page. This clears the server cache for that specific page.
• If you’ve made changes and they aren’t showing up—even after clearing your browser cache—it’s probably a server cache issue.
  

Theme and Plugin Cache: Special Considerations

Caching doesn’t just happen at the browser and server levels—many themes and plugins include their own caching systems too. Here’s what to know about a few common ones.

Divi Theme Caching

If your site uses the Divi theme, caching plays a key role in keeping your site running efficiently. However, Divi’s built-in CSS and JavaScript caching can sometimes cause styling issues after updates.

Best Practices for Divi Cache Management:

1. Go to Divi > Theme Options > Builder > Advanced.
2. Enable “Static CSS File Generation”, click Clear, then disable it again.
3. Clear your browser and plugin caches after updating Divi settings.
   

Event and Booking Plugins

(e.g., The Events Calendar — TEC)

Plugins like The Events Calendar (TEC) often rely on live database updates. Sometimes, caching can make event listings show outdated information.

In most cases, clearing the server cache fixes the issue right away.

If the problem persists or you’re unsure, reach out to us at support@worshiptimes.org and we’ll take care of it. We can also help adjust caching rules so frequently updated event pages are excluded from aggressive caching.

Logged-In vs. Logged-Out Users

Caching behaves differently depending on whether a visitor is logged in or not.

Logged-Out Users:

• Benefit the most from caching, since static pages, images, and scripts can be fully cached.
  
• Enjoy faster load times because full-page caching can be used freely.
  

Logged-In Users:

• Often bypass or limit caching so they always see up-to-date, personalized content.
• Pages like dashboards, forms, or shopping carts rely on live data instead of cached content.
• Rarely experience caching issues, but when they do, we’re happy to help resolve them.
  

Managing Cache for Our Users

At Worship Times, we handle caching for you through a combination of tools and managed solutions. Whether it’s browser, server, or plugin-level caching, we keep your site fast while making sure changes appear when they should.

Making the Most of Caching

Caching is one of the most effective ways to boost website performance, reduce server load, and improve the visitor experience. That said, it does require thoughtful management to avoid issues like outdated content or broken styles.

By understanding how browser, server, and application (theme or plugin) caching work together, you can keep your site running quickly and consistently—for both mobile and desktop users, and for both logged-in and logged-out visitors.

✅ Coming Soon — Part 3:
We’ll take a closer look at Content Delivery Networks (CDNs)—what they are, how they work with caching, and why they’re essential for modern websites.

Lovingly made by Worship Times, Websites for Ministries