Most website hosting quotes are built to make one number do all the talking: the monthly price. That is why it is the least useful figure on the page. For businesses choosing UK web hosting, the real question is not what it costs per month but who controls the account, whether backups have ever been restored, how the site performs under load, and how quickly a human responds when something breaks.
This analysis walks through each question in practical detail. You will learn why monthly price is the least informative number on the quote, who holds the account and what lock-in looks like, how to test backups and restores, why demo-page speed proves little under real traffic, and what fast support means. It also covers UK data and hosting location questions, how to use the four questions in a buying conversation, and where Neil Foulkes fits into the picture. Neil Foulkes offers website hosting and ongoing support, so this piece is written with a commercial interest. The aim is to help you buy with ownership and resilience in mind, not just a low headline rate.
Why Monthly Price Is the Least Informative Number on the Quote
The invoice is the smallest number in the decision. The real cost of hosting is the afternoon your site goes down, the enquiries you never see, and the rebuild if nothing can be restored. A cheap monthly figure carries an expensive risk figure. Cyber incidents hit 43% of UK businesses in the past year.
Price is the one number you can compare in ten seconds, which is why it dominates the conversation. Four things that decide how your year actually goes are invisible on a pricing table: who holds the account, whether backups are ever restored, how the site behaves when traffic arrives, and how fast a human replies.
Tip: write the four questions into your brief before you request any quotes. Every provider then answers the same things and you compare like with like. Most quotes answer none of them unless you ask.
In the UK, web hosting and website hosting are sold across a huge spread of prices and a very small spread of marketing language. The difference usually hides in account control, recovery, load handling and support, not the storage figure on the plan table.
Who Holds the Account? Ownership, Access and Lock-In
Ask any provider to put three things in writing. They are three separate accounts with separate risks.
The domain registrar is where the name lives. DNS holds the records pointing that name at your website and your email. The hosting panel is where the site is managed. Different logins, different risks.
On each, your business should be the named owner, using a business email address you control and could still recover in five years. Not a developer’s personal address, an agency inbox, or a relative who once helped. Only the registered name holder can approve a transfer, so ownership is authority, not sentiment.
Ask for a second administrator on every account. One named owner plus one backup means a holiday or locked inbox does not take your site offline.
Then ask lock-in directly: if you leave, can you export the files, database and DNS records, and will credentials be handed over without a fee, notice period or a hold on your domain? A host that will not answer in writing is telling you something. Note that a host can hold your files without owning your name.
At handover, record renewal dates and the paying card, keep every login in a shared password manager you control, and export your DNS records once live, so you always have the map back.
Have the Backups Ever Actually Been Restored?
Ownership settled, the next question is recovery. A backup means a copy exists somewhere. A restore means that copy goes back and the site works again on a deadline. “We back up daily” answers the first question and says nothing about the second.
Ask when the last restore was performed, whose site it was, and how long that site was unavailable while it happened. If nobody can name a date, the backup has never been proven. One tested restore is worth more than a schedule you have only been told about; regularly testing backups is what genuinely prevents data loss, per NCSC guidance on implementing and testing backups.
Ask what is actually inside the backup. Website files only, or files plus database, email and DNS records? The database holds your content; your email depends on DNS records and mail-server settings that a file-only backup will not capture. A file-only backup may restore a site with no content, because the database, which holds posts, pages and orders, is a separate file the backup may not include.
Then ask where the copies live. If backups sit on the same server or under the same account as the live site, one compromised admin login or ransomware incident takes the website and its safety net in a single move. Independence is the point of a backup.
Finally, ask for a restore test into a staging copy rather than over your live site, and schedule one before a launch, a redesign or a busy trading period.
A restore proves recovery is possible. The next question is whether the site holds up before anything breaks at all.
Does Performance Hold Under Load, Not Just on a Demo Page?
Proven restores protect you when something breaks. They do not help when demand arrives.
A home page that loads quickly with nobody on it proves little; almost any host looks fast on a quiet Tuesday. Your site is judged the afternoon a campaign, newsletter or press mention sends real traffic at it.
Ask how the host handles a spike, and what happens at your plan’s limit: throttling, an automatic upgrade, extra charges, or a page that stops responding. Get it in writing rather than assumed.
Ask what is shared and what is isolated: shared server, container, or dedicated CPU and memory. That tells you whether a neighbour’s surge or runaway script can slow your site through no fault of your own.
Ask which load tools are included, and who configures them. Caching, a content delivery network, image optimisation and database query caching are either switched on for you or left as your project. Do not rely on performance or uptime figures unless a credible technical source or independent testing provides them.
Then test it yourself: ask for a trial or staging environment and check it from a UK connection if your customers are in the UK. Ask what monitoring the host runs, whether you are alerted when the site slows or goes down, and where status updates are published. Any web hosting comparison should settle the setup process before launch.
Who Answers When the Site Goes Down, and How Fast?
Load tests reveal configuration; support reveals what happens when it fails, and it is harder to verify in advance.
Ask the hours of human coverage and the timezone behind them. Plugin updates, failed renewals and certificate expiries do not wait for office hours, they surface at any time. Then ask the route in: ticket form, live chat, or a number that rings a person? Is the first reply automated, and does anything reach a human out of hours?
Ask what counts as an emergency (site down, suspected hack, email outage) and get the target time to first human response written into the contract, not quoted from a marketing page. If it lives only on the website, it is marketing.
Ask who is on the other end: someone with access to your hosting account, or a first-line queue reading a script with no visibility of your setup. The difference shows up on the worst day of your year. According to Uptime Institute’s 2026 annual outage analysis, 57% of respondents to their 2025 survey said their most recent major outage cost more than $100,000, a figure drawn from enterprise and data-centre operators, but a useful prompt for any business to ask what an outage hour actually costs them. Our WordPress aftercare: hosting, maintenance and support explained covers how that relationship should work day to day.
Tip: spend one low-stakes ticket before you commit, and time the reply. A genuine pre-sales question is the cheapest support test going, and it tells you more than any service level promise in a brochure. The wider picture is set out in our notes on hosting, maintenance and support.
Does It Matter Where the Hosting Sits? UK and Data Questions to Ask
Support response times answer one question. Location answers another, and buyers often mistake it for the whole answer.
Ask where the servers sit and where the backups sit, and whether those are the same place. UK, EEA or elsewhere. With a UK customer base, a UK or near-UK data centre shortens the round trip between visitor and server. If your audience is international, ask whether a content delivery network is available and how it is configured.
Ask who can access your data, including support and engineering staff, and whether that access is logged. A provider that cannot answer has not thought about it.
Ask how your data comes back. If you leave, how are the files and database returned to you, and when is the copy held on the old host deleted?
For searches such as website hosting uk, the intent is usually hosting for my UK business website rather than a strict requirement for a UK data centre. Location is one of the four questions, not a substitute for them, and it should never outrank account ownership or recovery.
Keep these as questions, not assumptions. Where data protection or record keeping applies, check your own requirements with an adviser, and ask the provider to confirm in writing where data is stored, who processes it and what happens on exit.
How to Use These Four Questions in a Buying Conversation
Location settled, the rest is process. Put all four questions in writing before you request a quote, asking for written answers in return. A provider who replies carefully and unambiguously is showing you the standard of support you are buying.
Before you pay, ask for three things: a trial or staging environment you can look at, one restore demonstration, and a support ticket you can time. Test while the stakes are low rather than discovering the answers on a bad day.
Then read the contract for what the pricing page omits: renewal price and term, what happens at exit and how you export, what support excludes, and what the provider accepts as an emergency.
Red flags worth walking away from: the provider cannot confirm in writing who the named account holder is, the provider cannot name a date when a restore was last performed, performance claims arrive with no monitoring or reporting detail, support has no published hours, and there is no clear path to take your data elsewhere.
After purchase, close the loop. Collect every login on day one, store the written answers and your DNS records in one document you own, and revisit the whole set at renewal, when price and terms are open for discussion again.
Where Neil Foulkes Fits Into This Picture
Plainly: Neil Foulkes offers hosting and ongoing support alongside website design and development and SEO, so this studio has a commercial interest in the advice above. Apply the same four questions to it as you would to anyone else.
That is not a formality. These are the questions worked through when hosting is set up here, because ongoing support means living with the answers long after a site goes live rather than handing over logins and hoping. Hosting is treated as part of that support, not a standalone line item, which is why account ownership, the backup schedule and the support route are agreed with the client rather than decided for them. How those pieces fit together is set out in WordPress aftercare: hosting, maintenance and support explained.
Apply the same four questions here, and ask for the answers in writing.
The Price Becomes a Rounding Decision
The same four questions apply when you compare quotes and again at every renewal: who holds the account, whether a restore has actually been performed, how the site behaves under real load, and how fast a human answers when it breaks. Settle them and the monthly figure stops being the decision.
Test one restore and one support ticket early, while nothing is at stake. On a business website, that is the cheapest insurance available: an evening spent proving recovery costs far less than an afternoon of unexplained downtime. If a provider will not answer in writing, that silence is the answer.
Conclusion
The four questions are your buying filter: who holds the account, whether a backup has actually been restored, how the site performs under real load, and how quickly a human responds when something breaks. Written answers before you commit, and one early restore test, are the two cheapest forms of insurance available. If a provider avoids straight answers, treat that silence as a warning. The monthly price should come last, because once ownership, recovery, performance and support are settled, it becomes a rounding decision. As a next step, read Neil Foulkes’s guide to WordPress aftercare, then put the same four questions to every provider, Neil Foulkes included. Demand evidence, not reassurance.