Choosing Web Hosting, Honestly

Hosting reviews are among the most heavily monetised content on the web. Commissions of a hundred dollars or more per signup mean that rankings track payout rather than quality. Knowing what to evaluate yourself is the only reliable approach.

The pricing trap

The advertised price is an introductory rate, usually for the first term, and usually requiring payment for one to three years upfront.

The renewal rate is frequently two to four times higher. It is disclosed, in small print, and it is the price you will actually pay for most of the time you use the service.

Calculate the three-year total at introductory plus renewal rates before comparing anything. This alone reorders most rankings.

Watch for what is extra: backups, SSL beyond the free tier, email accounts, migration, and a control panel licence are all sometimes billed separately.

Matching the type of hosting to the need

Static site hosting. If your site is static — a generated blog, documentation, a brochure site — several providers host it free or nearly free, with a global content network included. This is the correct answer far more often than people realise, and it is faster and more secure than shared hosting.

Shared hosting. Many sites on one server. Cheap, adequate for small sites, and performance depends on your neighbours.

Managed application hosting. Purpose-built for one platform, with updates, caching and backups handled. More expensive, less to go wrong, and appropriate for a business site where downtime costs money.

Virtual private server. Your own environment. Requires you to administer it — updates, security, backups. Cheap for the resources, expensive in time, and only sensible if you know what you are doing or want to learn.

Platform services. For applications rather than sites, with deployment from a repository. Usually the right answer for anything custom.

What actually matters

Renewal price, as above.

Backups: frequency, retention, restoration. Ask specifically whether restoring is free and how long it takes. Some hosts charge for restoration, which is a poor discovery to make during an incident.

Whether you can leave. Can you get a full export — files and database — without assistance? Some hosts make migration out deliberately awkward. Test this early, not when you need it.

Support hours and channels, and whether support can actually fix things or only reads scripts. Trial this before committing, by asking a moderately technical question pre-sale.

Resource limits that are stated. Unlimited bandwidth is never unlimited; the limits are in the acceptable use policy, expressed as file counts, inode limits, CPU seconds or process counts. These are what you will actually hit.

Server location, which affects latency and sometimes legal obligations about where data is stored.

Uptime commitment, and what the remedy is. A guarantee with no remedy is marketing.

Signals worth noticing

Ownership. Many apparently distinct hosting brands are owned by the same parent company. A comparison of five brands may be a comparison of one operator's five products.

How old the reviews are, and whether they describe the current service. Hosting quality changes after acquisitions, frequently downward.

Community discussion in places where affiliate links are not permitted. Forums for the platform you use are more informative than any ranking site.

Pricing pages without a renewal rate visible. If you have to hunt for it, that is itself information.

The evaluation that costs an hour

Sign up for the shortest term available, even at a higher rate, rather than committing to three years for the discount.

Put a real site on it, not a test page.

Raise a support ticket with a genuine question and time the response.

Perform a backup and a restore.

Export everything and confirm you have what you would need to move.

If any of those go badly, you have learned it for the cost of one month instead of three years.

When free hosting is right

Static sites: genuinely free tiers from several providers, with no meaningful catch for a personal site.

Documentation and project sites: repository-based hosting is free and well suited.

Learning: free tiers everywhere.

Not for: anything commercial where support matters, or anything where the provider's terms allow them to place advertising on your pages.

A short decision path

Static site: use a static host, free or nearly so.

Small personal site on a common platform: cheap shared hosting, evaluated on renewal price, bought for the shortest term.

Business site where downtime costs money: managed hosting for the platform, and treat the price difference as insurance.

Custom application: a platform service.

You know how to administer a server and want control: a virtual private server, with your own backups.

Mistakes people make

Comparing introductory prices. The renewal rate is frequently two to four times higher and is what you will pay for most of the time you use the service. Calculate the three-year total.

Buying three years upfront for the discount before knowing whether the host is any good.

Not testing a restore. Some hosts charge for restoration or take days. Discovering this during an incident is the wrong time.

Trusting rankings. Commissions in this industry run to a hundred dollars or more per signup, and rankings follow payouts.

Paying for shared hosting for a static site. Several providers host static sites free, faster and more securely than shared hosting does.

Not checking whether you can leave. Test a full export early, while nothing is urgent.

The short answer

Work out what kind of hosting the site actually needs, buy the shortest term available even at a higher rate, and within the first month raise a support ticket, run a backup and restore, and export everything. If any of those go badly you have learned it cheaply.