Performance profile · Photography portfolios
Web hosting for photographers — Your slowest page is the one you are proudest of
The gallery you spent a fortnight sequencing is also the heaviest thing you publish, and nobody waiting on it will ever tell you they left.
The short answer
Start by finding out which photograph is holding the page up. PageSpeed Insights names the largest contentful paint element by selector, and on a portfolio it is a specific image you can go and look at. Fix that one file before you consider anything structural — 2.5 seconds is the threshold worth clearing.
Underneath, HostingFast runs NVMe storage behind a LiteSpeed cache with WebP conversion included on every plan, from $2.42 a month on Sprint. Free SSL, free migration and 24/7 support come with it, and the renewal figure matches the order figure.
By the HostingFast team · Reviewed 24 August 2026
99.9%
Uptime target with a credit clause
24/7
Engineers on shift, any hour
Free
SSL included on every tier
NVMe
NVMe under every gallery page
A photography site has an unusual shape. Almost all of the bytes sit in a handful of pages, and almost all of the judgement happens in the first two seconds of one of them. Everything else — about, rates, contact — is text and effectively free.
That concentration is good news, because it means optimisation is targeted rather than general. You are not making a whole site faster. You are making three or four gallery pages faster, and mostly by changing what you upload.
The sections below go in the order that pays: identify the element, fix the file, then deal with client delivery and storage, which are separate problems that get mistaken for each other.
Name the photograph that is costing you
Run PageSpeed Insights on your busiest gallery URL. Under the diagnostics it identifies the largest contentful paint element with a CSS selector and a thumbnail. Open that image in a new tab and check its real dimensions and byte size — the answer is very often an export that was never resized for the web.
Then look at field data separately from lab data. Field figures come from real Chrome visits over a rolling window and are what search actually sees; the Lighthouse run underneath is a simulation you can repeat on demand. Use the lab run to iterate and the field figure to confirm, and give the field number a few weeks to catch up.
Dimensions, format, and the profile nobody strips
Three things make a portfolio image heavier than it needs to be. It is served at a larger pixel size than it is displayed at. It is a JPEG when it could be WebP, which conversion here handles on the server without a plugin. And it still carries an embedded colour profile and full EXIF block, which on a set of forty images adds up to real weight for no visible benefit.
Use srcset so a phone downloads a phone-sized file rather than a desktop one, and give every image explicit width and height so the layout does not jump as the set loads. Lazy-load anything below the fold, but never the LCP image itself — deferring the hero is the classic optimisation that makes the metric worse.
Client galleries behave differently
A password-protected proofing gallery is, by definition, not cacheable. Every view runs PHP, hits the database and reads from disk, which is a completely different load profile from the public portfolio the cache is absorbing. That is the part of a photography site that consumes CPU.
Keep the two apart in your head when you size a plan. Public work benefits from the cache and costs almost nothing to serve; delivery and proofing cost real resource per view, and if that is a large part of your business it is what you are buying headroom for.
Storage, costed against what you actually publish
Web-sized work is small. A disciplined portfolio of display-resolution frames fits inside the 10 GB on Sprint at $2.42 a month without straining, and most photographers never approach it.
The reason to size up is full-resolution delivery from the same account, which is a different order of magnitude. Nitro at $7.08 carries 200 GB with two cores and 4 GB of RAM behind it, and moving up is an account change rather than a migration — the site stays where it is, the allocation grows around it.
Sized for images, not for spreadsheets
WebP conversion is included on every plan and runs server-side, so the single biggest win on a photographic page is applied before you install anything. NVMe storage keeps the uncached first view quick.
Migration is free and carried out by our engineers, SSL issues and renews itself, and support is staffed at every hour of the day for the nights when a gallery has to go out.
- WebP conversion applied on the server, no plugin required
- NVMe storage on every tier, including the entry plan
- Free engineer-handled migration from your current host
- Upgrades applied in place, with no site move involved
Why HostingFast
Standard on every plan
The biggest image win, included
Server-side WebP conversion removes most of the bytes from a photographic page before a plugin is involved.
Fast on the uncached first view
NVMe storage means the visitor who arrives before the cache is warm is not the one who suffers.
Room for full-resolution delivery
200 GB on Nitro absorbs client galleries alongside the public portfolio without a second account.
Upgrades that do not move you
Changing tier is an allocation change; the site stays put and nothing goes offline for it.
Certificates handled for you
Free SSL issues and renews automatically, which matters on any page asking for a client password.
Answers at two in the morning
Support is staffed around the clock, aiming to reply within two hours, or one when a site is down.
Quick Start
From order to online
- 1
Identify the element
Run PageSpeed Insights on your heaviest gallery and note which image it names as the largest contentful paint, with its size and dimensions.
- 2
Bring the site over free
Our engineers handle the migration at no charge, or install WordPress with a portfolio theme in one click from Softaculous.
- 3
Re-shoot the numbers
After resizing and converting, run the same lab test three times and compare medians. Check field data again a month later.
Built In
Loaded onto every plan
- Server-side WebP conversion included at no extra cost
- NVMe SSD storage on every tier, not only the expensive ones
- LiteSpeed caching built into the server rather than patched in by plugin
- Free SSL on every plan, renewed automatically before it can expire
- In-place account upgrades — no migration when you change plan
- Daily backups, with self-service restores you run from the panel
- Free migration of an existing portfolio by our engineers
- Human support on duty every hour of every day
- Softaculous installs 240+ applications in one click
- 99.9% uptime as the target, with a pro-rated credit in our terms
Frequently Asked
What people ask us most often
How do I find out which image is slowing the gallery down?
PageSpeed Insights tells you directly. In the diagnostics section it names the largest contentful paint element with a CSS selector and a thumbnail, so you can open the exact file and check its dimensions and weight. On a portfolio it is nearly always a hero frame exported at print resolution and scaled down in the browser, which means the full file crossed the network for nothing.
Should I lazy-load every image in a set?
Everything below the fold, yes. The hero image, no. Lazy-loading the largest contentful paint element delays the very thing the metric measures and reliably makes the score worse. Mark the first image as eager, let the rest load as they approach the viewport, and give all of them explicit width and height so the page does not shift while the set arrives.
Do password-protected client galleries slow the site down?
They behave differently rather than badly. A protected gallery cannot be cached, so every view runs PHP and reads from the database — which is real work, unlike a public page the cache answers from memory. If proofing and delivery are a large part of what you do, that is the reason to buy CPU headroom, and Nitro at $7.08 brings two cores and 4 GB of RAM for it.
Should full-resolution originals live on the same account as the site?
Only if you are delivering them to clients from it. Display-resolution frames are a few hundred kilobytes each, so a career of selected work sits inside the 10 GB on Sprint at $2.42 a month without strain. Serving originals is a different order of magnitude entirely, and that is what the 200 GB on Nitro at $7.08 exists for — with the move between them applied in place rather than as a migration.
Keep reading
Dance Studios — Hosting Guide
Timetable pages and class galleries, and the caching behaviour that keeps both quick.
Martial Arts Schools — Hosting Guide
Schedule-driven sites where the same page is read hundreds of times a week.
Best Hosting for Portfolio Sites
The portfolio shortlist, judged on image delivery rather than on disk allowance.
WordPress Hosting — Built for Photographers
Managed WordPress with Redis object caching, staging copies and WP-CLI on every plan.
Joomla Hosting
The same measurements applied to a different CMS, and where Joomla spends its time.
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.
Fix the file, then the host.
NVMe behind LiteSpeed with WebP conversion built in, from $2.42 a month, with free migration and SSL included.
View WordPress Hosting — Built for Photographers plans