Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Hosting · Explainer

What Is Server-Level Caching in WordPress Hosting?

Short answer

Server-level caching means your host stores finished pages, database results, or compiled code on the server so WordPress does not rebuild them for every visitor. The main layers are page cache, object cache, opcode cache, and CDN cache. Most managed hosts turn these on for you, and they usually beat a caching plugin because they run before WordPress even loads.

Key takeaways

  • Server-level caching stores finished pages, query results, or compiled code on the host.
  • Kinsta runs four server-level cache types: bytecode, object, page, and CDN cache.
  • Kinsta's page cache expires every hour by default; WP Engine's holds pages for 10 minutes.
  • WordPress has a built-in object cache, but it only lasts for a single page load.
  • A plugin still helps with file optimization, but two page caches can clash.
  • Check the X-Kinsta-Cache header or load a page twice to confirm caching works.

What is server-level caching?

Server-level caching is caching that runs on your host's server, before WordPress loads, instead of inside a plugin.

When a visitor requests a page, the server first checks whether it already has a saved copy. If it does, it sends that copy straight away. WordPress only runs when there is no saved copy to serve.

Kinsta's caching guide lists four types of cache that run at the software or server level: bytecode cache, object cache, page cache, and CDN cache.

Most managed WordPress hosts run all four for you, with no plugin needed. That is the key point of this guide: the cache is part of the hosting, not something you bolt on later.

What are the layers of server-level caching?

Server-level caching has four layers, and each one saves a different kind of repeated work.

The page cache stores finished HTML pages. The object cache stores database query results. The opcode cache stores compiled PHP code.

The CDN cache stores static files on servers around the world. A request can hit several layers at once, and each layer you add removes work from the next one.

LayerWhat it storesTypical defaultWhere it lives
Page cacheFinished HTML pages10 minutes to 1 hourWeb server
Object cacheDatabase query resultsNo fixed expiryServer memory
Opcode cacheCompiled PHP codeUntil files changeServer memory
CDN cacheImages, CSS, JavaScriptHours to daysEdge servers worldwide

Defaults vary by host, so treat the table as a guide. The exact numbers below come from Kinsta and WP Engine, two hosts that publish theirs.

Some hosts push the CDN layer further. Hosting.com describes WordPress-aware full-page caching at the edge on its WordPress plans, plus WP Rocket and Object Cache Pro, so the edge layer can serve whole pages, not just static files.

What is page caching?

Page caching stores the full HTML of a page so later visitors get the saved copy instead of a fresh build.

Building a WordPress page means running PHP files and querying the database many times. For a page that rarely changes, that work is wasted on every visit. Page caching builds the page once and serves the saved copy to the next visitors.

Kinsta uses the nginx FastCGI cache module for page caching, set to expire every 1 hour by default, with options from one hour to one year in the dashboard.

WP Engine's page cache holds pages for 10 minutes by default, while its static assets stay cached for up to one year. The numbers differ, but the idea is the same: fresh pages often, static files rarely.

Pages that must differ per visitor skip the page cache. Kinsta's guide notes that the WordPress dashboard, WooCommerce carts, and similar pages are bypassed by default, and WP Engine's docs say the same for logged-in and cart pages.

What is object caching?

Object caching stores the results of database queries so WordPress can reuse them instead of asking the database again.

Every WordPress page runs many queries, and some repeat on every load, such as menus, options, and widget settings. The object cache keeps those answers in memory, which cuts database load and speeds up PHP.

WordPress has a built-in object cache, but it only lasts for a single page load. Kinsta's guide explains that cached objects are not reused after that one load, so a persistent cache needs an external store such as Redis, added through a drop-in file in wp-content.

WP Engine's object cache is optional and uses a 1 MB buffer with no fixed expiry. Its docs say old results are removed when the space fills up, using a least-recently-used rule, and that the cache can be toggled per environment from the user portal.

What is opcode caching?

Opcode caching stores compiled PHP code so the server skips the compile step on repeat requests.

PHP files must be compiled into machine code before they run. OPcache saves that compiled code, so the next request for the same file starts from the saved version instead of compiling again.

