Performance brief · Builders
Builders: find the slow page before a client does
Your homepage scores well and your project gallery does not, and the gallery is the page a homeowner actually reads before ringing you.
The short answer
Test the heaviest project page first, because that is where a builder's site is slow. A homepage carrying six thumbnails will pass almost any check; a completed-extension gallery carrying twenty photographs straight off a camera will not, and the gallery is the page a homeowner opens before they decide to call.
Aim for Largest Contentful Paint at or under 2.5 seconds and Time to First Byte at or under 800 milliseconds, both measured at the 75th percentile of real visits rather than on your own desk. NVMe storage behind a LiteSpeed cache handles the server half; the image half is yours, and it is usually the larger half.
Plans start at $2.42/mo and renew at that same rate, with free SSL, engineer-run migration, domain mailboxes and 24/7 support included rather than itemised.
By the HostingFast team · Reviewed 15 August 2026
NVMe
Storage under the media library
Free
Domain registration, year one
99.9%
Uptime, and a credit if we miss it
Flat
Renewal against the sign-up rate
A builder's site is a small number of pages carrying a very large number of photographs. Completed projects, accreditation marks, the services you take on, an enquiry route. Four of those five are text. The fifth is where every second goes.
The measurement that matters is not the one your web designer ran on a wired connection in an office. It is the one a homeowner's phone produces on a patchy 4G signal, standing in a kitchen that has not been extended yet, and that measurement is usually two to three times worse.
So the useful question is never whether the site is fast. It is which request on which page costs you the most, and what number proves you fixed it. This page works through that in the order a builder would actually tackle it.
Start on the gallery page, not the front door
Open PageSpeed Insights and paste in the URL of your busiest completed-project page rather than the homepage. Read the field data at the top first: that is Chrome's record of real visits over the previous 28 days at the 75th percentile, and it is the only number that reflects the phone in the kitchen. The lab score underneath is a simulation and it wobbles run to run.
If there is no field data yet, the page has too little traffic to have been sampled, so fall back to a throttled lab run. In Chrome DevTools, open the Network panel, set the throttling dropdown to Slow 4G, tick Disable cache, and reload. That single setting is the difference between a page that looks fine and a page that behaves the way a visitor experiences it.
Where the seconds go on a construction gallery
Sort the Network panel by size and the answer usually appears in one line. A photograph straight out of a camera or a modern phone is 3000 to 5000 pixels wide and several megabytes; the slot it lands in on screen is often 600 pixels. The browser downloads the whole file and throws most of it away, and on a slow connection that single image becomes your Largest Contentful Paint.
The other common cost is a hero slider that preloads every slide before showing the first. Six slides at 1.5 MB each is 9 MB of bandwidth spent before a homeowner sees anything at all. Built-in WebP conversion is included on every plan and strips a good deal of that weight without a visible change in quality, but it cannot rescue an image you asked the browser to fetch six times over.
Fix in this order, and stop when the number is green
One: resize before upload, so nothing above roughly 1800 pixels wide ever reaches the media library. Two: let WebP conversion do its work. Three: give every image below the fold a lazy loading attribute and explicit width and height, which also removes the layout shift that makes a page feel cheap. Four: cut the slider to one static hero image, or drop it entirely.
Only after that does the server side matter, and it usually already reads well: LiteSpeed serves a cached page before PHP starts, and NVMe returns the database query underneath it in microseconds. If Time to First Byte is still slow on an uncached hit, switch the site to the current PHP version from cPanel, which you can do per site, and re-run the test.
Prove it moved, then keep proving it
Change one thing, then re-measure the same URL with the same throttling profile. Three runs, take the median. If Largest Contentful Paint has not moved by at least a few hundred milliseconds, undo the change rather than keeping it out of superstition; that discipline is what separates optimisation from decoration.
Field data lags, so expect the 28-day window to catch up gradually rather than the morning after. Diary a check for four weeks out. In the meantime, use a staging clone from WordPress Toolkit to trial the next change, so the site homeowners are looking at never becomes the test bench.
The stack under a builder's photographs
Every plan runs NVMe SSD storage behind a LiteSpeed cache, so a cached project page is served before PHP is involved at all. That is the half of page speed a host can genuinely own.
Free SSL issues and renews itself, engineers move your existing site across at no charge, and accounts go live minutes after checkout rather than after a provisioning queue.
- NVMe behind LiteSpeed on every plan, Sprint upward
- WebP conversion built in — no image plugin licence
- PHP version set per domain from cPanel's MultiPHP
- SSH with Git and Composer when the theme is versioned
Why HostingFast
Standard on every plan
A cache that answers first
LiteSpeed returns a cached project page without waking PHP, which is where most of a slow first byte comes from.
NVMe under the queries
Uncached hits still have to read the database; NVMe keeps that read in microseconds rather than milliseconds.
Image weight handled
Built-in WebP conversion cuts photograph payload at no extra cost, which is the single biggest win on a gallery page.
Staging you can break
Clone the site, trial the change, measure it, then push it live once the number has actually moved.
Migration run by engineers
We move the existing site across free and you sign off before anything is switched, so nothing goes dark mid-enquiry.
Support that reads a waterfall
Humans on the desk at any hour who will look at the actual request timings rather than reply that the server is up.
Quick Start
From order to online
- 1
Take a baseline you can defend
Record LCP, TTFB and total page weight for your busiest project page, on Slow 4G with cache disabled. Save the screenshot. Every later claim gets compared against this one.
- 2
Land on hardware that helps
Sprint at $2.42/mo covers one site; Turbo covers twenty-five if you also run a landing page per town. Both sit on NVMe behind LiteSpeed, and moving between them is a settings change rather than a rebuild.
- 3
Change one thing, re-measure, repeat
Resize images, then re-test. Enable WebP, then re-test. Cut the slider, then re-test. Keep only the changes that moved the median, and check the field data again four weeks later.
Built In
Loaded onto every plan
- NVMe SSD behind a LiteSpeed cache, on Sprint and every plan above it
- WebP conversion built in, so there is no image plugin licence to renew
- MultiPHP in cPanel sets the PHP version per domain on the account
- WordPress Toolkit clones the site to staging before you touch the slider
- Free SSL, reissued on its own long before it can lapse
- A fresh backup daily, restorable from cPanel without a ticket
- Free migration — engineers bring the site and its media library across
- Softaculous installs 240+ applications in one click
- Sprint to Turbo is an in-place upgrade, not a rebuild
- 99.9% uptime, answered with a pro-rated credit rather than an apology
Frequently Asked
What people ask us most often
Which page on a builder's site should I benchmark?
The completed-project page with the most photographs on it. That page carries the payload, and it is also the page a homeowner spends the longest on before deciding whether to enquire. Benchmarking the homepage tells you almost nothing, because a homepage is usually text and six thumbnails.
What image width should I upload at?
Around 1800 pixels on the long edge is plenty for a full-width hero on a high-density screen, and most gallery slots need far less. Anything above that is bandwidth a visitor pays for and never sees. Resize before upload; conversion to WebP then does the rest.
My Lighthouse score is 92 but the site feels slow. Which is right?
The site. Lighthouse runs a simulation on a machine that is not your visitor's, and it scores the moment it happened to run. Field data in PageSpeed Insights aggregates real Chrome visits over 28 days at the 75th percentile, so a quarter of your visitors had it worse than the figure shown. Trust that one.
Does upgrading the plan make the site faster?
It helps where the constraint is server-side, and does nothing where the constraint is a 5 MB photograph. Measure first: if Time to First Byte is under 800 ms and Largest Contentful Paint is still four seconds, the fix is in your media library, not on the invoice.
Keep reading
Florists — Hosting Guide
Perishable stock, same-day orders and a photography problem of their own.
Hair Salons — Hosting Guide
Booking widgets, third-party scripts and the mobile page that has to carry them.
Best Hosting With Free SSL Included
Which hosts include the certificate, and which quietly bill for it at renewal.
cPanel Reseller Hosting — Built for Builders
WHM, per-account limits and what a reseller stack costs to run properly.
Domain Names & Registration
Register, transfer and point a name, with the first year free on annual hosting.
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.
Take the baseline first.
Measure the gallery page today, then move it onto NVMe behind LiteSpeed and measure it again.
View cPanel Reseller Hosting — Built for Builders plans