Performance profile · Translators & Language Services
Web hosting for translators — What each extra language actually costs the server
A multilingual plugin turns one site into three, and the cost lands in the database, the cache and the disk — none of which shows up in a homepage score.
The short answer
Every language you add multiplies three things: rows in the database, entries in the page cache, and the work a plugin does on each request to decide which version to serve. Two languages roughly doubles the cache footprint; the fix is not a bigger plan but sane cache variants, one language switcher, and the collation set correctly from the start.
The second half of the job is the quote form. Translation is priced from a document, so `upload_max_filesize`, `post_max_size` and `max_execution_time` all need raising — they are per-site settings in the panel here — and a scanned 20 MB contract should reach you rather than failing silently on a phone.
By the HostingFast team · Reviewed 24 August 2026
24/7
Support, any hour
1-click
To install WordPress
Free
SSL, issued and renewed
Daily
Backups, every day
A multilingual site is not one site with extra text. The plugin adds a translation table, filters most queries, and produces a separate cached copy of every URL per language. That is all perfectly manageable, but it is real work, and it is why a two-language site can be measurably slower than the single-language version it grew out of.
Measure it directly rather than in the abstract. Time the same page in each language with five `curl -s -o /dev/null -w '%{time_starttransfer}'` runs and compare medians. Then time one of them with a cache-busting query string to see the uncached cost. If one language is slower than the others, something in the switching layer is doing work it should not.
The other half of this page is about characters. Get the database collation wrong and accented characters survive right up until somebody searches for them, at which point the bug appears in exactly one language and nobody can reproduce it.
One page, three cached copies
A page cache stores finished HTML keyed by URL, so a site in three languages holds three copies of everything. That is fine — storage is cheap and Sprint carries 10 GB of NVMe — but the cache warms three times more slowly, and a purge on publish clears three entries rather than one. Expect a lower hit rate in the days after a big content change.
Keep the language switcher simple. A switcher that resolves the alternate URL by querying the database on every page view puts work into the one path that was supposed to be free. Time a cached page in each language; if one is consistently slower, that is where to look, and no amount of extra CPU will make an unnecessary query fast.
The database grows in two directions
Translated posts, translated meta, and the mapping table between them: a plugin like this adds rows in proportion to languages times content, and the queries it filters are the ones your archive and search pages already run. Sprint's 25 MySQL databases are ample in number; the pressure is query time, and Redis object caching is the layer that answers it because it stores individual query results rather than pages.
Set the collation properly before you have data. `utf8mb4` handles the full range — accented Latin, Cyrillic, Greek, CJK and emoji — while an older character set will store some of it and mangle the rest. Getting this wrong is a migration to fix later and a two-minute decision now.
The quote form has to accept a real document
Clients send scanned certificates, contracts with graphics and slide decks, and a word count decides the quote, so the file has to arrive. Raise `upload_max_filesize` and `post_max_size` together — both have to clear the file size — and give `max_execution_time` room for a slow mobile upload to finish. All three are per-site settings you change from the panel.
Then break it deliberately: upload a 20 MB PDF yourself and watch what happens. If it fails, the message the client sees matters as much as the limit — a generic error reads as your business being broken. Confirm receipt on screen and by email, and check that the confirmation authenticates: SPF, DKIM and DMARC are configured here, with MailChannels handling outbound delivery.
Serving readers who are not in the UK
The origin is in London. From a UK or Irish connection that is a 5 to 15 ms round trip; from Western Europe 10 to 35 ms; from South Asia the round trip runs to roughly 200 ms, which cached pages absorb well and the control panel does not. If a meaningful share of your clients are far away, put a CDN in front and understand what it does: cached HTML and static assets travel, logged-in screens and uncached requests still run the full distance.
That distinction decides where to spend. A CDN improves the reading experience for a distant audience and does nothing for your own admin session, which is the thing you will actually notice. Measure both before you buy, and choose knowing which one you were fixing.
Built for sites that carry more than one language
Multilingual sites want three things: fast uncached queries, per-site PHP settings you can change yourself, and enough disk for cache copies and client documents.
All three are standard on HostingFast — NVMe storage on every tier, PHP version and limits controlled from the panel, and Redis object caching on the WordPress plans for the queries a page cache cannot help with.
- NVMe storage for the translation tables a page cache never touches
- Redis object caching on the WordPress tiers
- Per-site PHP upload and execution limits, changed from the panel
- utf8mb4-capable MySQL, so accented characters survive a search
Why HostingFast
Standard on every plan
Room for three copies of everything
Cache entries multiply per language. NVMe storage on every tier, and 10 GB to 200 GB depending on plan, keeps that a non-issue.
The cache that survives translation
Redis object caching stores query results, which is what speeds up the filtered queries a multilingual plugin adds.
Uploads sized for real documents
Raise upload_max_filesize, post_max_size and max_execution_time yourself, then prove it with a 20 MB scanned contract.
Characters that stay intact
MySQL with utf8mb4 support, so accented and non-Latin text survives storage, search and export without mangling.
Distance stated honestly
A London origin: 5 to 15 ms from the UK, 10 to 35 ms from Western Europe, and roughly 200 ms from South Asia.
Quote confirmations that land
SPF, DKIM and DMARC configured with MailChannels on outbound mail, so a document received is a document acknowledged.
Quick Start
From order to online
- 1
Time the same page in every language
Five curl runs per language, medians compared. A language that is consistently slower is a switcher doing unnecessary work.
- 2
Set the collation before the content
Confirm the database is utf8mb4 at the start. Fixing character corruption after two years of translated content is a migration, not an edit.
- 3
Upload a 20 MB document to your own form
If it fails, raise the three PHP limits from the panel and try again. Then check the confirmation email authenticates.
Built In
Loaded onto every plan
- NVMe storage on every tier for multiplied cache entries
- Redis object caching and AccelerateWP on the WordPress plans
- Per-site PHP version, upload and execution limits from the panel
- MySQL with utf8mb4 for accented and non-Latin characters
- SPF, DKIM and DMARC configured, MailChannels on outbound mail
- Daily backups with self-service restores from the panel
- Staging copies for testing a multilingual plugin upgrade
- Softaculous installs WordPress and 240+ applications in one click
- Money-back cover: 30 days on hosting plans, 7 on reseller
- In-place upgrades from 10 GB through 20 GB to 200 GB of NVMe
Frequently Asked
What people ask us most often
Does adding a second language make the site twice as slow?
Not twice, but it is not free either. You get a second cached copy of every URL, extra rows in the database and a plugin filtering most queries. Time the same page in each language with five curl runs; if one language is consistently slower, the language switcher is doing work on a path that should be served from cache.
Which database collation should a multilingual site use?
utf8mb4, decided before you have content. It covers accented Latin, Cyrillic, Greek, CJK and emoji. An older character set stores some of that and corrupts the rest, and the symptom often does not appear until somebody searches in one particular language. Changing it later means converting tables rather than flipping a setting.
Why does my quote form reject a scanned contract?
Because at least one of three PHP limits is too low: upload_max_filesize, post_max_size or max_execution_time. All three are per-site settings you change from the panel here. Raise the first two together, because a 20 MB file needs headroom in both, and give the third room for a slow mobile connection.
Will a CDN help clients in another continent?
For reading, yes: cached HTML and static assets get served from an edge node near them. For you, no: the control panel, the editor and any uncached request still travel the full distance to the London origin. From South Asia that is a round trip of roughly 200 ms, which cached pages absorb and admin work does not.
Keep reading
Videographers — Hosting Guide
A media-heavy workload where the bottleneck is file size rather than query filtering.
Yoga Studios — Hosting Guide
A booking-led site with the same uncached-form problem and no translation layer.
How to Test Your Website Speed
The exact timing method used above, with the commands and thresholds spelled out.
Domain Names — Built for Translators
Register or transfer the names your language versions live on, first year free on annual plans.
VPS Hosting
Full root access on a KVM virtual server if a translation memory or CAT tool needs its own stack.
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.
Time each language.
Five curl runs per language and one oversized test upload tell you what the translation layer is really costing.
View Domain Names — Built for Translators plans