What Does Web Hosting Actually Do?

Most business owners pay for web hosting without ever being quite sure what they're paying for. It shows up as a monthly or yearly charge, the website works, and that's the end of it until something goes wrong or a renewal price jumps. This article explains what a host actually does, in plain terms, so you can make sense of hosting plans and know what to ask when you're choosing one.

If you're still sorting out how hosting relates to your domain name and the website itself, start with our explainer on domains, hosting, and websites. This one picks up from there.

Hosting is a computer that never switches off

A website is a collection of files: pages of code, images, stylesheets, scripts, and sometimes a database holding things like blog posts, products, or customer accounts. For anyone in the world to see those files, they need to sit on a computer that's always on, always connected to the internet, and set up to respond when someone asks for them.

That computer is called a server, and hosting is the service of keeping your files on one and making sure it answers requests. Servers live in data centers, buildings designed for steady power, cooling, fast network connections, and physical security. You could technically run a website from a computer in your office, but it would go offline every time the power or internet dropped, and it would be your job to keep it secure. Hosting is paying someone else to handle that.

What happens when someone types your address

Say a customer types yourbakery.com into their browser. A few things happen in the background, usually in well under a second:

1. The browser looks up the address. Domain names are for humans. Computers find each other using numeric IP addresses. So the browser asks the DNS system, which works like the internet's address book, which server yourbakery.com points to.
2. The browser contacts the server. With the IP address in hand, the browser connects to your host's server and asks for the page.
3. The server responds. The server finds the right files, or builds the page if it needs to (more on that below), and sends them back.
4. The browser assembles the page. It reads the code, fetches the images and other files the page needs, and displays the result.

Your registrar handles step one by pointing your domain to the right place. Everything from step two onward is your host's job. If the server is slow, overloaded, or down, the visitor waits or gets an error, no matter how good the website is.

SSL and the padlock in the address bar

When you see https:// and a padlock next to a web address, the connection between the visitor and the server is encrypted. That's done with an SSL certificate (technically TLS these days, but everyone still says SSL). It means anything sent back and forth, like a contact form submission or a login, can't easily be read by someone snooping on the network.

Browsers now warn visitors when a site isn't secure, and search engines generally prefer HTTPS, so this isn't optional anymore. Certificates have to be installed on the server and renewed regularly. A good host handles this automatically. If your current setup involves you or someone else manually renewing a certificate each year, that's a sign of an older hosting arrangement.

Why distance matters, and what a CDN does

Data travels fast, but not instantly. If your server is in Virginia and a visitor is in Sydney, every request has to cross the world and come back. For a page that loads dozens of files, those round trips add up and the site feels sluggish.

A content delivery network, or CDN, solves this by keeping copies of your site's files on servers in many locations. When someone in Sydney visits, they get files from a nearby location instead of from Virginia. Visitors close to your main server benefit too, because the CDN takes load off it.

For a local business whose customers are mostly in one city, a CDN still helps with speed and resilience, even if the distance benefit is smaller. For anyone with a national or international audience, it makes a noticeable difference. Our hosting includes a global CDN for this reason.

Traffic and resources

Every server has limits: processing power, memory, storage, and how much data it can send. On cheap shared hosting, hundreds of websites share one server, so a busy neighbor can slow your site down. More expensive hosting gives you a bigger or dedicated share of resources.

How much you need depends less on how many visitors you get and more on how much work each visit requires. A five-page site for a solo accountant can handle a lot of traffic on modest hosting. An online store running searches, updating carts, and processing orders for each visitor needs considerably more, even with fewer visitors.

Speed problems aren't always the host's fault, though. Oversized images, too many plugins, and bloated code slow a site down on any server. In our experience, a sluggish small business site is more often a build problem than a hosting problem, which is why performance optimization usually starts with the site itself before anyone talks about upgrading the server.

Static and dynamic sites, in simple terms

This distinction matters because it changes what kind of hosting you need.

Static sites

A static site is made of pages that are built ahead of time. When someone visits, the server just hands over a finished file. Nothing is calculated on the spot. Think of it like handing someone a printed brochure.

Static sites are fast, cheap to host, and have fewer moving parts that can break or be attacked. They suit most brochure sites, portfolios, landing pages, and many small business sites where the content doesn't change minute to minute. Content can still be updated; the pages are simply rebuilt and republished when it changes.

Dynamic sites

A dynamic site builds pages at the moment someone asks for them, usually by pulling information from a database. A traditional WordPress site works this way, as do online stores, booking systems, and anything with user accounts. It's more like asking someone to write you a custom letter every time you visit.

Dynamic sites can do more, but they need more server resources, more careful security updates, and often caching to keep them quick. Say you run a bakery that wants customers to place orders online with live availability. That needs dynamic features. A bakery that just wants a menu, opening hours, and a phone number doesn't.

Many modern sites mix the two: mostly static pages, with specific dynamic pieces like a contact form or an embedded booking widget handled by a separate service.

What the host handles and what you handle

This is where expectations often don't match reality. The split varies by provider and plan, so always check, but a typical arrangement looks like this.

The host usually takes care of the physical servers and data center, the network connection, keeping the server's operating system and core software updated, SSL certificates, the CDN if one is included, and basic monitoring so problems get noticed.

The site owner, or whoever maintains the site for them, is usually responsible for the website's content, updating the site's own software (WordPress plugins and themes, for example), making sure forms and integrations keep working, and keeping their domain renewed. Backups can fall on either side depending on the plan, so it's worth asking directly rather than assuming.

The gap between those two lists is where many small business sites get into trouble. The host keeps the server running, but nobody updates the plugins, and two years later the site breaks or gets compromised. If you don't have someone looking after your side, it's worth arranging ongoing maintenance or choosing a setup with less to maintain in the first place.

When it's time to move hosts

Sometimes the right answer is a different host. Common reasons include a site that stays slow after the obvious fixes, renewal prices that have crept up well beyond the introductory rate, poor support, or an old hosting account nobody fully understands anymore.

Moving a site involves copying its files and any database, testing everything on the new server, then updating DNS so your domain points to the new location, ideally without touching your email in the process. It's very doable, but it rewards care and a checklist. Our website migration service exists for exactly this kind of move.

If you're trying to work out whether your current hosting is a good fit, or what a new site would need, send us a few details and we'll give you a straight answer.