Two-market brief · Istanbul
Istanbul: measure it from both ends
A textile or machinery catalogue is read in Istanbul and in Stuttgart, and a single speed score describes neither of them accurately.
The short answer
An Istanbul exporter has two audiences with different round trips, so one measurement is not enough. Türkiye sits in the Eastern Europe and Turkey band we publish for the London origin at 30 to 60 milliseconds; the German buyer reading the same catalogue is in the Western and Northern Europe band at 10 to 35. Test from both, or you are tuning for whichever half you happened to sample.
The good news is that the fix is shared. A cached catalogue page is prepared once and answers both audiences without PHP running, so cache coverage does more for the pair of them than any per-market tinkering. What differs is the enquiry path, which is uncached and therefore feels the distance on every step.
By the HostingFast team · Reviewed 15 August 2026
99.9%
Availability target
24/7
Engineers on shift
Free
SSL, every plan
NVMe
Drives as standard
Textiles, machinery, furniture and food leave this city for Europe, the Gulf and Africa in the same week, which means one catalogue is read in four currencies at once. On top of it sits one of the largest gaming and startup scenes in the region, staffed by graduates who could work anywhere.
That dual audience is the engineering brief. What follows: how to measure from two places without guessing, what a large catalogue costs when it is not cached, where the second language does and does not slow things down, and how the enquiry path behaves across a border.
Two audiences, two measurements
Read the field data in PageSpeed Insights first, because it is aggregated from real Chrome users and therefore already includes both audiences whether you meant it to or not. Then take a deliberate lab reading from each side: a run with the test location set in Europe, and one from your own office connection in Istanbul.
The gap between them is the distance, and it is smaller than most people expect once the page is cached. What is usually larger is the gap between a cached page and an uncached one, which is the same on both sides of the border and is the thing actually worth fixing.
A big catalogue, uncached, is the real cost
A machinery catalogue with thousands of variants and a faceted filter is genuine database work. Load the slowest listing page as an administrator with Query Monitor and sort by duration: unindexed filtering across a meta table is the usual answer, and it costs the visitor most of a second while producing nothing visible in the markup.
Index the columns the filters search, cache the expensive fragment, and let the server cache hand the finished page to everyone who is not logged in. Then remove the diagnostic. NVMe storage and 100 MySQL databases on the top shared tier give you the room; the queries are what decide whether you need it.
The second language, honestly assessed
Turkish and English as parallel trees under hreflang cost nothing at runtime. Two trees mean twice the cache entries, which is a warming and storage question rather than a speed one, and it only becomes interesting immediately after a global purge.
Arabic is the one that carries a real cost, and it is the fonts rather than the direction. A right-to-left layout is a stylesheet property; an Arabic webfont with full coverage is a large file. Subset it, self-host it so it arrives on the connection already open, and measure the page before and after rather than assuming either way.
The enquiry path across a border
A quote request is a POST and cannot be cached, so every step of it makes the full round trip. Keep it short, hand off cleanly to whatever system actually processes the enquiry, and give the confirmation screen its own URL so completion is measurable rather than assumed.
Route the confirmation mail through the platform's outbound mail — MailChannels handles delivery on every plan — because an enquiry that succeeds and never arrives looks exactly like one that failed. Domestic trust runs through .com.tr and the newer direct .tr, with a .com alongside for the international line, all registered on the same account with one renewal date.
What serves both markets at once
One origin, one cache: LiteSpeed built into the server so a catalogue page prepared for a buyer in Istanbul is handed unchanged to one in Stuttgart an hour later.
NVMe storage under the queries that cannot be cached, per-site PHP switching, and SSH with Git and Composer for the people who read a slow query log.
- One cached catalogue serving both audiences
- SSH with Git and Composer for slow-query work
- MailChannels handling outbound enquiry mail
- .com.tr or .tr registered on the hosting account
Why HostingFast
Standard on every plan
One cache, both markets
A server-level cache prepares a catalogue page once and serves it to domestic and export buyers alike, without PHP running for either.
Database room to grow into
Up to 100 MySQL databases on the top shared tier, with NVMe underneath, so a large variant catalogue has somewhere to live.
Shell access for the diagnosis
SSH with Git and Composer on the developer-focused plans, so a slow query log is something you read rather than request.
Enquiry mail that arrives
Outbound mail goes through MailChannels rather than the theme's default mailer, so a quote request reaches the person who sent it.
Flat renewals in USD
Plans bill in USD at a rate that renews unchanged, so the hosting line stays predictable when other costs are not.
Support in both business days
Engineers on shift around the clock, first reply inside two hours and inside one when a site is down, covering both your markets' hours.
Quick Start
From order to online
- 1
Measure from both sides
Field data first, then one deliberate lab run from Europe and one from Istanbul. The gap between them is the distance; the rest is yours.
- 2
Index what the filters search
Query Monitor on the slowest catalogue page, sorted by duration, then indexes and a cached fragment. Remove the diagnostic afterwards.
- 3
Shorten the quote path
Fewer uncached steps, a clean hand-off, a distinct confirmation URL, and delivery through the platform's outbound mail.
Built In
Loaded onto every plan
- LiteSpeed caching inside the server rather than added by plugin
- NVMe throughout, from the entry plan upward
- Up to 100 MySQL databases on the top shared tier
- SSH, Git and Composer on the developer-focused plans
- Per-site PHP version switching from the control panel
- MailChannels handling outbound mail on every plan
- A renewal price identical to the one you signed up at
- In-place tier upgrades, with no migration when you change plan
- Free SSL on every plan, reissued before it can lapse
- Human support on duty at every hour both markets trade
Frequently Asked
What people ask us most often
Should we run separate sites for the domestic and export markets?
Rarely, and not for speed reasons. One site with Turkish and English trees under hreflang serves both from the same cache, which is cheaper to run and easier to keep consistent. Separate sites start earning their keep only when the product ranges themselves diverge, at which point the split is a commercial decision rather than a performance one.
How do I test what a German buyer actually experiences?
Set the test location in your measurement tool rather than trusting your office connection. A lab run from a European location plus the field data in PageSpeed Insights gives you both halves. The field figures already blend your real audiences, which is why they are the number to quote when somebody disputes the lab result.
We are adding Arabic. What will that cost the page?
The layout direction costs nothing — it is a stylesheet property. The typeface is where the weight is: a full-coverage Arabic webfont is a large file, so subset it to the ranges you actually set, self-host it so it arrives on the connection already open to your site, and measure the page before and after. Half-finished Arabic is worse than none, so budget the translation as well as the bytes.
Does the currency moving affect what we pay for hosting?
Plans are billed in USD at a flat rate, and renewals bill at the same figure as your original order, so the hosting line does not move even when other costs do. That predictability is most of the appeal here, and it is worth more than an introductory discount that quietly expires after a year.
Keep reading
Web Hosting in Zurich
Zurich, and the same catalogue argument on an entirely gated workload.
Web Hosting in Manchester
Manchester, where an export-facing site sits in the shortest latency band.
Best Domain and Hosting Together
Buying a name and hosting together, weighed up with a verdict at the end.
Agency Hosting
Client accounts, staging and care-plan infrastructure built for agency workloads.
cPanel Reseller Hosting
The industry-standard panel scaled for resellers, with WHM included.
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.
Test it from both ends.
One cached catalogue for two markets, NVMe under the queries that cannot be cached, and shell access to prove it.
View Agency Hosting plans