WPShift — caching
WordPress Redis caching and page caching, configured for you.
WordPress Redis caching on WPShift is one half of a two-layer setup that ships pre-installed and pre-configured on every server: a Redis object cache that speeds up database-heavy work inside WordPress, and a FastCGI page cache that serves whole pages straight from Nginx without touching PHP at all. It is aimed at anyone running WordPress in production, from a single site to an agency portfolio, and it needs no caching plugin, no drop-in wiring and no CLI diagnostics. There is nothing separate to pay for: caching is included on every plan, and the only limits that apply are the plan’s server and site counts (1 server and 3 sites on Personal at €5.99/mo, up to unlimited on Agency at €29.99/mo).
Two layers, one job: keep PHP out of the request path.
Most caching problems are configuration problems. WPShift ships sensible presets for the platforms that need special handling, WooCommerce, WP Super Cache, WP-Admin, and rule-based exclusions for the edge cases, so a logged-in checkout never gets a stale page.
The Redis object cache takes the repeated database queries WordPress makes on every request and answers them from memory. It is installed on every server with a per-site keyspace, so caches stay isolated between WordPress installs on the same machine. The drop-in is wired up automatically, and hit-rate, memory and key-count stats come from the site dashboard without installing a plugin or running diagnostics through the CLI.
The FastCGI page cache goes further: for anonymous traffic it serves finished HTML directly from Nginx, so PHP never runs at all. TTL, URI excludes, cookie excludes and per-method behaviour are configurable per site, which is why a logged-in WooCommerce checkout never gets a stale page.
What you get.
Redis object cache
Running out of the box with a per-site keyspace, so caches stay isolated between installs on the same machine. Key count, memory usage and hit-rate stats are visible from the site dashboard.
FastCGI page cache
A disk-backed page cache that sits in front of PHP and serves cached HTML directly from Nginx, measured in microseconds, not milliseconds.
One-click presets
Presets handle the URIs and cookies that need to bypass cache for WP-Admin, WooCommerce carts and WP Super Cache compatibility.
Rule-based exclusions
Configurable TTL, URI excludes, cookie excludes and per-method behaviour per site, for anything bespoke the presets do not cover.
Flush from the dashboard
Clear the whole site or a single path in one action when you ship something that needs an immediate purge.
Presets for the platforms that need special handling.
Caching breaks in predictable places: carts, checkouts, admin screens, plugins that manage their own cache. WPShift ships one-click presets for exactly those, WP-Admin, WooCommerce and WP Super Cache compatibility, covering the URIs and cookies that must bypass the cache.
For everything else there are custom rules. Add your own URI and cookie exclusions per site, and when you ship a change that needs an immediate purge, the flush button clears the whole site or a single path in one action. If you prefer, you can also ask the AI Copilot to flush a cache for you in chat.
Who it’s for.
Anyone whose sites need to stay fast under real load.
- 01
Agencies
Consistent caching across every client server without maintaining a zoo of caching plugins with different settings on each install.
- 02
WooCommerce operators
The WooCommerce preset keeps carts and checkouts out of the page cache, so shops get the speed without the stale-basket bug reports.
- 03
Freelancers
Ship fast sites by default. The stats live in the dashboard, so proving the hit rate to a client takes a screenshot, not a CLI session.
How it works.
- 01
The server ships ready
Redis and the FastCGI page cache are installed and tuned when the server is provisioned. There is nothing to install afterwards.
- 02
Your site is wired automatically
The Redis drop-in is connected when a site is created, with its own keyspace so neighbouring installs never share a cache.
- 03
Apply presets or your own rules
One click covers WooCommerce, WP Super Cache and WP-Admin. Add URI and cookie exclusions for anything bespoke.
- 04
Watch the stats, flush when needed
Hit rate, memory and key counts live on the site dashboard, and the flush button purges a path or the whole site instantly.
How it’s priced.
Caching is included with every server on every plan. There is no caching tier, add-on or gate.
See all plans and pricing- Both layers, Redis object cache and FastCGI page cache, ship on Personal (€5.99/mo), Professional (€14.99/mo) and Agency (€29.99/mo) alike.
- The only limits that apply are the plan’s server and site counts: 1 server and 3 sites on Personal, 5 and 15 on Professional, unlimited on Agency.
- The 7-day free trial runs full Professional features, no credit card required.
Questions, answered.
Do I still need a caching plugin?
No. The Redis drop-in is wired up automatically and the page cache runs in Nginx, in front of WordPress. Stats that would normally need a plugin, hit rate, memory, key counts, are on the site dashboard.
Does it work with WooCommerce?
Yes. The one-click WooCommerce preset excludes the cart and checkout URIs and cookies, so logged-in shoppers never see a stale page while anonymous traffic still gets cached HTML.
Can I exclude specific URLs or cookies?
Yes. TTL, URI excludes, cookie excludes and per-method behaviour are all configurable per site, on top of the presets.
How do I clear the cache after a deploy?
From the dashboard, one action flushes the whole site or a single path. You can also ask the AI Copilot to flush a cache in chat.
Do sites on the same server share a cache?
No. Redis runs with a per-site keyspace, so caches stay isolated between WordPress installs on the same machine.
Fast by default, from the first request.
Start your 7-day free trial with full Professional features. No credit card required, cancel anytime.