Load Profile
Multilingual site hosting — Languages multiply your cache, not your traffic
Every extra locale copies your page count and your cache footprint, while the cost of serving any individual visitor stays exactly where it was.
The short answer
Build multilingual WordPress on subfolders and host it on Turbo: one installation, correct hreflang, 20 GB of NVMe and headroom for the cache entries that multiply with every locale you add. Subfolders keep all the links and signals on one domain, which is the structural decision everything else follows from.
Below: how to verify hreflang instead of trusting the plugin that generated it, what translation machinery genuinely costs in queries and cache entries, why the admin slows before the front end does, and what regional speed really depends on.
By the HostingFast team · Reviewed 24 August 2026
99.9%
Uptime target we monitor
24/7
Humans on support, any hour
Free
SSL, issued and renewed
NVMe
Drives, entry tier included
Placing each language under a subfolder such as /fr/ or /de/ concentrates every link and every signal on one domain, whereas subdomains and country domains divide that authority between them. Make subfolders the default unless a legal or market reason overrides it — and if one does, know which reason it is.
The hosting consequence is specific and easy to underestimate. Five languages means five times the pages, five times the cache entries and five sets of translated strings in the database, while the cost of serving one visitor one page has not changed at all. That is a storage and cache-footprint question, not a capacity one.
Verify hreflang rather than trusting the plugin
View the rendered source of a translated page and check three things: every language version is listed, each page includes a self-referencing tag, and the codes are valid. Then open the corresponding French or German page and confirm it points back. Reciprocity is the requirement people most often fail — a page that links out without being linked to is ignored.
Add an x-default for the version you want shown when no language matches, and be careful with region codes: a language code alone covers everyone reading that language, while a language-region pair narrows it to one country. Choosing the second by accident quietly excludes most of your audience.
Check it after every structural change. Plugins regenerate these tags, and a redirect rule added six months later is a common way for reciprocity to break without anything visibly going wrong.
What the translation machinery actually costs
Translation plugins of the WPML and Polylang class store strings in additional tables and join against them on request. Cached front-end pages barely notice, because the cache answers before any of that runs. The admin notices a great deal, since nothing there is cached and every screen carries the extra joins.
So measure the admin, not the home page. Time a post list and a page save with one language active and again with five. If the second figure is materially worse, object caching is the intervention that will help — this is one of the genuine cases where Redis earns its place rather than being added out of habit.
Watch the cache entry count as well as the disk. Every locale multiplies the number of stored pages, and a cache that quietly starts evicting entries produces a site that is fast in the language you test in and slow in the ones you do not.
The plan we would run it on
Build multilingual WordPress on subfolders and host it properly — one installation, correct hreflang, and the translation budget concentrated on the languages your audience actually reads.
In our line-up that is the Turbo plan: 20 GB of NVMe, up to 25 sites, 1 TB of bandwidth, SSL, migration and mail already in, renewal charged at the order rate, and an upgrade path so this decision never has to be re-run from zero.
Backups run daily on every plan, and restoring a file or a database is a single click in the panel rather than a support ticket.
Regional speed is a caching problem
Our origin is in London, and the indicative round trip is 5 to 15 milliseconds from the UK and Ireland, 10 to 35 across Western and Northern Europe, and 160 to 230 from Southeast and East Asia. Cached pages absorb that distance well; anything uncached pays it in full, which is why an edge network helps readers and does nothing at all for your editors.
Machine-translating your way into a heap of thin near-duplicate pages is the other trap — search engines reward genuine localisation and quietly discount convincing imitations of it. Concentrate the budget on the two or three languages your analytics say people actually read, and translate those properly.
Storage and cache, not capacity
The instinct is to buy a bigger plan when a second language arrives. The measurement usually says otherwise: what grows is the cache footprint and the admin's query load, and both have specific, cheaper fixes.
NVMe storage and LiteSpeed caching power every tier from the smallest plan up — the extra locales come off the same fast path as the original one.
- Check reciprocity, not just presence
- Time the admin at one language and at five
- Watch cache entries, not only disk usage
- Subfolders unless a real reason says otherwise
Why HostingFast
Standard on every plan
Room for the cache to multiply
20 GB of NVMe on Turbo, which is what actually grows when a fourth and fifth locale arrive.
Object caching where it earns it
Redis is available for the uncached admin queries that translation plugins genuinely add — the rare case where it is not cargo cult.
Staging for structural changes
URL structure and hreflang changes are exactly the sort of thing to rehearse on a clone before they reach a live index.
One installation, many languages
Subfolders under a single site rather than several installs to keep in sync, patch and back up separately.
A company on the record
Vitalcare at Home Ltd, registered in England and Wales — the same supplier whichever markets you publish into.
One rate, order and renewal
Adding a language does not change the plan price, and the plan price does not change at renewal.
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
Audit the tags in both directions
From the English page to the French one, and from the French page back. Reciprocity is the requirement most installations fail.
- 2
Time the admin, not the home page
Post list and page save at one language and at five. That gap is what translation machinery actually costs you.
- 3
Track cache entries per locale
Eviction shows up as a site that is fast in the language you test and slow in the ones you do not.
Built In
Loaded onto every plan
- A daily backup, restored from the panel without a ticket
- Money-back cover: 30 days on hosting plans, 7 on reseller
- Spam and virus screening applied to every mailbox by default
- Full SSH with Git and Composer, not a restricted shell
- Mailboxes running on your own domain name
- No setup fee — there is no joining charge, ever
- WebP conversion handled server-side at no extra cost
- Free SSL that reissues itself well before expiry
- DDoS filtering absorbed out at the network edge
- Renewal billed at the rate you ordered at
Frequently Asked
What people ask us most often
How do I check hreflang is reciprocal?
Open the rendered source of the English page and note every alternate it lists. Then open one of those pages and confirm it lists the English one back, plus a self-referencing tag of its own. One-way tags are the most common fault and they are ignored rather than reported, so nothing tells you it is wrong except the absence of results in that market.
Does an extra language double the hosting requirement?
No — it multiplies pages and cache entries, not the cost of serving each visitor. Storage and cache footprint grow with each locale; per-request work does not. A mid-tier plan carries several languages comfortably, and the genuine expense of going multilingual is paying people to translate well rather than paying for capacity.
Why is the admin slower on a multilingual install?
Because nothing in the admin is cached, and translation plugins add tables and joins that every screen has to walk. The front end is protected by the page cache; the editor is not. Time a post list and a page save with one language and with five — if the difference is significant, object caching is the fix that addresses the actual cause.
Do I need a server in each country I publish to?
Almost never. Cached pages absorb distance well, and an edge network handles the rest for logged-out readers. What distance genuinely costs you is uncached work — the editor experience, and anything dynamic — so the honest answer is to cache aggressively, put an edge network in front, and accept that admin sessions from the far side of the world will feel the miles.
Keep reading
Laravel Hosting Plans
Deploying a Laravel application without adopting DevOps as a second profession.
White-Label Hosting Platforms
Reselling under your own name, and what you inherit from the platform underneath it.
Uptime (Glossary)
What an uptime figure covers, what it excludes, and how it is actually monitored.
Web Hosting
cPanel hosting on NVMe with SSL, free migration and a year-one domain included.
VPS Hosting
KVM virtual servers with root access, DDoS filtering and one flat monthly 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.
Publish in five languages.
NVMe with room for the cache to grow, Redis where it genuinely helps, and a renewal rate that matches the order rate.
View Web Hosting plans