Performance
Every WordPress site gets a full-page cache and a per-site Redis object cache, included with the hosting and running on the server rather than in a plugin you have to configure. Both are switches on the site's Performance tab, and the same tab measures what they change: Core Web Vitals from real visitors, request timings taken on the server, and code-level profiling that names the plugin or query spending the time.
These come with the hosting. They are not a tier and turning the paid upgrade off never removes them — which matters, because a downgrade that quietly took your caching away would be taking something you never bought and never stopped paying for.
Rendered pages are served straight from the cache, skipping PHP entirely for visitors who are not logged in. For a content or brochure site this is the single biggest win available, and it is the difference between a server that shrugs at a traffic spike and one that falls over.
A persistent object cache stops WordPress rebuilding the same database query on every request, so pages assemble faster under load and the database stays cool. Per site, not shared — your cache is not somebody else's eviction.
Carts, checkouts, account pages and anything served to a logged-in visitor are excluded by default, for WordPress and WooCommerce alike. A cache that serves one customer another customer's basket is not a performance feature.
Publish a post and it clears that post and the listings it appears on; a comment clears its parent; a theme switch clears everything.
Caching makes a page cheaper to serve. It does not make a heavy image lighter or a blocking script stop blocking — that is work on the site itself, and it is what the expert speed-up is for.
| Included caching | Expert speed-up | |
|---|---|---|
| Full-page cache (LiteSpeed LSCache) | Yes | Configured for how the site is built |
| Per-site Redis object cache | Yes | Configured and tuned |
| Image compression and modern formats | No | Yes |
| Render-blocking CSS and scripts | No | Deferred; critical CSS on the heaviest tier |
| A CDN in front of the site | From the CDN tab | From the CDN tab |
| How it is charged | With the hosting | One-off, by how complex the site is |
| Who does the work | You switch it on | Our engineers |
| How you get it | The Performance tab | Bought as an add-on |
The expert speed-up is priced by how complex the site is, because complexity drives the hours — see the speed-up page for what each tier covers.
Every site has one. It shows the caching that is already on, what real visitors are experiencing, and where your site's time is going.
The page cache and the object cache are included and listed there. Each is its own switch, so a site that has to leave one off keeps the other.
Read the Core Web Vitals card and the server-side timings first, so you have something to compare against rather than an impression.
If the numbers still disappoint, the bottleneck is usually not the cache — it is images, a plugin or a query. The expert speed-up is our developers finding and fixing exactly that.
Proof, not vibes
Core Web Vitals come from what real visitors actually experienced, checked automatically for your homepage and on demand for any other page. Server-side timings are real requests your site served, timed on the server before anything reached a browser — so a slow page is separated from a slow network.
Code-level profiling is the one that changes what you do next: every request is profiled on the server, and the history says which pages are slowest, which plugin or query is eating the time, and whether it is getting worse. A score out of a hundred tells you there is a problem; this tells you whose it is.
The difference between them is who does the work. Picking the wrong one is easy and expensive, so here is the honest map.
The page cache and the object cache come with your plan and are switched from the Performance tab. Right for most content and brochure sites, and it costs you nothing.
How caching works →A one-off service where we configure the caching against your actual site — the exclusions it needs and the rules it wants — and hand it back working.
See the speed-up services →Our developers work on what is actually slow: a query with no index, a plugin doing something expensive on every page load, a theme rendering the whole catalogue. Priced by how complex the site is.
Expert speed optimisation →The page cache is LiteSpeed's, and LiteSpeed Enterprise is what our fleet runs. If you host elsewhere and want the same engine, we manage that too.
LiteSpeed, managed →A server-side caching layer for WordPress, managed at the hosting level rather than by a plugin you install and tune. It is a full-page cache and a per-site object cache, both included with your plan and both switched from the site's Performance tab. There is no licence to buy separately and no configuration file to edit.
Two caching layers, and they are separate switches rather than one setting. The page cache serves rendered pages straight from LiteSpeed's LSCache, skipping PHP entirely for visitors who are not logged in — the single biggest win for a content or brochure site. The object cache is a per-site Redis instance that stops WordPress rebuilding the same database query on every request. Both are on every plan, and turning the paid tier off never takes them away.
No. The caching and the optimisations run on the server, underneath WordPress. We do ship the Zinn® Cache plugin as part of a site's deployment, but it is a cache controller rather than a cache engine — it exists so that publishing a post clears exactly the pages that post appears on, and tells our edge to do the same, instead of you clearing caches by hand.
The optimisations run at the server and cache layer and ship with safe defaults, including exclusions for the WordPress and WooCommerce paths that must never be cached — carts, checkouts, account pages and anything served to a logged-in user. If something does need excluding, the cache controller lets you exclude it rather than turning the whole layer off.
The same tab measures it three ways. Core Web Vitals come from what real visitors experienced. Server-side timings are real requests your site served, timed on the server before anything reached a browser. And code-level profiling names the plugin, query or piece of code that spent the time — which is the only one of the three that tells you what to actually change.
By who does the work. The caching on this page is already on, and you switch it yourself. The setup service is us configuring it properly for your particular site, once. The expert speed-up is our developers working on your site's actual problems — images, a slow query, a heavy plugin, a theme doing something expensive on every page load. They are not versions of one product; one of them may be exactly what you need and the others useless.
Every WordPress site we host carries both caching layers — they come with the hosting, not with a tier. What varies is the machine underneath: the caching runs where we control the server, so a site on a vendor-managed package gets what that vendor's platform provides instead.
The object cache is built for WordPress and that is where it does the most. The full-page cache is not WordPress-specific — a PHP application or a static site on our fleet is served by the same LiteSpeed page cache, and a static site is fast for reasons that make most of this moot.
Not at the moment. The caching on this page is what every WordPress site we host runs, and it is included. If your pages are still slow once it is on, the cause is usually images, a plugin or a query rather than the cache — which is work the expert speed-up does, by hand, against your particular site.
There is nothing to trial: the caching is included with the hosting and is on from the first deploy. The hosting itself comes with a card-free 14-day trial.
No, and deliberately. AccelerateWP ships an integrated CDN and we never switch it on, because every Zinn® site is already fronted by an edge we choose — a second CDN in front of it would mean two caches in series, and a purge on one would leave the other serving a stale page. Your CDN comes from the site's CDN tab.
Yes. Both layers are switches on each site's own Performance tab, and they are independent of each other — a site that has to leave the page cache off still keeps its object cache.
Start a card-free 14-day trial. The caching is on from the first deploy — open the Performance tab and watch what it does to your own numbers.
Start free