Skip to content

Clear your site's cache

If you’ve changed something on your site but still see the old version — an updated page, a new image, a price, a published post — it’s almost always caching: a saved copy of the page is being shown to make your site fast. Clearing the cache tells the system to build a fresh copy.

There are two places a saved copy can live: in your browser, and on the server (if your site uses our Optimized Webserver add-on with LiteSpeed Cache). Work through the steps below in order — the first one fixes most cases.

A normal refresh often reloads the page from your browser’s own saved copy. A hard refresh forces your browser to fetch everything fresh from the server.

  1. Open the page that looks out of date.

  2. Do a hard refresh:

    • Windows / Linux: press Ctrl + Shift + R
    • Mac: press Cmd + Shift + R
  3. Still seeing the old version? Open the same page in a private / incognito window (which ignores your browser cache entirely). If it looks correct there, the issue was just your browser — clear your browser cache and you’re done.

If your site is on the Optimized Webserver add-on, pages are also cached at the server by LiteSpeed Cache. Most of the time this clears itself automatically — publishing a post, updating a page, or completing an order purges the right pages for you. Occasionally (after a large change, a theme edit, or a bulk update) you may want to clear it by hand.

For WordPress sites, you do this from the free LiteSpeed Cache plugin:

  1. Sign in to your site’s WordPress admin (yourdomain.com/wp-admin).

  2. In the left menu, go to LiteSpeed Cache → Toolbox.

  3. On the Purge tab, click Purge All. This drops every cached page; the next visitor to each page gets a freshly built copy.

  • Your site isn’t WordPress, or you don’t have the LiteSpeed Cache plugin — there’s nothing for you to purge directly. Contact us and we’ll clear the server-side cache for you.
  • You purged everything and still see the old version — give it a moment and try a hard refresh again. If it persists, it may not be a cache issue at all (for example, a change that didn’t actually save, or a content/plugin problem). Reach out and we’ll take a look.

Still stuck? Open a support ticket and our team will help.