How to Choose Web Hosting in 2026: A Practical Checklist

i

This post contains affiliate links. If you buy through them, we may earn a commission at no extra cost to you. It does not change what we recommend checking.

Choosing web hosting in 2026 is less about finding “the best host” and more about avoiding the wrong one for your situation. Almost every provider advertises fast servers, free SSL, and friendly support. The differences that actually cost you money or downtime are buried in renewal terms, backup policies, resource limits, and how easy it is to leave.

This guide is a practical checklist. It does not rank hosts and it does not contain our own speed benchmarks — we have not run lab tests, and we will not pretend otherwise. Instead, it tells you exactly what to look for, which questions to ask before you pay, and where to verify the answers. Where we state a technical fact, we link to the official source in the Sources section at the end.

Table of Contents

• Step 1: Define What You Are Hosting
• Step 2: Pick the Right Type of Hosting
• Step 3: Check the Technical Baseline
• Step 4: Read the Pricing Like an Accountant
• Step 5: Backups, Security, and Recovery
• Step 6: Performance You Can Actually Measure
• Step 7: Support and Uptime Promises
• Step 8: Plan Your Exit Before You Enter
• The One-Page Checklist
• FAQ
• Sources

Step 1: Define What You Are Hosting

Before comparing a single plan, write down three things:

1. What software will run the site. WordPress, a static site generator, a Node or Python app, or a hosted builder? This alone rules out half the market. Shared hosting is built around PHP and MySQL; it is usually a poor fit for long-running Node or Python processes.
2. How much traffic and data you realistically expect in the next 12 months. Not your dream number — your realistic one. A new blog does not need a dedicated server. A shop running paid ads from day one may outgrow the cheapest tier quickly.
3. What happens if the site is down for a day. For a hobby blog, an annoyance. For a store or a lead-generation site, lost revenue. Your answer decides how much you should pay for backups, support, and redundancy.

Keep this note open while you compare. Most bad hosting decisions come from buying for a site you do not have.

Step 2: Pick the Right Type of Hosting

There are five broad categories. Each is a trade-off between price, control, and how much work you do yourself.

A useful rule: choose the least complex option that comfortably fits Step 1. If you are not willing to patch an operating system, an unmanaged VPS is not “more professional” — it is a liability.

If shared or managed WordPress hosting fits, this is where most beginners start. Providers to shortlist: Hostinger, IONOS, Kinsta (managed WordPress, see our Kinsta vs WP Engine comparison). Run each one through the rest of this checklist rather than taking any of them on reputation.

Step 3: Check the Technical Baseline

For WordPress specifically, WordPress.org publishes its own hosting recommendations. As of its current requirements page, it recommends:

• PHP 8.3 or greater
• MySQL 8.0 or greater, or MariaDB 10.11 or greater
• HTTPS support
• Apache or Nginx (with mod_rewrite on Apache) as the most robust server choices

WordPress still runs on older PHP and MySQL versions, but the same page notes those versions have reached end of life and may expose your site to security vulnerabilities. In practice: if a host cannot tell you which PHP versions you can select, move on.

WordPress.org also suggests asking hosts whether PHP runs under your own account user rather than a shared server user — a simple question that reveals how seriously a shared host isolates customers.

Other baseline items to confirm on the plan page or with sales:

• Free SSL/TLS certificates with automatic renewal. Free certificates are widely available — Let’s Encrypt, for example, is a free, automated certificate authority — so you should not pay extra for a basic certificate.
• SSH and Git access if you or a developer will deploy code.
• Staging environment so you can test updates before they hit the live site.
• Data center location close to your audience, or a CDN included.
• Email hosting: is it included, how many mailboxes, and what are the sending limits? Many people find out about sending caps only when their newsletter bounces.

Step 4: Read the Pricing Like an Accountant

Hosting pricing is designed to look cheaper than it is. Do this for every plan you shortlist:

1. Find the renewal price, not the introductory price. The headline price usually applies to the first term only and often requires prepaying multiple years. Look in the plan’s fine print or the checkout page for “renews at.”
2. Calculate the three-year total. First term plus renewals. This is the number to compare between hosts.
3. List the add-ons you will actually need: daily backups, malware scanning, a dedicated IP, extra storage, email. Some hosts include them; some sell them at checkout with pre-ticked boxes.
4. Check the domain. A “free domain” is frequently free for the first year only. Note the renewal price of the domain itself.
5. Read the refund policy. How many days, and what is excluded (domains and add-ons often are)?
6. Read the resource limits. “Unlimited” storage or bandwidth almost always comes with a fair-use clause, inode limits (number of files), or CPU limits. Find them in the terms of service.

We deliberately do not quote prices in this guide: they change often and vary by country and currency. Always confirm the final number on the provider’s checkout page before you pay.

Step 5: Backups, Security, and Recovery

This is the section people skip and regret. Ask, and get the answers in writing or on an official page:

• How often are backups taken? Daily is a sensible minimum for any site that changes.
• How long are they kept? Seven days of retention is very different from thirty.
• Where are they stored? Same server as the site is weak protection. Off-site is better.
• Can you restore yourself, in one click, without a support ticket? And is there a fee for restores?
• Can you download a full backup (files plus database) to keep your own copy?
• What isolation exists between accounts on shared servers?
• Is there a web application firewall and malware scanning, and is cleanup included if you get hacked, or billed separately?
• Is two-factor authentication available for the hosting control panel?

