Cito Boost is a built-in page cache that serves pages to visitors without running WordPress on every request, making WordPress and WooCommerce sites much faster with very little overhead. This can be found in your site’s settings by clicking the ‘Caching’ tab. We recommend testing on a staging site first (you can clone a site to create one) to make sure there is no unusual cache behaviour.
Cito Boost is currently available for WordPress sites only. The ‘Caching’ tab is not shown for other site types.

Enabling & disabling Boost

Use the ‘Enable Cito Boost’ switch at the top of the Caching tab. Changes apply immediately. Pages are cached for 6 hours. Only successful responses and redirects (HTTP 200, 301 and 302) are cached.

Checking if a page is cached

Every response from a Boost-enabled site includes an x-prostack-boost header. The main statuses are:
  • HIT - the page was served from the cache.
  • MISS - the page was not in the cache, so it was generated by WordPress and stored for next time.
  • BYPASS - the request skipped the cache because of an automatic exclusion, a cache exclusion or a cookie.
You may also see EXPIRED, STALE or UPDATING when a cached page is older than 6 hours and is being refreshed.
The first request for any page will be a MISS unless the cache is already populated, so always test twice. Test in a private browser window: if you’re logged in to WordPress, or your browser has any cookie that isn’t on your ignored cookies list, you’ll always see BYPASS.

What’s excluded automatically

Boost always bypasses the cache for the following, so you don’t need to add rules for them. Requests
  • POST requests (e.g. form submissions)
  • Any URL with a query string, unless it contains only tracking parameters
  • Add-to-cart links (add-to-cart=) and wp-api= requests
WordPress & WooCommerce pages
  • The WordPress admin area and login page (/wp-admin/, wp-login.php and other wp-*.php files)
  • xmlrpc.php and index.php
  • RSS feeds and XML sitemaps
  • Any URL containing /cart, /basket, /checkout, /check-out, /my-account, /store or /addons
  • WooCommerce API endpoints (/wp-json/wc, /wc-api), /coupon, /products-compare and /my-account/lost-password
Visitors with cookies
  • Logged-in WordPress users, visitors who have left a comment, and visitors viewing a password-protected post
  • WooCommerce shoppers with items in their basket or an active session
  • Any visitor with a cookie that isn’t on your ignored cookies list
The first two always bypass the cache, even if you add those cookies to your ignored list.
URL checks match anywhere in the path, so a blog post at /blog/cart-buying-guide would also bypass the cache. If this is a problem for your site, contact Support.

Cache exclusions

Cache exclusions let you keep specific pages out of the cache, for example a members area or a page that shows live stock levels. You’ll find them in the Caching tab under ‘Cache Exclusions’.

Adding an exclusion

Click ‘Add Exclusion’ and enter the path you want to exclude, plus an optional comment to remind you why.
  • Paths must start with /.
  • A rule matches any URL that begins with the path, so /members excludes /members, /members/profile and /membership. Add a trailing slash (/members/) to match only pages inside that section.
  • Use * as a wildcard to match anything, e.g. /shop/*/reviews excludes the reviews page of every product.
  • Matching is case-insensitive.
Every other character is matched literally, so you don’t need to escape dots or other symbols. Exclusions take effect immediately; you don’t need to purge the cache. You can add, edit and delete exclusions while Boost is switched off, and they’ll apply when you enable it.

Ignored cookies

Boost only serves a cached page when every cookie the visitor’s browser sends is on your site’s ignored cookies list. If a visitor has any other cookie, they get a freshly generated page. This means an unexpected session cookie from a plugin can never cause one visitor’s personalised page to be shown to someone else. Visitors with no cookies at all, such as first-time visitors and search engine crawlers, are always served from the cache.
The ignored cookies list starts empty, so any cookie at all will bypass the cache. Most sites use analytics or a cookie consent banner, which set cookies after the first page view. Until you add those cookies here, returning visitors won’t benefit from Boost.
Under ‘Ignored cookies’ in the Caching tab, enter the cookie name and click ‘Ignore Cookie’.
  • Add a trailing * to match every cookie starting with that name, e.g. _ga* matches _ga and _ga_ABC123.
  • Names can contain letters, numbers, dots, hyphens and underscores, and are matched case-insensitively.
  • You can add up to 50 cookies per site.
Changes apply immediately.

Which cookies to ignore

Only ignore cookies that never change what a page looks like. Common examples: Don’t ignore login or session cookies, or cookies that change content, such as currency or language switchers. If you do, visitors could be shown a cached page meant for someone else. To see which cookies your site sets, open it in a private browser window, accept the cookie banner, browse a few pages, and then check your browser’s developer tools (Application or Storage tab, then Cookies). If a page still shows BYPASS in the x-prostack-boost header, one of those cookies isn’t on your list yet.

Query strings

A query string is the part of a URL after the ?, such as /products?colour=red. Because these often change what a page shows, Boost bypasses the cache for any URL with a query string. The exception is tracking parameters added by ad platforms and email campaigns, which never change page content. If a URL’s query string contains only tracking parameters, it’s served from the same cache entry as the plain URL. For example, /?utm_source=newsletter and /?gclid=abc123 both get the cached copy of /. The parameters aren’t removed, so analytics tools running in the visitor’s browser still see them. If the query string contains any other parameter, even alongside tracking parameters (e.g. /?utm_source=newsletter&page=2), the cache is bypassed. The following are treated as tracking parameters:
  • utm_* (e.g. utm_source, utm_medium, utm_campaign)
  • Ad click IDs: gclid, dclid, fbclid, msclkid, ttclid, twclid, srsltid, ScCid
  • Others: _, _ga, __lsa, affiliate, eref, fb_ref, fb_source, fb_xd_bust, fb_xd_fragment, fbid, gref, hootPostID, hpt, ia_share_url, icid, iid, iref, linkId, migAgencyId, migRandom, migSource, migTrackDataExt, migTrackFmtExt, mod, ncid, npt, omcamp, pretty, snapid, wsrlui
Cached pages for tracking URLs are generated without the parameters, so any server-side (PHP) code that reads them won’t run on a cache hit. Client-side analytics such as Google Analytics are unaffected.

Purging the cache

Purging the entire cache

Click the ‘Purge Cache’ button at the top of the Caching tab.

Purging when content changes

To purge a specific page automatically when it’s updated, you need a plugin. We recommend Nginx Helper. Once Nginx Helper is installed, go to its settings, tick ‘Enable Purge’ and make sure the Caching Method is set to ‘nginx FastCGI cache’ (the default).

Cloning

Cache exclusions and ignored cookies are automatically carried over when you clone a site.