Object caching is a behind-the-scenes feature that makes your WordPress site faster by storing frequently used data in memory. This guide explains what it does and how it works on Web60.
What is object caching?
Every time someone visits a page on your WordPress site, WordPress runs a series of database queries. It looks up the page content, the site settings, the menu structure, widget content, and more. On a busy site, this can mean dozens of database queries per page load.
Object caching stores the results of these queries in your server's memory (RAM) instead of fetching them from the database every time. The next time WordPress needs the same piece of data, it pulls it from memory, which is significantly faster than reading from the database.
How Web60 uses Redis for object caching
Web60 uses Redis, a fast in-memory data store, to handle object caching for all sites on the platform. Redis keeps frequently accessed data ready in memory so that WordPress can retrieve it almost instantly.
This is enabled by default on every Web60 site. You do not need to install a plugin, change any settings, or configure anything. The platform handles it automatically.
How object caching differs from page caching
It is easy to confuse object caching with page caching because both aim to make your site faster, but they work differently:
-
Page caching stores the entire finished HTML of a page. When a visitor requests a page that is in the page cache, the server delivers the stored HTML immediately without running WordPress at all. This is extremely fast but only works for visitors who are not logged in and for pages that are the same for everyone.
-
Object caching stores individual pieces of data from the database. WordPress still runs and assembles the page, but it skips the slow database queries by reading cached data from Redis instead. This helps on every page load, including pages that cannot be fully page-cached.
Where object caching helps most
Object caching benefits all WordPress sites, but it makes the biggest difference on:
-
Sites with logged-in users. WooCommerce shops, membership sites, and sites with user accounts cannot rely on page caching for logged-in visitors. Object caching speeds up the database queries that run on every page load for these users.
-
Sites with dynamic content. Pages that change frequently or show personalised content often bypass the page cache. Object caching still reduces the load on the database for these pages.
-
Sites with complex queries. Sites using advanced custom fields, large menus, or many widgets run more database queries per page. Caching these query results in Redis prevents the database from doing the same work repeatedly.
What you need to do
Nothing. Redis object caching is fully managed by the platform. It runs automatically and requires no action from you. When you clear your site's cache from the Web60 portal, both the page cache and the object cache are cleared together.
Frequently asked questions
Do I need to configure Redis or object caching myself?
No. Redis object caching is enabled and managed automatically on all Web60 sites. There is nothing you need to install, activate, or configure.
Can I disable object caching on my site?
No. Object caching is a platform-level feature that runs on the server. It is not something that can be turned off per site. It improves performance for all sites on the platform.
Is object caching the same as page caching?
No. Page caching stores the complete HTML of a page so the server does not need to rebuild it for each visitor. Object caching stores individual database query results in memory so WordPress can reuse them without querying the database again. Both work together to speed up your site.
Last updated: 4 April 2026