Skip to main content
.com domains from $2.99 — free WHOIS privacy on every name

Throughput Guide

A growing store slows in the half the page cache cannot reach

Your catalogue and order book left the hobby stage a while ago, and the symptom is always the same: the shop front is quick and everything behind the login has started to drag.

The short answer

Turbo Store at $5.59 a month running AccelerateWP with Redis: 2 cores and 4 GB, 20 GB of NVMe, 2 TB of bandwidth and room for 25,000 products — with Nitro Store above it at $9.09 for the season when orders climb.

The reason that tier rather than the entry one is object caching plus concurrency. Redis stores the results of individual database queries, which is the only layer that speeds up the pages WooCommerce forbids a page cache from serving: cart, account, checkout and wp-admin.

By the HostingFast team · Reviewed 15 August 2026

Free

Migration in, at no cost

24/7

Humans answering, any hour

Daily

Backups, every day

$0

Setup fees

A WooCommerce checkout is deliberately excluded from page caching, because every basket differs. That single design decision is why retail speed rests on database throughput and object caching, where a blog would coast on page cache alone.

It also explains the shape of the complaint. Nobody says the store is slow; they say the admin has become unusable and checkout hesitates at peak. Both are the same fault, and both are fixed in the same place.

Find out where the time is actually going

Before buying anything, get evidence. Turn on the MySQL slow query log for a day and read what comes back — on a struggling WooCommerce store it is usually the same two or three queries, often from a plugin building an unindexed lookup across wp_postmeta.

Then check the object cache. With Redis running, redis-cli info stats shows keyspace_hits against keyspace_misses. A hit rate that is not comfortably dominant means the cache is not doing the work you think it is.

On our Nitro tiers PHP X-Ray on CloudLinux Pro will point at slow code directly, which turns a week of guessing into an afternoon of fixing.

The three resources that bind, in order

Database throughput first. Order tables, meta lookups and the admin's order screens are all database work, and NVMe is what stops that becoming disk latency.

Concurrency second. Turbo Store carries 2 cores and 4 GB against Sprint Store's 1 core and 2 GB. That doubling is what keeps a shopper in checkout from queueing behind a stock report running in wp-admin.

Disk last, and only for images. Turbo Store's 20 GB and 25,000-product ceiling is generous; Nitro Store's 200 GB with 3 cores, 6 GB and 100,000 products is a volume decision, not a storage one.

Set the backup interval against your order rate

Backup frequency is a data-loss calculation, not a feature. Losing a day of orders costs something very different at five orders a day than at fifty, and the interval should be set from that arithmetic rather than from the marketing.

Daily backups run on every plan with self-service restores from the panel. Nitro Store shortens that to every 4 hours specifically to compress the exposure window as volume rises, and Nitro on the standard shared range lands every 6 hours.

Whatever the interval, rehearse a restore once on staging. A backup you have never restored is a hypothesis.

Prove the move rather than assume it

Baseline three things before migrating: time to first byte on /checkout with a full basket, the time to load the orders screen in wp-admin, and the slow query count over 24 hours. Repeat all three afterwards on the same URLs.

Migration is free and usually lands within 24 hours, and you review the copy before DNS moves, so the store keeps trading throughout. HostingFast is a trading name of Vitalcare at Home Ltd, registered in England and Wales, if you want the supplier check on file.

A shopper moving through the checkout of a quick online store

The measurements a store owner can run

Slow query log, cache hit rate, checkout time to first byte. Three numbers, none of them requiring a consultant, and together they explain almost every growing-store complaint we are sent.

The rate you sign up at is the rate you renew at, so year two costs exactly what year one did.

  • Redis hit rate, read from redis-cli info stats
  • Slow query log as the first diagnostic
  • Backup interval set against order rate
  • Order rate and renewal rate, identical

Why HostingFast

Standard on every plan

Redis object caching on store plans

The only cache layer that reaches cart, account, checkout and wp-admin — the pages page caching is not allowed to serve.

Turbo Store, specified

