Roaming profile · Lisbon
Lisbon hosting, judged from someone else's network
Your first visitor of the day is on a foreign SIM, roaming, on a train, and your last speed test was run on office fibre in Alcântara.
The short answer
Test from the connection that decides your bookings, not the one on your desk. A roaming handset in another country gives you high latency, variable bandwidth and a cold cache all at once, so measure it with a synthetic probe in the visitor's market plus DevTools throttling for the payload — two readings, clearly labelled.
The origin side is settled: Portugal sits inside the 10–35 ms band we publish for Western Europe, and every plan runs NVMe storage behind a LiteSpeed cache built into the server, so pages arrive pre-built rather than being generated per request. Free SSL, free migration and support at any hour come with it.
By the HostingFast team · Reviewed 12 August 2026
NVMe
Storage on every tier
Free
Domain, year one
99.9%
Uptime target, monitored
Flat
Renewal, unchanged
Web Summit made this a fixture on the technology calendar and the founders and remote workers who came for it kept arriving. Around them a tourism boom reshaped whole neighbourhoods and turned local hospitality into an internationally marketed business with an internationally distributed audience.
So this page is written from the visitor's connection inwards: what a roaming phone experiences, what caching removes, where a short-let booking flow stops being cacheable, and what changes when you move country but keep the domain.
What a roaming visitor actually gets
Three things at once: a longer path than your test, bandwidth that changes between one carriage and the next, and no warm cache in the browser. That combination punishes payload far more than it punishes distance, which is why a heavy page fails on a foreign SIM while feeling fine at your desk on the same origin.
So produce two readings and label them. A synthetic run from a probe in the visitor's market shows connect time, start render and LCP over a realistic path. DevTools with a slow 4G profile and CPU slowdown shows what a throttled handset does with your bytes while keeping your own routing. Different questions, different answers, and quoting one as the other is how bad decisions get funded.
10–35 ms from the Atlantic edge
Portugal sits inside the band we publish for Western and Northern Europe: 10–35 ms round trip to our London origin, indicative for a well-connected consumer network. Against the 800 ms Google treats as a good time to first byte, the geography is spending a few per cent, and a server in Lisbon would not measurably change what a visitor perceives.
What does change it is whether the page existed before the request. A cache hit costs the round trip plus the server's handling; a miss costs the round trip plus a full application boot and whatever the theme does before it emits HTML. Request the page twice and read the cache header on the second response — that one check settles most arguments about this band.
Short-let booking: the uncacheable tail
The property pages, the photographs and the neighbourhood guides cache perfectly. The availability calendar, the price calculation and the payment step do not — they are personal and transactional, so each one runs the full round trip plus a render. On a 10–35 ms band that is comfortable; on a roaming connection with 300 ms of its own, every extra step is felt.
Cut steps rather than hoping. One form instead of a wizard, browser-side validation so nothing travels to be rejected, and an availability call made once rather than on every keystroke. The php.ini limits that a slow provider API needs — max_execution_time, memory_limit — are per-site panel settings you can change in two minutes.
Moving country without moving the site
This is the practical benefit of owning your own domain: the site, the mailboxes and the address travel with you regardless of which country you are billing from. Add Portuguese contact details, register a .pt if local clients matter to the mix, and nothing about the hosting arrangement has to change.
Keep it tidy while you do it. One canonical hostname, everything else 301ing to it in exactly one hop, verified with curl -sIL. And keep registration on the same account as the hosting so DNS, the certificate and the renewal date all sit in one place rather than three — year one of the domain is free on qualifying annual plans.
What the visitor's connection meets
NVMe storage behind a LiteSpeed cache built into the server, built-in WebP conversion, HTTP/2 and free SSL — so a roaming handset receives fewer bytes, sooner, already built.
And for you: cache status in the headers, per-site PHP versions and limits, staging copies, and daily backups you restore yourself from the panel.
- Cache hit or miss readable from every response
- WebP conversion built in at no extra cost
- .pt registered and renewed on the same account
- Per-site php.ini limits for a slow booking API
Why HostingFast
Standard on every plan
Fewer bytes, already built
Built-in WebP conversion and a server-level LiteSpeed cache, which is the combination that survives a roaming connection.
A band you can rule out
10–35 ms round trip published for Western Europe, so the network stops being the suspect and the payload gets the attention.
Limits you can change yourself
max_execution_time, memory_limit and the upload ceiling are per-site panel values for a booking provider that takes its time.
The domain travels with you
Site, mailboxes and address stay put whichever country you are invoicing from, with registration and DNS on one account.
Restores in minutes
Daily backups on every plan, restored by you from the panel — files, a database or both — rather than a ticket in a queue.
Support at any hour
Engineers on shift around the clock, with a first reply inside two hours and inside one when the site is down.
Quick Start
From order to online
- 1
Measure from their market
A synthetic probe in the country your bookings come from, plus a throttled DevTools run. Two figures, labelled, before you change anything.
- 2
Cut the payload first
Hero at display dimensions, two font weights, no third-party script before the headline paints. Re-measure after each change, not after all of them.
- 3
Shorten the booking tail
Count the steps to a confirmed reservation, remove one, and time it again. On a roaming connection each removed step is worth more than any server tuning.
Built In
Loaded onto every plan
- LiteSpeed caching built into the server rather than patched in by plugin
- Built-in WebP image optimisation at no extra cost
- NVMe SSD storage on every tier, not just the expensive ones
- Per-site PHP version switching from the control panel
- Staging environments for testing changes before they ship
- Daily backups, with self-service restores you run from the panel
- Free SSL on every plan, renewed automatically before it can expire
- WordPress and 400+ other applications installed in one click
- Year one of your domain free when you order annually
- Human support on duty every hour of every day
Frequently Asked
What people ask us most often
How do I test what a roaming visitor experiences?
Two readings, clearly labelled. A synthetic run from a probe in their country gives you connect time, start render and LCP over a realistic path. DevTools with a slow 4G profile and CPU slowdown shows what a throttled handset does with your payload while keeping your routing. Never quote one as the other.
I moved to Portugal — does the site have to move too?
No, and that is the point of owning the domain. Site, mailboxes and address are unaffected by where you invoice from. Add Portuguese contact details, register a .pt if domestic clients matter, and keep registration on the same account as the hosting so DNS and the certificate stay in one place.
Would a Portuguese server be faster for Portuguese visitors?
Not measurably. The band we publish is 10–35 ms round trip to London, against an 800 ms budget for a good first byte. If the site feels slow the cost is in the render or the payload, and moving the origin changes neither. Read the cache header on a second request before assuming otherwise.
How much of a booking flow can be cached?
The property pages, photographs and guides — all of it, and they should be. The availability calendar, price calculation and payment step cannot be, because they are personal and transactional. Shorten that tail rather than trying to cache it, and set the per-site PHP limits your provider's API needs.
Keep reading
Hosting in Portugal
Rates in EUR, which domain endings we can register there, and how the tax works out.
Web Hosting in Southampton
Southampton timed the same way, with the origin inside the 5–15 ms band.
Web Hosting in Frankfurt
Frankfurt on the same method, inside the same 10–35 ms European band.
TTFB (Time To First Byte) (Glossary)
What first byte contains, and why a roaming visitor fails on payload instead.
WordPress Hosting
Managed WordPress on NVMe with LiteSpeed, Redis and AccelerateWP in front.
Web Hosting
Shared hosting on NVMe with a LiteSpeed cache and free migration 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.
Measure from their connection.
NVMe behind a server-level LiteSpeed cache, WebP built in, free SSL and a free migration — plus per-site PHP limits for the parts that never cache.
View WordPress Hosting plans