Websites and Tech

Web Hosting

Also called hosting, web host, server

The rented server space where a website's files and database live so that visitors can reach them.

Quick facts: Web Hosting

Category
Websites and Tech
Also called
hosting, web host, server
Level
Beginner
Affects
Speed, uptime, security, email deliverability
Where to see it
Hosting control panel, PageSpeed Insights, Search Console crawl stats, uptime monitors
In this article4
  1. How web hosting works
  2. Why hosting matters
  3. Common mistakes with hosting
  4. How to act on it

How web hosting works

Your website is a set of files and, on most platforms, a database. Both have to live on a computer that is always switched on and always connected, and that computer is what you rent. The domain name is separate: it is an address that the domain name system points at the server, which is why you can change hosts without changing your name.

Plans differ mainly in how much of the machine is yours. Shared hosting puts many sites on one server, which keeps the price low but means a neighbour’s traffic spike can slow your pages. A virtual private server reserves a defined slice of processing and memory. Managed platform hosting adds a tuned stack, caching, automatic updates and usually a staging environment. Dedicated and cloud arrangements sit above that for larger or spikier workloads. What you are buying beyond disk space is processing capacity, how the server software is configured, whether backups are automatic and restorable, and how fast someone answers when something breaks.

Why hosting matters

Hosting sets the ceiling on everything else. It governs how quickly the server starts replying, which is what time to first byte measures, and no amount of image optimisation compensates for a server that thinks for too long before it speaks. It governs availability, so it decides whether ad clicks land on a page or an error.

It also affects things owners rarely connect to hosting at all. Outbound email sent from a crowded shared server often lands in spam because the address is shared with strangers. Security patching of the server software is the host’s job on managed plans and yours on unmanaged ones, and that distinction only becomes visible after an incident.

Common mistakes with hosting

Choosing on the introductory price is the usual one. The first term is discounted, the renewal is not, and the cheap plan often lacks the backups and staging that make the site safe to work on. The second mistake is geography: a business serving Kathmandu hosted on the other side of the world, or a Nepali company selling into Australia hosted only locally, both pay a distance penalty on every request.

Then there is the assumption that backups exist. Many plans include them, but with a short retention window and no simple way to restore without a support ticket. Others put the site, its staging copy and the email all in one account behind one password, so a single compromise takes everything. And plenty of sites outgrow their plan without anyone noticing: traffic grows steadily over a year, the same shared plan is asked to carry it, and the slowdown gets blamed on a plugin.

How to act on it

Audit what you have before you shop. Note the server response time on a cached and an uncached page, the backup frequency and retention, whether you have ever tested a restore, the version of the server software, and your own record of outages. That list turns a vague feeling that the site is slow into a specific decision.

Match the server location to where your customers are, and put a delivery network in front when the audience is split across continents. If you move, plan it properly: lower the DNS time-to-live in advance, copy and verify before switching, keep every URL identical, and check the certificate and tracking afterwards. That sequencing is the whole of careful hosting and migration work, and skipping it is how sites lose a day of orders.

Do and do not

Do

  • Match the server location to where customers are
  • Check backups, staging and support before comparing prices
  • Keep the domain registrar separate from the host

Do not

  • Choose a plan on the introductory price alone
  • Send marketing email from a crowded shared server
  • Stay on a plan your traffic has clearly outgrown

Questions people ask about this

How much should I pay for web hosting?

There is no fixed answer, and the useful question is what the plan includes rather than what it costs. Automatic backups you have tested restoring, a staging environment, current server software and support that answers during your working hours are worth more than extra storage. A brochure site and a busy shop have genuinely different requirements.

Where should my website be hosted?

As close to your customers as is practical. A business serving Kathmandu is best on a server in or near the region, while a Nepali company selling into Australia, the UK or the United States should host nearer that market. If the audience is split across continents, cache aggressively and use a content delivery network so the distance matters less.

Is my hosting the reason my website is slow?

Sometimes, but not always, and the test is simple. Look at how long the server takes to send the first byte of a page. If that is slow even on a cached page, the server or its distance is the problem. If the first byte is quick but the page still feels sluggish, the weight is in images, scripts and fonts, and moving hosts will not help.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.