Whatever the host promises, keep your own independent backup too. A host’s backup protects you from your mistakes; your own copy protects you from the host’s.

Step 6: Performance You Can Actually Measure

Every host claims to be fast. Instead of trusting marketing, measure outcomes your visitors feel. Google’s Core Web Vitals are a useful, public yardstick. According to web.dev, a good experience means:

• Largest Contentful Paint (LCP) within 2.5 seconds
• Interaction to Next Paint (INP) of 200 milliseconds or less
• Cumulative Layout Shift (CLS) of 0.1 or less

Google recommends assessing these at the 75th percentile of page loads. Hosting mainly affects server response time (Time to First Byte), which in turn feeds into LCP. Themes, images, and plugins matter just as much — so a slow site is not always the host’s fault.

How to test fairly during a trial or refund window:

• Install the same site (same theme, same plugins, same content) on the host you are evaluating.
• Run PageSpeed Insights or Lighthouse several times, from the region where your audience lives.
• Check Time to First Byte specifically for uncached pages (for example, while logged in or on a search results page).
• Compare against your current host, not against a marketing chart.

Step 7: Support and Uptime Promises

• Uptime guarantee: Look for a specific percentage in a Service Level Agreement (SLA), and — more important — what you get if they miss it. Usually it is a partial credit, and often you must request it yourself within a set window.
• Support channels: chat, tickets, phone? 24/7 or business hours? In which languages?
• Scope of support: Will they help with WordPress issues, or only with “server” problems? Will they help migrate your site?
• A pre-sales test: Before buying, send a technical question (for example, “Which PHP versions can I choose, and does PHP run under my account user?”). The speed and accuracy of the answer is a free preview of the support you will get later.

Step 8: Plan Your Exit Before You Enter

The best time to plan leaving a host is before you join it.

• Register your domain somewhere you control, ideally separate from your hosting, or at least make sure it is registered in your name and email.
• Know the transfer rules. ICANN’s registrant FAQ explains that a registrar may deny a transfer to another registrar within 60 days of initial registration or of a previous transfer, and that changing registrant details can trigger a 60-day lock. Registrars must provide your transfer (Auth-) code within five calendar days of your request. You can avoid inter-registrar transfers entirely by just pointing your nameservers or DNS records to a new host.
• Confirm you can export everything: files, databases, and email. Proprietary page builders and “site in a box” platforms can be hard to move.
• Check contract terms: is there a cancellation fee, and is the prepaid balance refundable after the trial window?

The One-Page Checklist

Copy this and fill it in for each host you are considering:

• ☐ Hosting type matches what I am actually building (Step 1–2)
• ☐ Supported PHP / database versions confirmed; HTTPS with auto-renewing free certificate
• ☐ SSH, Git, staging available if I need them
• ☐ Data center or CDN near my audience
• ☐ Three-year total cost calculated with renewal prices and add-ons
• ☐ Domain renewal price noted
• ☐ Refund window and exclusions read
• ☐ Resource limits and fair-use policy read
• ☐ Daily, off-site backups with self-service restore and download
• ☐ Malware scanning / cleanup policy known; 2FA on the control panel
• ☐ Core Web Vitals tested on a copy of my real site
• ☐ SLA percentage and compensation terms known
• ☐ Support tested with a pre-sales technical question
• ☐ Domain registered in my name; export and exit path clear

If a host fails two or more of these, keep looking — there is no shortage of alternatives.

Where Contabo fits

If Step 2 pointed you to a VPS rather than shared hosting and you are comfortable managing a Linux server yourself, Contabo is a budget VPS provider worth a look. On October 16, 2026 its official price list started at €5.50/month on a monthly term (€4.40/month on a 24-month term) for Cloud VPS 4 with 4 vCPU, 8 GB RAM and 100 GB SSD, before VAT and in the EU location. Plans are unmanaged by default, other regions add a monthly surcharge, and short terms on the entry plans can carry a setup fee, so run it through the checklist above like any other host. Our Contabo VPS price guide compares every tier, or see current Contabo VPS plans (affiliate link).

FAQ

Is cheap shared hosting good enough for a new blog?
Often, yes. A new site with modest traffic does not need premium infrastructure. What matters more is backups, a current PHP version, and an honest renewal price. You can move up later — which is why Step 8 matters.

Do I need managed WordPress hosting?
If downtime costs you money and you do not want to handle updates, caching, and security yourself, managed hosting is worth evaluating. If you are comfortable maintaining WordPress, a good shared or cloud plan can be enough.

Should I buy my domain from my host?
It is convenient, but keeping the domain at a separate registrar makes switching hosts simpler. Either way, make sure you are the registrant.

Is “unlimited bandwidth” real?
Treat it as “unmetered within fair use.” Read the acceptable-use and resource-limit sections of the terms.

How do I know if my host is the reason my site is slow?
Check Time to First Byte on uncached pages. If it is consistently high while your theme and images are optimized, the server is a likely cause.