Kinsta enables OPcache for all PHP releases since 7.3. The trade-off is that changes to PHP files do not show up at once, which is why Kinsta disables OPcache on staging sites.

You never configure opcode caching yourself on managed hosting. It is either on or it is not, and the host decides. If your host lets you pick a PHP version, newer versions pair with newer OPcache builds, but the cache itself stays invisible.

How is server caching different from a caching plugin?

Server caching runs before WordPress loads, while a caching plugin runs inside WordPress after it has already started.

That order is the whole difference. A plugin still pays the cost of loading WordPress before it can serve a saved page. Server caching can answer the request without starting WordPress at all, which is faster and uses less server power.

That does not make plugins useless. WP Rocket vs host caching compares the two, and a plugin still helps with file optimization, lazy loading, and database cleanup that the server cache never touches.

How do you know if server caching is working?

You know server caching is working when the same page loads from cache on the second visit.

The clearest check is a response header. Kinsta adds an X-Kinsta-Cache header: the first request shows MISS and the second shows HIT when the page is served from cache. Other hosts use their own header names, so check your host's docs.

You can also watch load times. Load a page twice in a private browser window and compare the two loads. The second load should be clearly faster, since the first visit built the page and the second one read the saved copy.

When should you clear the server cache?

Clear the server cache whenever visitors should see a change that the saved copy still hides.

Publish or update a post, change a menu, edit a widget, or update a plugin, and the cache for the affected pages should be cleared. Good hosts purge the right pages on their own when you save content, so you rarely need to clear everything by hand.

Full clears are for bigger changes, such as a theme switch, a design update, or a fix that touched many pages. Redis vs Memcached for WordPress covers the object-cache side, where a clear is sometimes needed after a plugin change leaves stale query results behind.

What mistakes should you avoid?

The biggest mistake is running a caching plugin on top of server caching without checking whether they clash.

Two page caches can fight over the same pages, serve stale copies, or break logged-in areas. If your host already caches at the server level, check its docs before installing a caching plugin, and turn off the plugin's page cache if the host tells you to.

Other mistakes are common too. Do not cache pages that must stay personal, such as carts and account pages.

Do not forget the CDN layer, since a page rule such as Cloudflare's “Cache Everything” is what puts full HTML on the edge. How to set Cloudflare cache rules for WordPress shows how that layer is configured.

Frequently asked questions

Do I still need a caching plugin if my host has server-level caching?

Usually not. Most managed WordPress hosts run page, object, opcode, and CDN caching at the server level with no plugin needed. A caching plugin still helps with file optimization, lazy loading, and database cleanup, but check your host's docs first, since running two page caches at once can cause stale pages or broken logged-in areas.

How can I tell if my pages are served from cache?

Check the response headers. Kinsta adds an X-Kinsta-Cache header that reads MISS on the first request and HIT on the second. Other hosts use their own header names. You can also load a page twice in a private window: the second load should be clearly faster, since it reads the saved copy.

What is the difference between page cache and object cache?

The page cache stores whole finished pages, while the object cache stores the results of database queries. A page cache hit skips WordPress entirely. An object cache hit still builds the page but skips repeated database work. Most hosts run both, and they solve different parts of the same slow page.

Does WordPress have an object cache built in?

Yes. WordPress has a built-in object cache, but it only lasts for a single page load. A persistent object cache needs an external store such as Redis or Memcached, added through a drop-in file in wp-content. Kinsta offers Redis as an add-on, and WP Engine lets you toggle object caching per environment.

How long do cached pages last?

It depends on the host. Kinsta's page cache expires every hour by default, with options up to one year. WP Engine's page cache holds pages for 10 minutes, while static assets stay cached for up to one year. Good hosts also purge the right pages at once when you publish or update content.

Sources

  1. WordPress Cache - Kinsta Handles It So You Don't Have To Kinsta
  2. Manage Server and Browser Caching WP Engine
  3. Object Cache in WordPress WP Engine
  4. LiteSpeed Web Server - Apache Alternative LiteSpeed Technologies
  5. Hosting for WordPress with One-Click Install hosting.com

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test