Performance guide · Birmingham
Birmingham: the quote form is the page that matters
Your home page is cached and fine. The page that decides whether you win the job is the one the cache cannot touch — and that is the one nobody measures.
The short answer
On a Birmingham trade or engineering site the critical path is the enquiry form, and a form submission is a POST: uncacheable by definition, running the full PHP and database path every time. Measure that request, not the home page, because that is where a lost job actually happens.
HostingFast runs NVMe storage behind LiteSpeed caching from London, with mailboxes on your own domain included so the enquiry lands as well as sends. Uncached requests are the ones that need real server underneath them, and that is what the platform is built for.
By the HostingFast team · Reviewed 12 August 2026
99.9%
Uptime target, monitored
24/7
Engineers, any hour
Free
Certificates, self-renewing
NVMe
Storage under every plan
A capability statement here is often a multi-megabyte scan rather than text, and the quote form beside it is usually four plugins deep. Both are ordinary in this city, and between them they set the agenda: one blows the byte budget, the other adds an uncacheable POST to the single journey that earns money.
That combination — heavy documents plus a form that has to work — decides how this page is ordered. Forms first, payload second, distance third, and then the field data sitting in an account you already own.
The request the cache can never help with
A GET on your services page can be served from LiteSpeed without loading PHP at all. The POST that submits the enquiry cannot: it runs your form plugin, writes to the database, and usually hands off to a mail transport before it returns anything. That is the request that times out at four in the afternoon when the customer's boiler has just died.
Time it directly. Submit the form with the Network panel open, find the POST in the list, and read its timing breakdown. If the waiting phase is measured in seconds, the fault is in the plugin chain or the mail hand-off, not in the megabytes of the page around it.
Spec sheets, catalogues and the payload budget
Engineering sites accumulate PDFs the way workshops accumulate offcuts. They are rarely the first-paint problem, but they become one the moment a datasheet is embedded in an iframe or a catalogue page renders forty thumbnails at full resolution. Serve thumbnails as WebP at the size they are displayed and link the PDF rather than embedding it.
Set yourself a budget and hold it: a target for total transferred bytes on a cold load, checked whenever the site changes. A number written down survives a redesign; good intentions do not.
How far is Birmingham from London, in milliseconds?
About 5-15 ms of round trip on a well-connected UK line. Three of those for DNS, TCP and TLS still leaves the network contributing under a tenth of a second, which is smaller than the variance you get between two runs on the same mobile connection.
Which is the honest answer to the question everybody asks: the datacentre's address is real but small. Disk speed, cache design and how quickly PHP builds a page decide what your customer feels, and those are engineering choices rather than geography.
You already own the field data — read it
Search Console's Core Web Vitals report groups your URLs and reports the 75th percentile of real visits over a rolling 28-day window. It costs nothing, it is already collecting, and it tells you which template is failing rather than which single page you happened to test.
Use it to pick the target: LCP at or under 2.5 seconds, INP at or under 200 ms, CLS at or under 0.1. Then use lab tools to work out why a template misses, because the field report tells you where the problem is and never why.
The parts of the stack that decide an uncached request
When nothing can be cached, the request is at the mercy of disk latency, PHP execution and the database. NVMe storage on every tier, a low accounts-per-server count and a current PHP version chosen per site are what keep that path short.
Mailboxes on your own domain come with the plan, with MailChannels handling outbound delivery — so the enquiry that leaves your form arrives rather than sitting in a queue nobody watches.
- .co.uk registered and renewed alongside the plan
- Per-site PHP version switching from the control panel
- Mailboxes on your own domain, with outbound delivery handled
- In-place plan upgrades, no migration when you outgrow one
Why HostingFast
Standard on every plan
Short paths for uncacheable work
NVMe storage and a restrained accounts-per-server count keep the requests that must hit PHP and MySQL from queueing behind somebody else's traffic.
PHP version per site
Switch a site's PHP version from the control panel and measure the difference. An old default is one of the cheapest performance losses to fix.
Mail that leaves the building
Mailboxes on your own domain are part of the plan and outbound mail goes through MailChannels, so quotes@yourfirm.co.uk is not a deliverability experiment.
Uptime with a credit attached
A 99.9% uptime target under constant monitoring, with a pro-rated credit if a month falls short — the sort of number a tender document will accept.
Growth as an account setting
Plan changes happen in place with no migration and no downtime, from a compact shared account through VPS to a dedicated server.
cPanel, so the knowledge transfers
The panel most of the industry standardised on. Every tutorial matches your screen and a backup restores onto any other cPanel host.
Quick Start
From order to online
- 1
Time the form, not the home page
Submit a real enquiry with DevTools open and read the waiting phase on the POST. That is the number a lost job is hiding behind.
- 2
Trim the catalogue
Thumbnails as WebP at display size, PDFs linked rather than embedded, and a written budget for total bytes on a cold load.
- 3
Check the field report
Open Search Console, group by template, and fix the template that fails rather than the page you happened to open.
- 4
Move it, then re-measure
Free migration takes about a day with the old site still serving. Repeat the same three measurements afterwards and keep both sets.
Built In
Loaded onto every plan
- Form submissions timed with the network panel open, not assumed
- Per-site PHP version switching from the control panel
- WordPress Toolkit, with updates handled for you
- In-place account upgrades — no migration when you change plan
- A daily backup, restored from the panel while the enquiry form stays up
- Webmail plus IMAP and SMTP, so the enquiry inbox works on a phone on site
- NVMe SSD storage on every tier, not just the expensive ones
- 99.9% uptime as the target, monitored around the clock
- Softaculous on board for one-click application installs
- 30 days of money-back cover on hosting, 7 on reseller, if the numbers do not move
Frequently Asked
What people ask us most often
Why is my contact form slower than the rest of the site?
Because it is the only request that cannot be cached. A form POST loads PHP, writes to the database and usually waits on a mail hand-off before it responds, so it carries every cost the cached pages avoid. Time the POST itself in DevTools; if the wait is in the mail step, moving delivery onto the platform's own outbound path is usually the fix.
Do embedded PDFs hurt my Core Web Vitals?
They can. An embedded viewer loads a separate document inside your page, competing for connections and often becoming the largest contentful element. Link the PDF instead and the page renders on its own terms. Where a preview is genuinely needed, render a WebP first page and load the viewer only when someone asks for it.
Which PHP version should I run?
The most recent one your codebase and plugins support, and you can prove it in an afternoon: clone to staging, switch the version there, run the same measurements, then apply it to production. Version switching is per site from the control panel, so one legacy application does not hold the others back.
How do I know whether to tune the site or buy a bigger plan?
Profile it before you spend anything. If PHP X-Ray on the top shared tier attributes 400 ms of a request to one plugin call, extra CPU buys you nothing — that is a code problem and it will follow you to any host. If the profile is flat and the server is simply saturated at peak, that is genuinely capacity, and plan changes apply from the client area in place, with no migration and no downtime, through VPS and dedicated servers above shared.
Keep reading
Hosting in the United Kingdom
Rates in GBP, which domain endings we can register there, and how the tax works out.
Web Hosting in Helsinki
Nordic connections, .fi, and a market that notices a slow page immediately.
Web Hosting in Bristol
Aerospace and animation payloads, and measuring on the device a visitor holds.
Registering a Domain Name
Registering a name, and the DNS records you will need the moment it resolves.
Dedicated Servers
Bare metal with a control panel included and the pricing stated up front.
Domain Names
Find, register and transfer domains — first year free with 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.
Make the enquiry path quick.
NVMe under LiteSpeed, mail on your own domain, and plan changes that happen in place rather than as a migration.
View Dedicated Servers plans