Platform Buying Guide
Your writers never see the cache. That is the whole problem
A team of eight loses more hours to a slow editing screen than a homepage ever loses in bounce rate.
The short answer
Measure the administration screens, because that is where a content team actually meets its hosting. Pick the CMS your team's complexity justifies and put it on hosting with room for the load editorial work generates — our CMS plans carry every mainstream engine — but choose the tier on admin response time rather than on a cached homepage figure.
This page names where the admin time goes, gives you a target number, explains why the public-facing benchmark everyone quotes is the wrong one here, and finishes with the plan and the way to prove it.
By the HostingFast team · Reviewed 15 August 2026
Free
Migration, at no charge
24/7
Engineers on duty
Daily
Backup cadence
$0
Setup charge
Most writing on this subject is a league table bankrolled by referral fees. This one is about a cost most buyers never price: the seconds an editor waits, multiplied by everyone on the desk, every working day.
An editorial team meets its hosting through the administration screens rather than the public pages. Those screens bypass the cache completely and hit PHP and the database on every click, which makes back-end response time the figure governing daily output.
Where the admin time actually goes
Every admin screen is composed on request. There is no page cache in front of it and there cannot be, because the content is specific to one signed-in user with one set of permissions and one draft queue.
So the time divides three ways: uncached PHP execution, database queries against the posts and metadata tables, and whatever the editor itself loads in the browser. The first two are hosting; the third is your plugin choices.
The database half grows silently. Post metadata, revisions and term relationships accumulate for years, and a query that was instant on a thousand posts is not instant on eighty thousand. Nothing announces this; the desk simply gets slower.
This is why a team's experience of hosting can deteriorate while every public-facing metric stays green.
The number to hold a host to
Open the post list filtered to your busiest category, with the network panel recording, and read the time to first byte on the document request. Under 400 milliseconds is a desk that feels responsive. Past a second and a half, editors start batching their work to avoid the wait, which is where output quietly drops.
Take the same reading on the media library and on a save. Those three cover the three shapes of admin work, and a plan can be fine on one and poor on another.
Repeat the readings at your busiest editorial hour rather than at midnight. Variance across the working day is what exposes an oversubscribed machine, and it is the figure a demo will never show you.
Why the usual benchmark is the wrong one here
Public-page speed scores measure a cached response. They are worth having, and they say almost nothing about the tool your staff use for six hours a day.
The related mistake is debating the CMS for months and treating the hosting as a footnote. The infrastructure underneath determines how that CMS feels on every one of the next thousand working days, regardless of which one you chose.
Three things move admin response time: NVMe storage under the database, OPcache so PHP is not recompiling, and object caching so repeated metadata lookups are answered from memory. None of them appear on a public speed score.
Our pick, and the proof
Turbo is where this page lands: 25 sites on one account, 20 GB of NVMe, per-site PHP switching, LiteSpeed at server level and daily backups with self-service restores — enough headroom for a publication and for the staging copy you will want beside it.
Prove it with the three admin readings. Post list, media library, save. Before the move and after it, at a comparable hour, with the same content restored. Migration is free and usually completes inside a day.
Then run the commercial checks: renewal rate against order rate, a real question to support at an awkward hour, the refund terms read for carve-outs, and the company registration looked up on the public record.
Our commercial interest, stated in the body copy
Most 'best hosting' content is ranking-for-hire. We sell what we are describing and say so up front, which lets the rest of this page be about admin latency rather than star ratings.
Already hosted somewhere slower? We migrate the whole site free, usually within 24 hours, and it keeps serving visitors the entire time.
- Readings you take inside your own CMS
- Renewal rates kept in the open
- Migration included, so test it properly
- Restores you run yourself, at any hour
Why HostingFast
Standard on every plan
The desk, not the homepage
We would rather be judged on admin response time, because that is the number your team experiences all day.
NVMe under the metadata
Post metadata and revision tables grow for years, and storage latency is what decides whether that growth is felt.
Every mainstream engine
WordPress, Joomla and Drupal all sit comfortably on the same plans, so the CMS decision is not constrained by the host.
Turbo, stated plainly
25 sites, 20 GB of NVMe and per-site PHP control at one published rate that does not change at renewal.
Restores without a ticket queue
A daily backup and a self-service restore, because a bad update at four in the afternoon should not become an evening.
Support with a real scope
DNS records, mailbox setup, restores and awkward practical questions — not a reply that says the server is up and closes the ticket.
Prices Side by Side
Our numbers next to the big names
Typical intro and renewal pricing across the market, lined up against ours — including the renewal figure most comparison charts skip.
| Feature | HostingFastMost popular | Typical household-name host | Typical bargain host | Typical loss-leader deal |
|---|---|---|---|---|
| Starting price / mo* | $2.42/mo | $4–$6 | $2–$4 | $1–$3 |
| Renewal price / mo | $2.42/mo | $10–$15 | $8–$12 | $4–$6 |
| Cheapest plan renews at its sign-up price | ||||
| SSL as standard | ||||
| Migration done for you | ||||
| NVMe drives on the cheapest tier | ||||
| Daily backups from the first tier | ||||
| Real humans on support, 24/7 |
*Our number is the lowest-priced plan we sell on an annual term, pulled live from the same catalogue that powers our pricing page — it physically cannot fall out of date. The other three columns show the ranges shared hosts in each bracket typically advertise: introductory offers that mostly demand a one-to-four-year commitment, then jump once it expires. We no longer name rivals or print their prices, because a figure we cannot verify on the day you read it has no business on this page. Line us up against whichever host you are really weighing — and give the renewal row the hardest look.
Quick Start
From order to online
- 1
Time the post list, filtered
Your busiest category, network panel recording, time to first byte on the document. That single figure predicts how the desk will feel.
- 2
Take the same reading at 3pm
Not at midnight. Variance across the working day is what separates a busy machine from a badly packed one, and it never appears in a demo.
- 3
Compare on the renewal figure
Renewal rate times the term, plus every extra you would genuinely enable. Introductory pricing never survives that arithmetic.
- 4
Re-measure with real content
Restore the actual database, not a sample. Eighty thousand posts behave differently from eight hundred, and only one of those is your newsroom.
Built In
Loaded onto every plan
- NVMe SSD under the database on every tier
- OPcache enabled, so admin screens are not recompiled per request
- Object caching available for repeated metadata lookups
- Per-site PHP version switching from the control panel
- Staging copies so an update is tested before the desk meets it
- Daily backups with restores you run yourself from the panel
- Room for WordPress, Joomla, Drupal or whatever you standardise on
- Mailboxes on your own domain included with the plan
- In-place account upgrades — no migration when you change tier
- Human support on duty every hour of every day
Frequently Asked
What people ask us most often
What admin response time should a newsroom accept?
Under 400 milliseconds on a filtered post list feels immediate; a second and a half is where editors start batching their work to avoid the wait, and that is the point at which hosting starts costing you output rather than money. Measure it at your busiest hour, because that is when it matters and when it is worst.
Why did the admin get slower when nothing changed?
Because the database grew. Post metadata, revisions and term relationships accumulate quietly, and a query that scanned a small table now scans a large one. Nothing announces it. The fix is usually an index, a revision limit and object caching rather than a bigger plan — but faster storage makes all three more forgiving.
Does object caching help editors or only visitors?
Editors, mostly. Visitors are largely served from the page cache and never reach the object layer. Editors bypass the page cache entirely, so a memory-backed object cache is the one improvement that lands squarely on the people using the CMS all day — which is the opposite of what most performance advice assumes.
How many people can work in one CMS before it needs more than shared hosting?
Concurrency matters more than headcount. Eight writers drafting is light work; eight writers plus a scheduled import, an image-heavy media library and a live traffic spike is not. Watch for admin response times that climb during your publishing window — that pattern, not a user count, is the signal to move up a tier.
Keep reading
WordPress Hosting for Small Business
What an owner-manager actually needs from a site, costed without the jargon.
Hosting Control Panels Compared
cPanel, Plesk and DirectAdmin judged on what each lets you see and change.
CMS (Content Management System) (Glossary)
The term in plain language, with the practical consequence for a page load.
CMS Hosting
Fast, hardened hosting for WordPress, Joomla, Drupal and every major CMS.
Web Hosting
cPanel hosting on NVMe with SSL, migration and a year-one domain in the price.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Make the editing screen quick.
NVMe under the database, a warm opcode cache and object caching available — measured where your team works.
View CMS Hosting plans