Image budget · Milan
In Milan, your slowest asset is a photograph
Campaign imagery is the point of the site and the reason it loads slowly. This page treats that as a measurement problem rather than a taste one.
The short answer
On a Milan fashion or design site the number that decides everything is largest contentful paint, and the element behind it is almost always a hero photograph. The good threshold is 2.5 seconds on a mid-range phone, and a four-megabyte camera export served at full size will miss it from any datacentre on earth.
So the order of work is fixed. Name the LCP element in PageSpeed Insights, serve the dimensions you actually display in WebP, and only then argue about servers — where our half is NVMe storage behind a LiteSpeed cache in London, per-site PHP switching, and SSH for people who would rather use a terminal than a plugin.
By the HostingFast team · Reviewed 12 August 2026
NVMe
Storage on every tier
Free
Domain, first year
99.9%
Availability target
Flat
Renewal, unchanged
Fashion houses and their showrooms, furniture and industrial design, and the Lombardy manufacturers who make what the rest of the world thinks of as Italian design. Every one of those websites carries photography that cost more to produce than a decade of hosting.
That is the tension this page is about: the imagery is the product and it is also the payload. What follows is the element to measure, what the image pipeline is worth in seconds, what the London origin costs a visitor in Lombardy, and where .it fits into the load.
Name the element before you tune anything
Run PageSpeed Insights against your busiest lookbook URL and read two things: which element it names as the largest contentful paint, and the field figure at the top of the report, which comes from real Chrome users rather than a simulated run. On a Milan portfolio the named element is a photograph almost every time.
Then open the browser network panel and sort by transfer size. The offending file is usually sitting at the top at several megabytes, exported at print dimensions and scaled down in CSS by the theme. That is a two-minute diagnosis, and it settles whether hosting is even the subject of the conversation.
What the image pipeline is worth in seconds
Serve the dimensions you display, in WebP, with width and height attributes so nothing reflows while the file decodes. WebP conversion is built into every plan here, so it is not a plugin somebody has to keep alive through the next theme update. Lazy-load everything below the fold and nothing above it — deferring the LCP image is the most common self-inflicted regression on a gallery layout.
Expect the largest single gain of the whole exercise from this step. Most lookbooks clear 2.5 seconds here without changing host at all, which is worth writing down plainly on a hosting company's website rather than leaving you to discover it after the invoice.
What London costs a visitor in Lombardy
The origin is a London datacentre, and Italy sits in the Western and Northern Europe band we publish: 10 to 35 milliseconds of round trip. Against a 2.5-second budget that is rounding error, and a cached page crosses the distance once rather than once per element.
The cache is where the distance actually goes. LiteSpeed's cache lives inside the server rather than being layered on by plugin, so the second visitor to a collection page is handed bytes instead of a rebuild. What stays uncached is the logged-in half — the editor loading the media library, the basket, the checkout — and that makes the full trip every time. Plan the working day around it rather than pretending otherwise.
The .it, the certificate and the second connection
Italian buyers read .it as domestic, and it registers on the same account as the hosting with year one free on qualifying annual plans and DNS pointed before you ask for it. An export-facing .com runs alongside without diluting either.
Two of those decisions show up in the waterfall. The certificate issues as soon as the name points at us, so there is no window of mixed content to explain to a client; and keeping images, pages and checkout on one hostname means the browser reuses a single connection instead of paying for TLS three times.
What the platform contributes to the number
Every account runs NVMe storage behind a LiteSpeed cache built into the server, so a repeat view of a collection page never rebuilds the markup that produced it.
For the diagnosis there is shell access — SSH with Git and Composer on the developer-focused plans — plus per-site PHP switching, staging copies and daily backups you restore yourself from the panel.
- WebP conversion on every plan, no plugin to maintain
- LiteSpeed cache inside the server, not bolted on after
- Staging copies to prove a gallery rebuild first
- .it registered and renewed on the hosting account
Why HostingFast
Standard on every plan
The cache does the rebuild once
LiteSpeed caching sits in the server, so a collection page assembled for the first visitor is handed straight to the next hundred.
Image handling that survives a redesign
WebP conversion is part of the plan rather than a plugin, so the pipeline keeps working after the theme changes hands.
NVMe on the smallest plan too
Disk speed decides how fast an uncached gallery is assembled, so it is standard on every tier rather than reserved for the expensive ones.
Somewhere to rehearse
Staging copies let a gallery rewrite or a plugin swap be measured on a duplicate before a single customer meets it.
Migration with the numbers kept
Our engineers move the site free of charge, the old one keeps serving throughout, and DNS waits on your sign-off so you can compare before and after.
Uptime stated as a figure
A 99.9% target under constant monitoring, with a pro-rated credit on the account if a month falls short through a fault on our side.
Quick Start
From order to online
- 1
Take the baseline
PageSpeed Insights on the busiest gallery, field data not lab, plus the network panel sorted by transfer size. Write both numbers down before touching anything.
- 2
Fix the pictures, then re-measure
Display dimensions, WebP, explicit width and height, lazy-loading below the fold only. Run the same test again and keep the difference.
- 3
Move the origin and prove it
Free migration with the current site still serving, DNS on your approval, then the identical two measurements repeated so the gain is documented rather than assumed.
Built In
Loaded onto every plan
- WebP conversion built in, so the pipeline outlives the theme
- LiteSpeed caching inside the server rather than added by plugin
- NVMe drives under the cheapest plan as well as the dearest
- Per-site PHP version switching from the control panel
- Staging copies for proving a gallery change before it ships
- A daily backup you roll back yourself, straight from the panel
- SSH, Git and Composer on the developer-focused plans
- Free SSL on every plan, reissued before it can lapse
- In-place tier upgrades, with no migration when you change plan
- Engineers move your existing site over, billed at nothing
Frequently Asked
What people ask us most often
How do I find out which image is the LCP element?
PageSpeed Insights names it outright in the diagnostics, and on a lookbook it will be the hero photograph. Cross-check in the browser network panel by sorting on transfer size: the same file is usually top of the list at several megabytes, because it went up straight from the camera and the theme resized it in CSS rather than on disk.
The photography is the brand. How far can we compress it before it shows?
Further than most art directors expect, provided you resize before you compress. Serving a 1600-pixel-wide file where the layout displays 800 wastes three quarters of the bytes and gains nothing visible on any screen. Convert to WebP at high quality, keep the original masters, and judge the result on the page at real size rather than zoomed to 400% in an editor.
The collection page is quick and the checkout is not. What is different?
The collection page is cacheable and the checkout is not. A basket is personal to the visitor holding it, so it is built on demand and makes the full round trip to the origin every time. That is normal and not a fault. The useful work is keeping everything around the checkout cached and keeping the checkout itself to as few uncacheable requests as it genuinely needs.
Can we rehearse a rebuild before Salone rather than during it?
That is precisely what staging is for. Clone the live site, rebuild on the clone, measure the same URLs with the same tool, and push it across only when the numbers hold. April is the month this city load-tests everything, and a theme change proved on a duplicate in March is a Tuesday rather than an incident.
Keep reading
Hosting in Italy
Rates in EUR, which domain endings we can register there, and how the tax works out.
Web Hosting in Warsaw
Warsaw, where the same cache questions get a different round-trip figure.
Web Hosting in Sheffield
Sheffield, and what a UK industrial audience sees from the same origin.
Best Hosting for Local Businesses
A shortlist for local businesses, with the reasoning shown rather than a table of ticks.
WHMCS License
Billing and provisioning automation, if the sites you are speeding up belong to clients.
Agency Hosting
Client accounts, staging and care-plan infrastructure built for agency workloads.
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.
Weigh the page, then move it.
NVMe behind a LiteSpeed cache, WebP conversion on every plan, and engineers who bring the site across for nothing.
View WHMCS License plans