Interaction profile · Moving Companies
Moving companies: your quote form is a latency problem
Your page score is fine and your quote form still loses people on step three, because nobody has ever timed step three.
The short answer
On a removals site the thing to measure is the quote form, step by step, not the page it sits on. A multi-step form makes a round trip to the server each time somebody presses Next, and none of those requests appear in a page speed score, because they happen long after the page has loaded.
Open the Network panel, work through your own form as a customer would, and read the timing on each request it fires. Anything over about 500 milliseconds per step is a visitor watching a spinner, and step three is usually the worst because that is where the inventory calculation happens.
Every plan carries NVMe storage behind a LiteSpeed cache, free SSL, engineer-run migration and 24/7 support, and moving up a plan is an in-place change rather than a rebuild.
By the HostingFast team · Reviewed 12 August 2026
99.9%
Uptime, credited pro rata
24/7
Humans on shift
Free
SSL, no add-on line
NVMe
NVMe as standard
A removals enquiry is a long form. Where from, where to, how many bedrooms, what is going, what date, packing or not. Every one of those screens is a chance to lose somebody, and a slow screen loses more people than an ugly one.
The awkward part is that none of this is visible in the tools most people use. Lighthouse measures loading a page. It does not measure what happens when a customer fills in a form for four minutes, and that is the entire commercial event on a removals site.
So this page is about instrumenting the interaction: what to time, where the time goes, and which of those seconds you can actually remove.
Time every step of the form
Open DevTools on the Network panel, tick Preserve log, and complete your own quote form from start to finish as a customer would. You will see a request per step, usually to an admin endpoint. Click each one and read the timing: the Waiting for server response row is the part your hosting and your code own.
Write the figures down step by step. A pattern emerges on almost every removals site: the first two screens are quick because they only store answers, and one screen in the middle is slow because it does real work, usually the volume or inventory calculation.
Why one step costs more than the others
The slow step is the one running a calculation, a lookup or a third-party call. Distance and volume estimates often query an external mapping or pricing service, and your visitor waits for the whole round trip: your server to the third party, back, then back to the browser.
Two fixes usually help. First, cache what does not change: a postcode-to-distance result for the same pair of postcodes is the same tomorrow. Second, do the work after the visitor has moved on, so the request that must be synchronous stays small and anything slow happens in the background.
Where the distance to the origin shows up
The platform's origin is in London. For a UK removals firm and its customers that is about 5 to 15 milliseconds of round trip, which is as good as it gets and effectively invisible. It becomes visible when a form makes many sequential requests, because latency multiplies with round trips.
That is the real argument for fewer steps rather than faster ones. A five-screen form makes five sequential round trips; a three-screen form makes three. Combining screens removes latency you cannot otherwise optimise away, and it usually improves completion for reasons that have nothing to do with speed.
Instrument the funnel, not just the page
Record how many people start the form and how many reach each screen. Once you have that, a slow step and a step where people leave can be compared directly, and you will often find they are the same screen. That comparison is worth more than any lab score.
Keep the page around the form cacheable so the entry point is fast, and keep the form itself lean. Then re-run the step-by-step timing after every change to the form and after any plugin update, because a quote form is exactly the sort of component that silently gains a second.
For the sites where the form is the product
NVMe storage keeps the uncacheable form endpoints quick, and LiteSpeed caching keeps the pages around them from competing for the same resources.
Free SSL, engineer-run migration, daily backups and 24/7 human support come on every plan, with a 99.9% uptime commitment backed by a pro-rated credit.
- NVMe under the endpoints the form posts to
- LiteSpeed over the pages leading into the form
- London origin: 5–15 ms across the UK and Ireland
- 99.9% uptime, credited when the month falls short
Why HostingFast
Standard on every plan
Fast where caching cannot reach
A quote endpoint can never be cached, so NVMe storage under the database is doing the work that matters on it.
Close to your customers
The origin is in London, roughly 5 to 15 milliseconds from UK and Irish visitors, which keeps multi-step forms responsive.
Cache on the way in
LiteSpeed serves the landing and service pages from cache, leaving PHP free for the form submissions that need it.
Notifications that arrive
MailChannels handles outbound mail, so a completed quote does not land in a junk folder while the customer waits.
Staging for form changes
Test a form rebuild on a clone and time each step there before a single real enquiry passes through it.
The credit behind the number
The 99.9% figure carries a pro-rated credit, and monitoring runs continuously rather than when you think to ask for it.
Quick Start
From order to online
- 1
Complete your own form with DevTools open
Tick Preserve log, work through every screen, and record the server response time for each request the form fires. That table is your diagnosis.
- 2
Attack the slow screen only
Find the one step doing real work, cache what is deterministic about it, and move anything slow off the synchronous path.
- 3
Cut a step, then re-time
Combine two screens, re-run the timing and check the completion numbers a fortnight later. Fewer round trips is the one saving latency cannot undo.
Built In
Loaded onto every plan
- NVMe SSD beneath the uncacheable form endpoints
- LiteSpeed caching on the pages that lead into the form
- A London origin, 5–15 ms from UK and Irish visitors
- MailChannels delivering the quote notification reliably
- Staging clones for rebuilding a multi-step form safely
- Per-site PHP, so the form host can run its own version
- Free SSL, issued and then reissued on its own
- A backup daily, with a restore that takes one click
- 99.9% uptime, with a pro-rated credit if it slips
- 24/7 support, with the first reply targeted at two hours
Frequently Asked
What people ask us most often
Why does my quote form feel slow when my page score is good?
Because page scores measure loading a document, and a multi-step form does its work afterwards. Each Next button is a separate server round trip that no page-level tool records. Open the Network panel, complete the form yourself and read the timing on each request; that is where the seconds are.
Which step of a removals form is usually the slow one?
The one doing the calculation, most often the inventory or volume estimate, and often because it calls an external mapping or pricing service. Your visitor pays for that whole round trip. Cache the deterministic parts and take anything genuinely slow off the synchronous path.
Is it better to have fewer steps or faster steps?
Fewer, if you have to choose. Latency multiplies with sequential round trips, so removing a screen removes a whole round trip that no amount of server tuning can recover. It also tends to improve completion for ordinary usability reasons.
Does the server location matter for a UK removals firm?
It helps and it is already handled: the origin is in London, which is roughly 5 to 15 milliseconds from UK and Irish visitors. That closeness matters more than usual here, because a form making five sequential requests pays the round trip five times.
Keep reading
Martial Arts Schools — Hosting Guide
Timetables, membership signups and a site that stays quick as classes fill.
Law Firms — Hosting Guide
Case pages, enquiry forms and the credibility layer around both.
Best Hosting With Free SSL Included
Which hosts genuinely include the certificate, and which bill for it later.
Web Hosting — Built for Moving Companies
The shared plans in full: specs, caching and what comes as standard.
WooCommerce Hosting Plans
Carts, checkouts and the performance work that changes order volume.
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.
Time the form, not the page.
NVMe under the endpoints, a London origin close to your customers, and support at every hour.
View Web Hosting — Built for Moving Companies plans