Benchmark notes · Coffee shop sites
Web hosting for coffee shops — Test it cold, on 4G, standing outside the door
Nobody visits a café site twice in a week, so the request that matters is the first one — the one that misses every cache the browser has.
The short answer
A café site is almost always somebody's first and only visit, which makes the cold request the only one worth measuring. Time it with curl -w on the command line, or watch the document row in DevTools with Disable cache ticked; 800 milliseconds of time to first byte is the line between good and slow.
On HostingFast that request is answered from NVMe behind a LiteSpeed cache running out of a London origin, which puts UK and Irish visitors inside a 5–15 ms round trip. Sprint costs $2.42 a month, with SSL, migration and a first-year domain included.
By the HostingFast team · Reviewed 24 August 2026
99.9%
Uptime target, with credit if missed
24/7
Support answering, any hour
Free
SSL on every plan, renewed for you
NVMe
NVMe drives under every tier
The whole job of a café site is to answer four questions before somebody walks past: where you are, when you open, what is on the brew bar and whether you sell beans. None of it is complicated. All of it is time-sensitive.
What makes these sites slow is rarely the content. It is the accumulated third-party furniture — a map iframe, a social feed, a chat bubble, a reviews badge — each one pulling code from a domain you do not control, over a connection you cannot see.
So treat it as a measurement problem. Time the cold request, count what the page fetches from elsewhere, and only then decide whether the hosting is the thing holding you up.
Time the first byte from a cold start
The quickest honest test is one line: curl -o /dev/null -s -w "%{time_starttransfer}\n" against your homepage, run three times, median taken. That figure is time to first byte and it is the part of the page that belongs squarely to the hosting. Under 800 milliseconds is good; a cached page coming off LiteSpeed on NVMe should be far quicker than that.
Run it again with a query string appended so the cache misses, and you have the honest worst case — the request a first-time visitor actually makes. If the two numbers are far apart, the cache is doing the work and an uncached page is where the trouble lives.
Save both figures with the date beside them. You cannot argue with a supplier, or with yourself, from memory.
Opening hours are a data problem
Half the complaints about café sites are not about speed at all: the hours on the page are wrong. Keep them in one place, mark them up as structured data so the search result and the map listing agree with the site, and edit them where they live rather than in three separate widgets.
There is a caching consequence to that. A page held in a server cache is not re-rendered until something invalidates it, so when you change your Sunday hours the cache has to be told. LiteSpeed purges on save for WordPress content; a hand-edited template or a hard-coded footer will happily serve yesterday's hours for as long as you let it.
Count the scripts you did not choose
In DevTools, filter the Network panel by JS and look at the domains. A typical café site pulls in a map, a social feed, a font service, a review badge and a chat widget — five separate connections, each with its own DNS lookup, TLS handshake and execution cost, none of them under your control.
That cost lands in interaction to next paint rather than in the paint metrics, which is why a site can score respectably and still feel sticky under a thumb. Remove one at a time and re-measure. A static photograph linking to your map listing is usually indistinguishable to a visitor and costs a fraction of an embedded map.
What the plan actually buys
Sprint at $2.42 a month carries one site with 10 GB of NVMe, 500 GB of bandwidth and 25 MySQL databases, which is more than a café site will ever ask for. The reason to move up is not speed on a cached page — it is a second site, or a shop.
If you sell beans by subscription, checkout and account pages are uncacheable by definition, and that becomes a CPU question. Turbo at $4.66 covers 25 sites; Nitro at $7.08 brings 200 GB, two cores and 4 GB of RAM, plus PHP X-Ray on CloudLinux Pro for finding the slow query instead of guessing at it.
A London origin and a cache that means it
The platform runs from London, which puts UK and Irish visitors in a 5–15 ms round trip and Western Europe in 10–35 ms. For a business whose customers are within walking distance, proximity is the whole game.
LiteSpeed caching sits inside the web server on every tier, so the pages your visitors read come back without PHP running at all — and the 99.9% uptime target carries a pro-rated credit if a month falls short through a fault on our side.
- London origin: a 5–15 ms round trip across the UK and Ireland
- Server-level LiteSpeed cache, not a plugin approximation
- Free SSL issued and renewed without you touching it
- 99.9% uptime target, credited pro rata if we miss it
Why HostingFast
Standard on every plan
Close to the people who walk in
A London origin means a 5–15 ms round trip for UK and Irish visitors, before any caching is counted.
Cold requests answered quickly
NVMe storage means the first, uncached request is fast too — not only the ones the cache already holds.
Certificates handled quietly
Free SSL issues and renews itself, so the padlock is never something you have to remember.
Room for a beans shop later
Move from Sprint to Turbo or Nitro in place when a basket appears; the account changes, the site does not.
A credit when we miss
The 99.9% uptime target is monitored, and a shortfall caused on our side is credited pro rata under our terms.
People, at three in the morning
Support is staffed around the clock, aiming to reply within two hours, or one when a site is actually down.
Quick Start
From order to online
- 1
Take the cold number
Run curl with time_starttransfer three times against your homepage, then again with a cache-busting query string. Keep both medians.
- 2
Bring it over free
Our engineers migrate the site at no charge, or install WordPress and the drag-and-drop builder in one click and start clean.
- 3
Strip one script, re-measure
Remove a single third-party embed, retest interaction to next paint, and keep whichever version the numbers prefer.
Built In
Loaded onto every plan
- A London origin, published with indicative round-trip times by region
- LiteSpeed caching built into the server rather than patched in by plugin
- NVMe SSD storage on every tier, including the entry plan
- Free SSL on every plan, renewed automatically before it can expire
- 99.9% uptime as the monitored target, with a pro-rated credit in our terms
- Per-site PHP version switching from the control panel
- Softaculous installs 240+ applications in one click
- Mailboxes on your own domain, with spam and virus screening
- Human support on duty every hour of every day
- A renewal price identical to the price you signed up at
Frequently Asked
What people ask us most often
What is a good time to first byte for a café site?
Under 800 milliseconds is the threshold worth holding yourself to, and a cached page served by LiteSpeed from NVMe should come in well below it. Measure it with curl -w "%{time_starttransfer}" rather than by feel, run it three times and take the median, then repeat with a cache-busting query string so you also know the uncached worst case.
Does an embedded map or social feed slow the page down?
It costs execution time rather than your bandwidth, since the code is fetched from someone else's domain and runs in the visitor's browser. The effect shows up in interaction to next paint and in how sticky the page feels under a thumb. Swap an embedded map for a static image linking to the map listing and re-measure — the difference is usually large and the visitor rarely notices.
How do I stop the site showing yesterday's opening hours?
Keep the hours in exactly one place, mark them up as structured data so search and map listings agree with the page, and make sure editing them invalidates the cache. LiteSpeed purges automatically when WordPress content is saved; a hard-coded footer or a hand-edited template does not, and will serve stale hours for as long as the cache lives.
Is the entry plan genuinely as quick as the top one?
For a cached page, yes — NVMe and LiteSpeed are on Sprint at $2.42 exactly as they are on Nitro at $7.08. What the higher tiers add is capacity and headroom: 25 sites on Turbo at $4.66, 200 GB with two cores and 4 GB of RAM on Nitro, plus PHP X-Ray for tracing slow code. Buy those when you have uncacheable pages, not before.
Keep reading
Online Course Creators — Hosting Guide
Course platforms, where logged-in pages cannot be cached and the CPU figure starts to matter.
Membership Sites — Hosting Guide
Members' areas: what a login does to your cache hit rate, and how to plan around it.
Best Hosting With Free SSL
Free certificates on every plan, plus what the TLS handshake costs a first-time visitor.
VPS Hosting — Built for Coffee Shops
When a shared account really is the ceiling, and what root access changes about tuning.
Joomla Hosting
A different CMS, the same measurements — where Joomla spends its server time.
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.
Measure it cold. Then decide.
NVMe behind LiteSpeed from a London origin, $2.42 a month on Sprint, with SSL, migration and a first-year domain included.
View VPS Hosting — Built for Coffee Shops plans