Seasonal load · Landscaping Sites
Web hosting for landscapers — Your load test happens on the first warm Saturday in March
Landscaping enquiries arrive in a weather-driven burst, mostly from phones on garden-strength signal, and the quote form with photo uploads is the part that has to survive it.
The short answer
Do the measuring in February, because the first warm weekend of spring is not a test you get to repeat. Three things to check before then: that your service pages are actually being served from cache, that the quote form's photo upload completes on a weak mobile connection, and that a before-and-after pair costs you one eager image rather than two.
That last one is specific to this trade and it is worth stating plainly: side-by-side comparison images put two large files above the fold, and only one of them can be the thing the browser paints first. HostingFast provides NVMe storage behind server-level LiteSpeed caching with automatic WebP conversion, free SSL, free migration and support at any hour.
By the HostingFast team · Reviewed 24 August 2026
24/7
Reachable, round the clock
1-click
WordPress setup
Free
Certificate price
Daily
Restore points, all plans
Landscaping searches follow the weather closely: the first warm weekend generates more enquiries than the whole of the preceding winter. That gives the site an unusual profile — eleven quiet months, then a burst of mobile traffic from people standing in their own gardens with poor signal and a specific question.
It also concentrates the risk. Whatever is wrong with the quote form will be wrong for everyone at once, on the one weekend the year's work is booked, and you will find out from a competitor's diary rather than from an error log.
So the calendar matters as much as the method. Everything below is work to do in the off season, when a broken form costs nothing and a measurement can be repeated as often as you like.
Before-and-after pairs, and the one eager image
A comparison pair is two large photographs sitting next to each other above the fold, which is the least convenient arrangement for Largest Contentful Paint. Whichever the browser paints last is effectively what you are measured on, so the two should not both be full-weight originals. Serve them at the dimensions they render at, let automatic WebP conversion do the format work, and keep only the pair on the first screen eager.
Everything further down the project page — the process shots, the planting detail, the finished garden at dusk — should be lazy-loaded with width and height reserved so nothing shifts as it arrives. Layout shift on a phone is measured too, with a good threshold of 0.1 at the 75th percentile, and reserved dimensions cost nothing to add.
The upload is the request that must not fail
A quote form that accepts photographs of the garden saves you a great many wasted visits, which makes it the most commercially important request on the site and also the most fragile. Check that the maximum upload size, the script execution time and the form plugin's own limit agree with each other, because a mismatch produces a failure with no useful message and a homeowner who does not try twice.
Then reduce what has to travel. Client-side resizing before upload turns three 6 MB phone photographs into a few hundred kilobytes with no loss for the purpose. Test the full flow throttled to a slow mobile profile, and make sure the form tells the sender clearly whether it worked — a silent failure on garden-strength signal is the failure mode this trade actually suffers.
Measure from where the enquiries come from
Test from your audience's location, not from wherever a tool defaults to. A site serving a British audience tested from a US node reports transatlantic latency as if it were your fault; most tools let you choose the test location, and choosing correctly changes the number materially.
Then get the server figure on its own: `curl -s -o /dev/null -w '%{time_starttransfer}' https://yourdomain.example`, five runs, median kept. Against Google's 800 ms good boundary, a cached page off LiteSpeed and NVMe from a UK connection to our London origin — a 5–15 ms round trip — should sit a long way inside it. If it does, the remaining seconds are payload, and payload is fixable in February.
Publish the seasonal pages before the season
Spring planting content written in February has time to be found by the time the first warm weekend arrives; the same page written in April is competing for a demand that has already been served. That is a scheduling point rather than a speed one, but it interacts with performance: adding pages in the quiet months means the site you measured is the site that takes the traffic.
Freeze changes as the season opens. No plugin updates, no new galleries, no theme adjustments on a Friday in March. If something has to change, put it on staging, measure it there, and keep the daily backup restore path rehearsed so a mistake is a ten-minute problem rather than a lost weekend.
What holds up in a burst
Cached service and project pages come off LiteSpeed inside the web server, so a weekend of mobile traffic is one render and a great many cache hits rather than a full stack invocation each time.
NVMe storage sits under the quote submissions that cannot be cached, and automatic WebP conversion keeps the before-and-after pairs at a weight a garden-strength signal will carry.
- Cache hits answered without booting PHP
- NVMe storage under the uncached form submissions
- Uploaded site photography converted to WebP for you
- Daily restore points on all plans, entry included
Why HostingFast
Standard on every plan
Reads that absorb a weekend
A cached project page costs one render and then bandwidth, which is what lets a modest plan carry a weather-driven burst.
Format work done for you
Automatic WebP conversion on uploads, so a before-and-after pair is lighter without anybody remembering to export differently.
Fast storage under the submissions
Quote forms with attachments cannot be cached, so NVMe under the write path is the part of the stack that actually matters for them.
A clone for off-season changes
Staging lets you rebuild a gallery in January and measure it, so March gets the version you already tested.
Certificates renewed without a reminder
Free SSL on every plan. A certificate expiring on the first warm Saturday is entirely avoidable, and here it is avoided by default.
A Friday change you can undo
Daily backups recover files, a database or both from the panel, which is what makes a Friday change survivable if it goes wrong.
Quick Start
From order to online
- 1
Do the work in the quiet months
February, not April. Every measurement below can be repeated freely when nothing is at stake, and none of it can be repeated in March.
- 2
Test the upload path on bad signal
Throttle the network, attach three photographs, confirm the limits agree and the form reports clearly. This is the request that books the work.
- 3
Set the pairs, then freeze
One eager image on the first screen, everything else lazy with reserved dimensions. Then stop changing things as the season opens.
Built In
Loaded onto every plan
- Service and project pages confirmed as cache hits on a logged-out request
- Before-and-after pair served at display dimensions, not camera resolution
- Only the images on the first screen loading eagerly
- Width and height reserved on lazy images so nothing shifts as it loads
- Upload size, execution time and form plugin limits checked for agreement
- Client-side image resizing applied before the quote form uploads
- Full upload flow tested throttled to a slow mobile profile
- Speed tests run from a test location matching your actual audience
- Server response timed with curl from your region and compared to the 800 ms boundary
- A change freeze in place from the start of the season, with staging for exceptions
Frequently Asked
What people ask us most often
Two comparison images side by side — how do I keep that fast?
Treat the pair as one budget. Serve both at the dimensions they actually render at rather than at camera resolution, let the platform's automatic WebP conversion handle the format, and keep only the images on the first screen eager. Whichever of the two paints last is effectively your Largest Contentful Paint, so halving both files helps considerably more than optimising one of them.
Homeowners say the photo upload fails. What is going on?
Usually a limit mismatch plus a weak signal. Check that the maximum upload size, the script execution time and the form plugin's own cap all agree; a file that clears one and not another fails without a useful message. Then add client-side resizing so a phone photograph is a few hundred kilobytes rather than several megabytes before it is ever sent.
When should I be doing this work?
In the off season, because the first warm weekend is a load test you cannot re-run. February gives you time to measure, change one thing at a time, and re-measure without any of it mattering. It is also when seasonal content should be published, since a spring planting page written in February has time to be found before the demand arrives.
My speed test reports a slow result from a US server. Is that real?
Not for your audience. Testing a British site from a North American node measures the Atlantic as though it were your hosting, and most tools let you pick the test location from a dropdown. Set it to where your enquiries actually come from, then confirm the server side separately with curl — that combination gives you a number that describes your customers rather than the tool's default.
Keep reading
Letting Agents — Hosting Guide
Availability that changes daily, precise cache purges, and the writes behind them.
Moving Companies — Hosting Guide
Peak-week load and the uncached routes to measure before the vans move.
Uptime (Glossary)
What an uptime figure can and cannot see when a warm cache is in the way.
WordPress Hosting — Built for Landscapers
Managed WordPress with staging copies for the off-season rebuild.
cPanel Reseller Hosting
cPanel accounts you can resell, on the storage and cache layer described here.
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 in February, not in March.
Cache hits off LiteSpeed, NVMe under the quote submissions, automatic WebP conversion, and staging so the off-season rebuild is tested first.
View WordPress Hosting — Built for Landscapers plans