Origin timing · Rome
Rome: your best press day should be dull for the server
A guidebook mentions you on a Tuesday, four thousand people arrive at once, and whether that becomes bookings or an error page was decided weeks earlier.
The short answer
A press spike is almost pure reading, and reading caches — so the pages that crowd lands on should be served pre-built without the application booting at all. Check the ratio now rather than then: request your ten busiest URLs twice each, and confirm the second response reports a cache hit. Whatever never hits is what will fall over.
The platform gives you the rest: NVMe storage behind a LiteSpeed cache built into the server, OPcache on current PHP 8.x, and a published 10–35 ms round trip from Italy to our London origin. Free SSL, an engineer-run migration and support at any hour are included on every plan.
By the HostingFast team · Reviewed 15 August 2026
Free
Migration, engineer-run
24/7
Engineers on shift
Daily
Backups, restore yourself
$0
Setup, every tier
Trade has run here continuously for three thousand years, and today it is the ministries and their suppliers, the Cinecittà production trade, and an extraordinary density of family businesses — some serving their tenth generation of customers from the same address. Several of them have websites older than the smartphone.
So this page covers what actually decides a good day: cache ratio before a spike, which content belongs pre-built, the round trip in figures, and the fifteen years of old URLs quietly costing every visitor an extra hop.
Check the ratio before the write-up, not after
Take your ten busiest URLs, request each twice, and read the cache header on the second response. Hits mean those pages will absorb a crowd without touching the database. Misses mean every one of those four thousand arrivals triggers a full PHP render, and that is the version of the story that ends in a screenshot of an error page.
When a page refuses to cache, the cause is usually small: a session cookie set sitewide, a 'recently viewed' widget, or a booking fragment loaded on every page rather than only where it is needed. Fix them on a staging clone, re-run the same ten URLs, and keep the record — it takes ten minutes and it is the difference between a good day and an incident.
Hours, menus and price lists belong pre-built
The content a visitor from a guidebook wants is exactly the content that changes least: opening hours, the menu, the price list, how to find you. All of it should be static HTML served from cache, not assembled per request from a database, and none of it needs to be dynamic to be current — editing a page and letting the cache invalidate is enough.
Two details matter more than they look. Mark up hours and address so a search engine can display them, which often answers the visitor before they even arrive. And keep the lead photograph at display dimensions and out of the lazy set — deferring the element the browser is timing is the most common self-inflicted regression on a restaurant page.
10–35 ms, and where the seconds really are
Italy sits inside the band we publish for Western and Northern Europe: 10–35 ms round trip to London, indicative for a well-connected consumer network. Against the 800 ms Google treats as a good time to first byte, the distance is a few per cent, and a server in Rome would not change what a visitor feels on a cached page.
The seconds are in the render and the payload. An uncached page pays the round trip plus a full application boot; a heavy page pays for every byte over a connection you do not control. Split your own measurement with curl -w — time_connect is the network, and the gap to first byte belongs to the server — and you will stop attributing the wrong half.
Fifteen years of URLs, and one redirect
A business that has been online since the mid-2000s has accumulated old addresses: a www variant, an http original, a previous domain, maybe an old CMS path structure. Each of those should reach the current page in exactly one 301. Run curl -sIL against the bare http address and count the hops — a chain of three costs three round trips and a TLS handshake before any HTML moves.
Keeping .it on the same account as the hosting keeps that tidy: one renewal date, DNS aimed correctly, and SSL issued as soon as each name resolves here. Old links in printed guides and other people's articles keep working, and the authority attached to them keeps arriving at the page you actually want people to read.
What a long-established site gets
Server-level LiteSpeed caching on NVMe storage with OPcache on current PHP 8.x, so an old site on a modern stack absorbs a crowd without being rebuilt for each visitor.
Plus per-site PHP version switching for a plugin nobody has updated since 2018, staging copies, free SSL on every hostname, and daily backups you restore yourself.
- Cache hit or miss readable from every response
- .it registered and renewed on the same account
- Per-site PHP versions for older plugins
- Staging copies before touching a live menu
Why HostingFast
Standard on every plan
A crowd answered from cache
Server-level LiteSpeed caching means a guidebook mention lands on pre-built pages rather than on the database.
Old code, current stack
Per-site PHP version switching lets a long-standing plugin keep its build while the rest of the account runs something current.
Cheap uncached requests
NVMe storage with OPcache on current PHP 8.x keeps a booking form or contact page quick even when it cannot be cached.
One 301, verified
Keeping the name on the same account as the hosting makes a single canonical redirect chain easy to set and easy to check.
Mail on your own domain
Mailboxes with IMAP, POP, SMTP and spam screening, and MailChannels handling outbound instead of a free address on a business card.
Migration handled for you
Engineers move a fifteen-year-old site across at no charge, keep it serving throughout, and change delegation on your sign-off.
Quick Start
From order to online
- 1
Audit the cache ratio
Ten busiest URLs, two requests each, cache result recorded. Do it this week rather than during the week somebody writes about you.
- 2
Straighten the redirects
curl -sIL against every old hostname you own. One 301 to the canonical page each, and old printed links keep their value.
- 3
Move it and re-measure
One free migration request, verification on a temporary address, delegation on your word, then the same measurements repeated and written down.
Built In
Loaded onto every plan
- LiteSpeed caching built into the server rather than patched in by plugin
- Current PHP 8.x with OPcache enabled from the start
- Per-site PHP version switching from the control panel
- NVMe SSD storage on every tier, not just the expensive ones
- 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
- Spam and virus screening on every mailbox as standard
- Zero setup charges — there is no joining fee, ever
Frequently Asked
What people ask us most often
How do I know the site will survive being written about?
Measure the cache ratio before it happens. Request your ten busiest URLs twice each and read the header on the second response. Pages that report a hit will absorb a crowd without touching the database. Pages that never hit will trigger a full render for every arrival, and those are the ones to fix.
We have old URLs from three website generations. What now?
Map each one to its current equivalent with a single 301 — not a chain. Run curl -sIL against every old hostname and path you can remember and count the hops. One redirect keeps the value of a link printed in a guidebook a decade ago; three redirects spend a round trip each before any HTML moves.
Can a plugin from years ago keep running?
Often, yes — set that site's PHP version and extension list to what it needs from the panel, and run a current build elsewhere on the account. Test the combination on a staging clone first, and keep a backup you can restore yourself before you promote anything.
Does an Italian audience need an Italian server?
Not for a cached page. We publish 10–35 ms round trip for Western Europe against an 800 ms good first-byte threshold, so the hop is spending a few per cent. Split your own measurement with curl -w and you will see the network in the connect time and the real cost in the gap after it.
Keep reading
Hosting in Italy
Rates in EUR, which domain endings we can register there, and how the tax works out.
Web Hosting in Bristol
Bristol timed the same way, with the origin inside the 5–15 ms band.
Web Hosting in Paris
Paris on the same method, inside the same 10–35 ms European band.
DNS Propagation (Glossary)
What propagation is, what the TTL controls and how to watch a change land.
PHP Hosting
Any PHP project on current builds with OPcache already switched on.
Domain Names
Register or transfer a name and keep DNS on the account that serves the site.
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.
Make your best day boring.
NVMe behind a server-level LiteSpeed cache, OPcache on current PHP 8.x, free SSL and an engineer-run migration — with a cache header you can read.
View PHP Hosting plans