What are you really paying for with web hosting, and where do your files actually sit?
So you've built a website. Maybe you coded it yourself, used an AI tool, or put it together in WordPress. It looks fine on your computer, but now you want other people to be able to visit it. For that, you need hosting.
A website needs somewhere to store its files and data. It also needs a computer connected to the internet that can respond when someone visits. That's what a web server does.
What is a website actually made of?
A website is a collection of files and, in many cases, a database. The files contain everything needed to build the pages visitors see. Depending on how the site was built, that might be HTML, PHP, JavaScript, CSS, images and so on.
The database stores information the website needs to work with. A WordPress site keeps its pages, posts, settings and other data in one. Not every website needs a database, though. Plenty of simple sites are just files.
This matters because how your site was built changes what it needs from hosting.
Where does the website live?
Your files and database have to sit somewhere that can be reached over the internet. That's the web server's job. It's a computer designed to run websites and other online services. Similar in principle to the one on your desk, but built and configured for very different work.
A hosting server has to stay connected to the internet all the time and handle whatever requests come in, so it needs enough storage, memory and processing power for the sites it runs. It sits in a data centre with reliable power and cooling, runs software that can deliver websites, and is protected with security and monitoring.
It also needs looking after. Depending on the hosting service, that means security updates, backups, monitoring, hardware maintenance and other ongoing work. You never see any of this when you visit a website. You type the address and the page loads.
How does someone reach your website?
When a visitor types your domain into their browser, the browser first has to find out where the site is hosted. DNS handles this. It connects your domain name to the location of your website, normally an IP address. Your domain might point to something like 185.42.19.7, and the browser uses that to contact the server.
The server receives the request and works out what the visitor needs. For a simple site, that might just mean returning an HTML file along with some images, CSS and JavaScript. A WordPress site is more involved. The server may need to run PHP, pull information from the database and process plugins before it can produce the page. The browser receives whatever comes back and displays it, usually in a fraction of a second.
HTTPS protects the connection between the visitor and the site, using an SSL/TLS certificate for the domain.
What are you actually paying for?
More than storage space. You're paying for the infrastructure that keeps the website running and available. CPU to process requests, RAM to run applications, storage for files and databases, network connectivity. Then the less visible parts: security and software updates, backups, monitoring, power and cooling, server maintenance, technical support. What's included varies by service.
How much of each you need depends on the site. A small website with a handful of pages may need very little processing power. A busy online store may need considerably more.
What determines the hosting you need?
Not every website puts the same load on its server. A five-page business site is nothing like an online store with thousands of products. A WordPress site loaded with plugins can demand far more processing than one that mainly serves static pages.
Storage is only part of the picture. Your site also needs enough CPU and memory to handle visitors and run the software behind it. If lots of visitors arrive at once, the server has to deal with many requests at the same time. The same thing happens when a single page needs a lot of processing before it can be displayed. So a site can have plenty of storage and still run short of resources.
Which hosting option applies to you?
Your website can share a server with other websites, or have resources allocated more specifically to it. That depends on the type of hosting you choose.
Hosting option | Resource model | Control | Cost | Usually suits |
|---|---|---|---|---|
Shared hosting | Resources shared with other websites | Lower | Lower | Smaller business sites with modest requirements |
VPS | Resources more isolated | Higher | Higher | Growing or specialised sites needing more control |
Dedicated server | An entire physical server assigned to you | Highest | Highest | Sites with substantial or specialised requirements |
Shared hosting is the simpler, cheaper option. You're sharing the underlying server with other sites, which also means less control over it. A VPS gives you more control and better-isolated resources. It costs more, and depending on whether it's managed for you, it may take more technical knowledge to run. A dedicated server gives you an entire physical machine. Most control, but you're paying for the whole server and responsible for a lot more.
More expensive doesn't mean better. If your site doesn't need the extra resources or control, paying for them won't get you anything. Plenty of sites do fine starting on shared hosting and moving to a VPS later, if and when they need to.
Which website are you running?
A small business website. A few pages, a contact form, basic company information. Shared hosting will often be enough, and there's not much point paying for a larger environment the site won't use.
A WordPress website. Depends on the site. Plugins, themes, databases, images and dynamic content all affect how hard the server has to work. Caching helps a lot here, since commonly requested pages can be served without rebuilding them from scratch every time. A small WordPress site may run perfectly well on shared hosting. A busy or complicated one may eventually need more.
An online store. Generally more work than an information site. Products, shopping carts, customer accounts and checkout all involve dynamic requests and database activity. Traffic can also spike during a promotion or marketing campaign, and slow pages or checkout problems cost you sales, so headroom matters more.
A site with bookings, logins or memberships. More server work again. The site may need to fetch different information from the database for each visitor, process bookings, or manage logged-in users.
Notice that visitor numbers alone don't tell you much. What matters is how much work the site does for each visitor.
Who is managing the server?
There's one more decision to make. How much of the technical work do you want to handle yourself?
With managed hosting, the provider takes care of much of the work involved in running the server. Configuration, security updates, monitoring, backups, other maintenance, depending on the service. You get to spend your time on the website instead of the server underneath it. Self-managed means more of that falls to you, including configuration, updates, security and general administration.
So it's not just a question of which server is powerful enough. It's also how much of it you want to manage yourself.
A bigger server won't always fix a slow website
Worth knowing before you upgrade. A more powerful server doesn't automatically make a slow website faster. Large images, badly configured plugins, too many third-party scripts and inefficient code all cause performance problems, and moving the site to a bigger server can leave the actual problem exactly where it was.
Before paying for more resources, find out what's causing the slowdown. If the server is running out of CPU or memory, more resources may help. If the website itself is creating unnecessary work, fix the website.
What this means for your business
Choosing hosting isn't about finding the biggest server you can afford. Start with what your website actually needs. A small business site may only need a simple environment. A busy WordPress site or online store may need more resources as it grows. A specialised application may justify the extra control of a VPS or dedicated server.
You'll also need to decide how much of the technical work you want to own. If you'd rather not manage the server, managed hosting takes much of that off your hands. If you want more control and you're comfortable doing the administration, self-managed may suit you better.
And if you're not sure where to start, you don't need to predict what your site will look like in five years. Pick an environment that fits the website you have today. You can always move up when the site actually needs it.
If you'd prefer a hosting environment where the server administration is handled for you, hosting.com offers managed hosting options.