WebWorld.nl
Performance

Setting up WordPress caching without surprises

Which caches exist, what they speed up and where things can go wrong.

Caching can make a WordPress site much faster, but “more cache” is not automatically better. The right configuration depends on the site, hosting, plugins and whether dynamic parts such as WooCommerce are present.

Page cache

A page cache stores generated HTML so WordPress and the database do not have to rebuild everything for every visit. This often gives the biggest gain for pages that are the same for many visitors.

Object and database cache

Object caching can speed up recurring database queries. The effect is most noticeable on more complex websites and web shops. A wrong configuration can add complexity instead, so measuring remains important.

Browser and CDN caching

Static files such as images, CSS and JavaScript can be kept longer in the browser or through a CDN. Use versioning, so visitors do not keep working with old assets after an update.

WooCommerce needs exceptions

Cart, checkout and account pages should generally not be cached as static pages. Sessions and personal prices also need attention. So always test the full ordering process after changes.

Measure before and after

Use caching as part of performance management: measure response times, Core Web Vitals and errors before and after the change. This avoids a fast benchmark that causes checkout problems in practice.

Which caching plugin suits LiteSpeed?

If your website runs on a LiteSpeed web server, as at WebWorld, LiteSpeed Cache is usually the logical choice. The plugin works with the cache in the server itself, which is faster than a plugin that only stores pages as files. Do not combine several cache plugins: two layers that both store pages often cause outdated content or errors that are hard to find.

Clearing the cache after changes

After an update or a theme change you sometimes still see the old version. Then clear in this order: the plugin cache, the server cache and finally the cache of any CDN. Afterwards check the page in a private window, so your own browser cache does not count.

What you had better not cache

  • Cart, checkout and account pages
  • Pages with personal content, such as member pages
  • Forms with a security token that differs per visitor
  • The WordPress admin area

Frequently asked questions

Does caching always make my website faster?

Usually yes, especially for visitors who open a page for the first time. For pages with a lot of personal content or a slow database, an object cache often helps more than a page cache alone.

How often should I clear the cache?

Normally the plugin handles that itself when things change. Manual clearing is only needed after larger updates or if you keep seeing an old version.

Can caching break my web shop?

Yes, if the cart and checkout are cached too. Exclude those pages and test the whole ordering process after every change.

Rather not manage this yourself?

We combine managed hosting, WordPress maintenance and support in one service.

Plan a free audit
WhatsApp WhatsApp