$5.59 a month for 2 cores and 4 GB, 20 GB of NVMe, 2 TB of bandwidth and room for 25,000 products.

Four-hourly backups on Nitro Store

A shorter exposure window as order volume rises, with Imunify360 in front and restores you run yourself.

PHP X-Ray on the Nitro tiers

CloudLinux Pro profiling that names the slow code instead of leaving you to bisect plugins by hand.

Staging before every plugin update

A new gateway or shipping plugin meets a test order somewhere private before it meets a paying one.

Upgrading is an account change

Sprint Store to Turbo Store to Nitro Store with no migration, so a strong season is a setting rather than a project.

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.

HostingFast pricing and features lined up against three other hosts
FeatureHostingFastMost popularTypical household-name hostTypical bargain hostTypical 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. 1

    Turn on the slow query log for a day

    Read what comes back. On most struggling stores the same two or three queries dominate, and they usually belong to one plugin.

  2. 2

    Check the Redis hit rate, not just that Redis exists

    redis-cli info stats gives keyspace hits against misses. An object cache that is installed but missing constantly is doing nothing for your checkout.

  3. 3

    Set the backup interval from your order rate

    Work out what a lost day costs at your current volume. If the answer is uncomfortable, Nitro Store's four-hourly interval is the specification that answers it.

Built In

Loaded onto every plan

  • Redis object caching and AccelerateWP on every store tier
  • 2 cores and 4 GB on Turbo Store, rising to 3 cores and 6 GB on Nitro Store
  • NVMe SSD storage behind a LiteSpeed cache
  • Backups every 4 hours on Nitro Store, daily across the rest
  • PHP X-Ray on CloudLinux Pro for pinpointing slow code on the top tier
  • Staging copies for testing a plugin stack against a test order
  • SSH, WP-CLI and Git for whoever maintains the theme
  • Free always-on SSL with HTTPS end to end for the PCI questionnaire
  • In-place upgrades between store tiers with no migration
  • Free store migration from your current host, usually within 24 hours

Frequently Asked

What people ask us most often

Why did my store slow down as it grew, when the home page is still fast?

Because growth loads the uncacheable half. Cart, account, checkout and wp-admin bypass the page cache entirely and go straight to PHP and the database, so they scale with orders rather than with visitors. Redis object caching plus more concurrency repairs exactly what another caching plugin cannot reach.

How do I tell whether Redis is actually helping?

Run redis-cli info stats and compare keyspace_hits with keyspace_misses. Installed-but-missing is a common state, usually because the object cache drop-in was never activated or is being flushed constantly by a plugin. A dominant hit rate is the evidence; the presence of Redis on the feature list is not.

What backup interval does a store at fifty orders a day need?

Work out what losing a day of orders costs you and set the interval from that. Daily backups run on every plan with self-service restores. Nitro Store shortens the interval to every 4 hours precisely to compress that exposure as volume rises, and Nitro on the standard range runs every 6 hours.

Which resource should I add first when checkout hesitates?

Database throughput and concurrency, in that order — not disk. Order tables and meta lookups are database work, which is why NVMe matters, and a second core is what stops a shopper in checkout queueing behind an admin report. Storage is almost never the constraint on a store that is otherwise well built.

Keep reading

  • Drupal Hosting Plans

    A Composer-era platform judged on deployment mechanics rather than on how many plugins exist for it.

  • Game Server VPS

    Sizing arithmetic for a workload where latency is the product rather than a nice-to-have.

  • How to Install WooCommerce

    Installing the plugin, then the settings that decide whether checkout stays quick.

  • WooCommerce Hosting

    Store hosting with Redis object caching, and four-hourly backups once order volume justifies them.

  • Web Hosting

    cPanel hosting on NVMe behind LiteSpeed, with the database on fast storage rather than SATA.

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.

You'll get the checklist email, then occasional pointers on keeping a site running fast. Unsubscribe the moment you want out — the privacy policy covers the rest.

Fix the half the cache never reached.

Redis and AccelerateWP on every store plan, four-hourly backups on Nitro Store, free migration and a flat renewal figure.

View WooCommerce Hosting plans