Storefront Buying Guide
Magento hosting for small retailers — Magento tells you what it needs. Most buyers never ask
The catalogue page is cached and the admin panel is not, which is why the admin panel is where under-provisioning shows up first.
The short answer
Size the server from the admin panel, not the storefront. Put it on a correctly sized VPS with Redis, a search service and NVMe underneath; Magento rewards real infrastructure and punishes economising in the most visible way available — and the admin panel is where that punishment lands first, weeks before a customer notices.
Below: where a Magento request actually spends its time, the two timings that size the machine, the caching that makes a demo look fast and a business feel slow, and the plan we would put a small catalogue on.
By the HostingFast team · Reviewed 24 August 2026
99.9%
Uptime target, monitored
24/7
Engineers on duty
Free
SSL on every plan
NVMe
Drives, every tier
Written for merchants already committed to Magento who want the sizing question answered with a stopwatch rather than a sales call. If you can time a product save and a category load, you can size this correctly.
A dedicated search service is a hard dependency in Magento 2 rather than an enhancement — catalogue browsing itself runs through it. Any plan making no provision for Elasticsearch or OpenSearch is not Magento hosting, whatever the marketing copy claims.
Where a Magento request actually goes
A cached category page barely touches the application: the full-page cache answers it and the storefront looks quick, which is precisely why storefront timings mislead everybody who buys on them.
An uncached request is a different animal. It runs the layout XML, resolves the block tree, queries the catalogue and hits the search service, and it is where PHP memory and worker count are consumed. Cart, checkout and any customer-specific block take this path on every hit.
The admin panel takes it too, and takes it hardest. Every screen is assembled from scratch, the grids are query-heavy, and setup:di:compile and the indexers run flat out on the same machine as your customers.
So there are three workloads on one box with wildly different profiles, and only one of them appears in a demo.
Two timings that size the machine
Time a product save from the admin with the browser's network panel open. Under three seconds is healthy on a small catalogue. Past ten, the machine is under-provisioned and your staff are paying for it in working hours every day.
Then time an uncached category page: append a cache-busting parameter, or flush and reload once, and measure time to first byte. That figure is what a customer sees on the first visit of the day and after every deploy.
If either number is bad, look at PHP memory and worker count before you look at CPU. Magento's own tooling documents a substantially higher command-line memory limit than a typical web request needs, and an under-provisioned box announces itself by timing out in the admin rather than by pegging a core.
The caching that flatters a demo
Full-page cache plus Varnish makes any Magento install look excellent in a screenshot. It does nothing for the checkout, nothing for the admin and nothing for a signed-in customer with a cart, which between them are the pages that turn into money and payroll.
The related mistake is forcing Magento onto an entry-level shared plan. The installation will complete, the homepage will cache, and every uncached page load afterwards makes the decision obvious to staff and customers alike.
Measure the uncached paths. A platform that only looks fast when it is not doing any work is not fast.
What we would put a small catalogue on
Our Torque VPS option is where this page lands: root access, memory you allocate rather than share, Redis for cache and sessions, and NVMe under the database — with DDoS filtering absorbed at the network edge and snapshots you can take before a risky deploy.
Provision it, restore a copy of the real catalogue, and re-run both timings. Product save and uncached category, same catalogue, same time of day. That is the only comparison worth making.
Note the commercial terms honestly: VPS and dedicated servers are built to order and sit outside the money-back window, which is exactly why we would rather you tested with measurements than with optimism.
Why this page has no affiliate table
Most 'best hosting' content is ranking-for-hire. We sell the thing we are writing about and say so, which frees the page to be about timings and provisioning rather than a leaderboard.
Order an annual plan and the first year of your domain registration costs you nothing.
- Timings you can take on your own catalogue
- No introductory rate waiting to expire
- Snapshots on demand before a risky deploy
- Refund terms stated including the exclusions
Why HostingFast
Standard on every plan
Memory you allocate, not share
Magento's appetite is real, and a VPS lets you give PHP the headroom the indexers and the admin grids actually need.
NVMe under the database
Catalogue queries are disk-bound long before they are CPU-bound, which makes storage latency the lever that matters.
Snapshots before you deploy
Take one on demand, run the upgrade, and roll back in minutes if the indexers disagree with you.
Filtering at the edge
DDoS traffic is absorbed on the network in front of the hypervisor rather than in your PHP worker pool.
Exclusions stated up front
VPS and dedicated servers are built to order and fall outside the refund window — we would rather print that than bury it.
An upgrade that is not a migration
Shared, VPS and dedicated on one platform, so a growing catalogue is an account change rather than a rebuild.
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 a product save
Network panel open, one real product with its images. Under three seconds is healthy; past ten you are watching an under-provisioned machine cost you staff hours.
- 2
Time an uncached category page
Bust the cache and measure time to first byte. That is the figure a first-time visitor and every post-deploy visitor actually experiences.
- 3
Count the services, not the gigabytes
PHP-FPM with real memory, MySQL with room, Redis for cache and sessions, and a search service. A plan missing any of the four is not a candidate.
- 4
Re-run both timings after the move
Same catalogue restored, same time of day, same connection. Two numbers, before and after, and the decision defends itself.
Built In
Loaded onto every plan
- Elasticsearch or OpenSearch provisioned, because 2.4 requires it
- Redis available for cache and session storage
- PHP memory sized for the indexers, not just for a page view
- NVMe SSD under MySQL rather than spinning disk
- Root access for the deploy and compile steps
- Snapshot backups you can take on demand before an upgrade
- DDoS filtering absorbed out at the network edge
- Staging copies so an upgrade is tested before it is trusted
- Renewal charged at the rate you ordered at
- Human support on duty every hour of every day
Frequently Asked
What people ask us most often
Why is my admin panel slow when the shop feels fast?
Because the shop is cached and the admin is not. Every admin screen is composed on request, the grids run heavy queries, and the indexers compete for the same CPU. If your storefront is quick and your product save takes fifteen seconds, that is not a paradox — it is the full-page cache doing its job and hiding how little machine is underneath it.
How much memory does a small Magento catalogue really want?
Think in services rather than a single figure. PHP-FPM needs generous per-process memory, MySQL needs a buffer pool large enough to hold the hot part of the catalogue, and Redis needs room for sessions and cache. In practice that adds up to 4 GB or more of VPS for a small catalogue, and the first symptom of getting it wrong is an admin panel that times out.
Which indexers should be on schedule rather than on save?
Nearly all of them, once the catalogue passes a few hundred products. Update-on-save turns every product edit into a full reindex while a customer is browsing, which is how a routine price change becomes a five-minute outage. Set them to update by schedule and let cron absorb the work between peaks.
Is Varnish worth adding, or is the built-in cache enough?
Varnish is genuinely faster for anonymous traffic and irrelevant for everything else. If most of your visitors browse without a cart, it is worth the complexity. If most arrive from email into a signed-in session, spend the same effort on database latency and PHP workers instead — that is where those requests are actually spending their time.
Keep reading
Reseller Hosting for Agencies
Turning delivered client projects into recurring revenue, with the operational cost written out.
Reseller Hosting vs Affiliate Programs
Owning the customer against handing them over, compared on what each actually pays.
Uptime (Glossary)
What uptime figures mean in practice, and what they quietly exclude.
Magento Hosting
Plans with the memory and PHP headroom Magento actually demands.
VPS Hosting
KVM virtual servers with root access, snapshots on demand and one flat monthly rate.
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.
Give the catalogue room to work.
Root access, real memory, Redis and NVMe under the database — provisioned the moment payment lands.
View Magento Hosting plans