What is web hosting?

A website is a set of files and, usually, a database. For anyone to see it, those files have to sit on a computer that is switched on, connected to the internet and running web-server software that answers requests. Hosting is renting that arrangement from someone whose business is keeping it switched on.

The provider supplies the machine or a slice of it, the network connection, the operating system, the web server, and the physical facility with its power and cooling. You supply the site. Everything else — who patches the operating system, who updates the application, who holds backups — is set by which hosting product you bought, and that is the part buyers most often get wrong.

Three separate things get bought at once and then blamed for each other's problems. The domain name is your address, rented from a registrar. Hosting is the land the building sits on. The website is the building, whether you built it, an agency built it, or a page builder generated it.

You can move hosting without changing your domain, and change your domain without moving hosting — the link between them is DNS, which is why a host migration involves updating DNS records rather than re-buying anything. Website builders blur this deliberately by bundling all three into one subscription, which is convenient and, for a simple brochure site, often cheaper than assembling the parts yourself.

When people ask which host is best, the answer usually depends on which of these they need. They are different products with different responsibility boundaries, and the price gaps between them largely buy labour rather than speed.

The honest test is not 'how much traffic do I have' but 'how much administration am I willing to own'. A busy site on well-run shared hosting is fine. A quiet site on an unpatched VPS is a liability.

Every plan has ceilings, and the marketing word 'unlimited' is always qualified by a fair-use or acceptable-use clause. Read the specifics: storage, monthly bandwidth or visit allowances, PHP worker or process limits, inode counts, and database size. These decide whether your site slows down or gets throttled long before raw server speed does.

Two limits catch people out. Visit allowances on managed WordPress plans count more than humans — bots and crawlers frequently consume a meaningful share. And process or worker limits, not bandwidth, are usually what makes a busy WooCommerce checkout feel slow on an entry plan.

Data has to travel. A server physically closer to your audience answers faster, which is why providers let you pick a datacentre region at signup and why that choice is difficult to change later without a migration. If your audience is domestic, pick the domestic region.

A content delivery network caches copies of your static assets at edge locations worldwide and narrows the gap considerably. What it does not change is where your origin data is stored, which is the point when data location is a contractual or regulatory requirement rather than a performance preference.

Four things predict satisfaction better than any benchmark. First, the renewal price at the term length you intend to keep — introductory rates in this market are attached to long first terms and step up sharply. Second, backups: how often, how long they are retained, and whether you can restore yourself without contacting support.

Third, migration: whether the provider will move an existing site for you, how many sites are included, and whether it is free. Fourth, support scope — whether the provider will help with your application at all, or only with the server underneath it. A cheap host that will not touch WordPress is expensive the first time something breaks on a Friday.