Website Hosting: How to Choose, What to Watch For, and When It's the Real Problem

Hosting is the least exciting decision in a website project, which is why it usually gets made in ten seconds, on price. A year later it introduces itself properly: the site opens slowly, the backup turns out not to exist, and support answers within two days. If the website is your business on the internet, hosting is the apartment it lives in — and it's worth knowing what you're actually renting.

What you're actually buying when you buy hosting

Four housing arrangements, in human language:

Shared hosting. A flatshare: hundreds of sites on the same server, sharing CPU, memory, and a queue. Cheap, and usually enough for a brochure site — as long as the neighbours stay quiet. When one of them lands a viral campaign or an infection, everyone feels it.

Managed WordPress hosting. Renting with a building committee: the provider maintains the server, updates, backs up, and keeps a cache for you. More expensive, and in return someone else gets up at night when something falls over.

A private server (VPS). Your own place: fixed resources no neighbour can steal. But you're also the plumber and the electrician — without someone actually maintaining it, a VPS is just a more expensive way to neglect a server.

A static site on a CDN. Not an apartment at all — more on that below, because it's the option worth knowing about.

The one-minute test that exposes tired hosting

Before blaming the images or the plugins, check one thing: how long the server takes to start answering. The metric is called TTFB — the time from the browser requesting the page until the first character arrives. Every other optimisation only begins after it finishes, and I covered it in the speed guide.

The home version of the test: open your site in the morning, after a night with no visitors. If the first visit is slow and the refresh right after is fast, your server "fell asleep" or is queuing behind the neighbours. That's almost always a sign of oversold shared hosting, and no amount of image compression will fix it.

Good hosting won't save a heavy site. Bad hosting will bury an excellent one.

Seven things to check before signing

1. Where the server sits. An audience in Israel and a server in the US means every request crosses an ocean, twice. Look for a nearby server, or a CDN that serves content from a close edge.
2. Backups — and not just that they exist. Automatic, stored off the server, with a simple way to restore on your own. A backup sitting on the same server gets infected along with it, and a backup you can't restore is hope, not a backup.
3. Current versions. PHP and the database on supported versions, with one-click upgrades. A provider running five-year-old versions is saving money at the expense of your security.
4. SSL included. An HTTPS certificate is basic infrastructure, not a "premium add-on". A provider that charges separately for it is telling you something about itself.
5. A staging environment. The ability to spin up a copy of the site, try an update or a change on it, and only then touch the live site.
6. Support you can measure. Not "24/7 support" in the headline, but: how fast does a human answer, and in what language. Send a question before you're a customer — the answer teaches you more than any sales page.
7. Isolation between sites. On shared hosting, what happens when a neighbouring site gets hacked? Serious providers isolate accounts; the very cheap ones don't always.

What sounds important — and isn't

"Unlimited hosting." There is always a limit; it's just written in a different clause, in terms like inodes or "fair CPU use". A normal business site never gets near the disk limits — it chokes on CPU and memory, which are exactly the resources nobody promises anything about.

Hundreds of gigabytes of storage. An optimised brochure site weighs less than one video from your phone. Storage is the easiest number to print and the least relevant one.

"Specially optimised for WordPress." Sometimes it means a well-configured cache and automatic updates; sometimes it means a WordPress logo on the sales page. The difference shows up in the questions from the previous section, not in the headline.

The control panel. cPanel, Plesk, or a home-grown interface — if you log in twice a year, you won't feel the difference.

Whose name is on the account

The rule from the ownership guide applies here too: the hosting account is registered in your name, paid by you, and the developer gets access — not ownership. The day you want to switch providers or developers is not the day to discover the site lives in someone else's apartment.

The option fewer people know: a static site on a CDN

Most brochure sites don't actually need a server assembling every page on every visit. You can build the pages once, in advance, and distribute them as ready files across a global CDN. The result: no server to get tired, no database to break into, no queue behind noisy neighbours — and the site opens fast from anywhere.

The site you're reading right now is built exactly this way, and it's part of why it scores 100 on speed metrics without heroics. It doesn't fit everything — a store with live inventory or a members' area needs a server — but for a business site that presents services and collects enquiries, it's usually the fastest and most resilient option, and often the cheaper one.

Switching hosts without drama

Decided to move? The order matters more than the speed:

1. Bring up a full copy of the site at the new provider and test it on a temporary address — forms, Hebrew, images.
2. Lower the TTL of your DNS records in advance, so the switch propagates quickly.
3. Point the domain at the new server — preferably at a quiet hour.
4. Keep the old server alive for a few more days, in case something was forgotten.

And if the move is not just a server but a platform too — that's where 301 redirects and a URL map come in, and I wrote a separate guide on it.

Bottom line

Hosting is not the place to pinch pennies, but it's also not the place to pay for meaningless numbers. A server near your audience, a backup that restores, current versions, and support that answers — that's the whole story, and it costs less than it seems.

Not sure what your current hosting is doing to your site? Send me the address — I'll check and tell you whether the problem is the apartment or the furniture, including the answer "your hosting is fine, keep it".