Operator's Guide
Hosting with redis cache — 'The site is slow' from a client whose slow pages can never be cached
Written for whoever fields the complaint — where the pages the client is describing are precisely the ones a page cache is obliged to skip.
Straight answer first
Put client shops and membership sites on WordPress plans running Redis through AccelerateWP, because the object cache accelerates exactly the pages a page cache must bypass — basket, account, admin — which are the pages the complaint is always about.
Handled well this is a package rather than an apology. A client who has been told their shop is slow, shown which pages are affected and why, and then sold a fix with a measurement attached, is a client buying an improvement rather than accepting an excuse.
Written by the Hosting Seller staff · Checked 24 August 2026
Free
Migration into the account
24/7
Cover at any hour
Daily
Backups across every account
$0
To open a new account
The complaint arrives in the same words every time: the site is slow. What the client means, almost always, is that the admin is slow, or the basket is slow, or the account page takes an age — and none of those are pages a page cache is allowed to serve from a stored copy.
That mismatch is why adding another caching plugin so often achieves nothing visible. The plugin is caching pages that were already fast for people who were never complaining.
Diagnosing the complaint before you spend anything
Establish which pages are slow and for whom. An anonymous visitor loading a product page, a logged-in customer with a basket, and the client themselves inside wp-admin are three different measurements with three different explanations, and the client will describe all of them as 'the site'.
Nine times in ten the answer is the third one. The client is the person with an editor session open all day, so they experience the uncached path constantly while their customers do not. That is worth establishing gently, because it changes what you should sell them.
Once you know which path is slow, the fix follows. Anonymous product pages want page caching. Basket, account and admin want the queries behind them answered from memory, which is what an object cache does.
Why the second page-cache plugin never helps
Basket, checkout, account and admin pages are built fresh for every request by design, because serving a stored copy would show one customer another's basket. Caching plugins therefore exclude them deliberately, and adding a second plugin adds a second set of exclusions.
What is actually slow on those pages is repeated database work: option lookups, meta queries, session and cart handling. An object cache holds the answers to those queries in memory, so the page still builds fresh but stops re-asking the same questions.
The two layers answer different questions and should both be present. LiteSpeed caching runs at the server for the anonymous path, and Redis through AccelerateWP handles the pages underneath it.
Selling it as a package rather than an apology
Package it: a measurement before, the change, a measurement after, and a short note explaining which pages improved and why. That is a deliverable a client can understand, and it is billable in a way that 'we turned on a setting' is not.
Be precise about what will not change. Anonymous product pages that were already served from cache will look identical afterwards, and saying that in advance prevents the conversation where a client feels they paid for nothing.
Set the expectation about memory too. An object cache lives or dies by eviction — if the allocation is too small, entries are discarded before they are reused and the benefit evaporates. Ask what the allocation is rather than assuming.
Confirming it is genuinely working
The plugin's status screen shows the connection and the hit rate, which is the number to record before and after. A hit ratio above roughly 80% means the cache is earning its keep; a much lower one usually points at eviction or at a plugin invalidating everything on each request.
The subjective check is faster and more persuasive with clients. Open wp-admin and edit a product. If dashboards and edit screens stop wading through treacle, the object cache is doing its job, and that is the improvement the client will actually notice because it is the one they were complaining about.
Record both numbers in the client's monthly note. A performance change with a figure attached is remembered; one without is assumed not to have happened.
Our position on this page
We sell the tier that carries the caching described here, so read this as an argument from a supplier. The diagnostic method is the transferable part and it works whoever you buy from.
Both cache layers are inside the plan price rather than sold as a performance add-on, which is what allows you to bill for the diagnosis and the report rather than for the software.
- Redis object caching through AccelerateWP
- LiteSpeed caching at the server for anonymous traffic
- Switched on from the panel rather than by ticket
- Hit rate visible so the change can be evidenced
Why Hosting Seller
On every plan, as standard
The pages the client means
Object caching accelerates basket, account and admin — the uncacheable pages that generate the complaint in the first place.
Two layers, not two plugins
LiteSpeed at the server for anonymous traffic and Redis underneath it, answering different questions rather than duplicating one.
A number to show the client
The hit rate is visible, so a performance change can be evidenced rather than merely asserted in a monthly note.
No ticket to switch it on
Enabled from the panel, which matters when the same change has to be made across a fleet of client accounts.
Billable as a package
Measure, change, measure, explain — a deliverable a client understands, rather than a setting you quietly toggled.
Staging to test it first
Rehearse the change on a copy for shops where an eviction problem would surface as a broken basket rather than a slow one.
Price Tags Compared
How we compare with the household names
Typical sign-up and renewal prices across the market, set next to ours — the second number most comparison charts leave off.
| Line item | Hosting SellerBest seller | Typical big-brand host | Typical budget host | Typical loss-leader |
|---|---|---|---|---|
| Entry price / mo* | $2.42/mo | $4–$6 | $2–$4 | $1–$3 |
| Price at renewal / mo | $2.42/mo | $10–$15 | $8–$12 | $4–$6 |
| Renewal price on the entry plan is unchanged | ||||
| SSL on every plan | ||||
| Site migration included | ||||
| The entry plan uses NVMe storage | ||||
| Entry plan gets a backup daily | ||||
| Live human support, 24/7 |
*The number in our column is the cheapest plan on our shelf, priced on an annual term and pulled live from the very catalogue that feeds the pricing page, so it cannot drift out of date. Other columns show the ranges shared hosting tends to advertise inside each bracket: introductory rates that normally ask for a one-to-four-year commitment, then climb once that term expires. Naming individual competitors and printing their prices is something we have stopped doing. A figure we cannot re-check on the day you read it has no business sitting in front of you. So compare us with whoever you are genuinely weighing up, and read the renewal line first. That line tells you more than the headline ever will.
First Steps
From choosing to live
- 1
Find out who is experiencing the slowness
Anonymous visitor, logged-in customer, or the client sitting in wp-admin all day. It is usually the third, and knowing which one changes what you should actually sell them.
- 2
Record the hit rate before and after
Note the figure from the plugin's status screen either side of the change. A performance improvement without a number attached is assumed not to have happened.
- 3
Say in advance what will not change
Anonymous product pages already served from cache will look identical afterwards. Stating that first prevents the conversation where the client feels they paid for nothing.
In the Box
Packed with every plan
- Redis available on the plan and connected, not merely mentioned
- Page caching running alongside it at the server
- The memory allocation stated rather than discovered
- Enabled from the panel without raising a ticket
- Hit rate visible so a change can be evidenced
- Staging copies for rehearsing the change on a shop
- Daily backups with restores you run yourself
- NVMe disks underneath the whole arrangement
- Support that will discuss eviction rather than closing the ticket
- The renewal figure printed next to the joining figure
Across the Counter
Things people ask us all the time
A client says their shop is slow. Where do I start?
Establish who is experiencing it. An anonymous visitor on a product page, a logged-in customer with a basket, and the client inside wp-admin are three different measurements. It is usually the third — they have an editor session open all day, so they meet the uncached path constantly while their customers do not.
Why does adding another caching plugin never fix a slow checkout?
Because basket, checkout, account and admin pages are excluded from page caching deliberately — serving a stored copy would show one customer another's basket. A second plugin adds a second set of exclusions. What those pages need is the repeated database work behind them answered from memory, which is an object cache.
How do I evidence the improvement to a client?
Record the hit rate from the plugin's status screen before and after, and note which pages changed. Above roughly 80% means the cache is earning its keep. Pair it with the subjective check — editing a product in wp-admin — because that is the improvement the client will actually notice.
What makes an object cache stop helping?
Eviction, usually. If the memory allocation is too small the entries are discarded before they are reused and the benefit disappears, which shows up as a low hit rate rather than as an error. Ask what the allocation is before you promise anything, and rehearse the change on staging for a shop.
Read next
Hosting for Small Business Websites
Small business sites judged by what they cost to keep quick and to keep answered.
Hosting for Students
Student accounts read from the operator's side, including when hosting classmates becomes a business.
WordPress Hosting
WordPress looked after for you — caching, staging copies and daily backups included.
Mail Filtering
Spam and virus filtering in front of a client's mailboxes, wherever the mail is hosted.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Fix the pages the client is actually describing.
Redis object caching through AccelerateWP, LiteSpeed at the server, switched on from the panel and measurable.
See WordPress Hosting plans