1. Shared hosting: the entry tier ($3–$15/month)
Shared hosting puts your site on a server alongside hundreds of other sites. All of them share the same CPU, RAM, and bandwidth pool. The host manages everything at the server level: you get a control panel (cPanel or a proprietary equivalent), an FTP connection, and a web root to drop your files into. No root access, no configuration control, no visibility into what your server neighbors are doing.
At $3–$15/month, shared hosting is priced for volume. The margins work because one physical server hosts many accounts. When load is light, shared hosting performs adequately. When one or several neighboring sites spike in traffic or run an inefficient script, everyone on the server slows down. This is called the noisy-neighbor problem, and you have no recourse against it except waiting or upgrading.
Common shared hosts: Hostinger, Bluehost, SiteGround's starter plans, DreamHost, GoDaddy's shared plans. These are legitimate companies running real infrastructure. The product is fine for what it's designed for: low-traffic sites where performance consistency isn't a business requirement.
What you're giving up at this tier beyond performance consistency: PHP version control (shared hosts often lag behind current PHP releases, which matters for security), fast technical support (expect ticket-based support with multi-hour response times rather than phone or live chat with a Linux engineer), and proactive monitoring. If your site goes down at 2 AM on a shared host, you won't discover it until morning unless you've set up independent uptime monitoring yourself.
The right use case for shared hosting: a personal portfolio, a placeholder site for a business that hasn't launched yet, a very low-traffic informational page where a few seconds of extra load time has zero business consequence, or a development environment for testing. For any site you're actively driving traffic to and relying on to generate leads or revenue, shared hosting is fundamentally the wrong foundation.
2. VPS hosting: dedicated resources ($20–$80/month)
A VPS (Virtual Private Server) is a virtualized slice of a physical server with dedicated CPU cores and RAM allocated exclusively to your account. The noisy-neighbor problem disappears because your resources aren't shared. Someone else's traffic spike doesn't touch your allocated memory or processing power. Performance is more predictable and consistently better than shared hosting under the same workload.
The trade-off is management responsibility. An unmanaged VPS gives you root access to a clean Linux server and nothing else. You decide what web server to run (Nginx, Apache), which PHP version to install, how to configure the firewall, where backups live, and how to set up SSL. If the PHP process crashes or Nginx stops responding, you fix it. If someone tries to brute-force your SSH port, your fail2ban configuration stops them (assuming you set one up). Every system administration task falls to you.
For developers comfortable with Linux server administration, an unmanaged VPS from providers like Hetzner, DigitalOcean, Vultr, or Linode is excellent value. Hetzner's entry-tier VPS (2 vCPU, 4 GB RAM, 40 GB SSD) runs around $5–$7/month in European data centers — competitive infrastructure at an absurdly low price. DigitalOcean and Vultr are slightly more expensive but offer more polished managed add-ons and better US-region options.
For business owners who don't want to manage a server, managed VPS services from Cloudways, Kinsta (WordPress-focused), or similar platforms put a management layer on top of underlying cloud infrastructure (AWS, Google Cloud, DigitalOcean). You get the performance of a VPS without the server administration, at a 2–3x price premium over the raw infrastructure cost. That premium buys you a control panel, automated backups, and a support team that handles the server layer — a reasonable trade for most non-technical site owners.
3. Managed hosting: infrastructure handled for you ($30–$100/month)
Managed hosting means the provider takes responsibility for the server infrastructure so you don't have to. That scope includes SSL certificate installation and auto-renewal, nightly backups with offsite copies, uptime monitoring with alerting, server software updates (web server, PHP version, OS security patches), firewall configuration, and malware scanning. You manage the application (the site itself); they manage everything underneath it.
The distinction between managed and unmanaged matters most when something goes wrong. On an unmanaged server, "something went wrong" is your problem to diagnose and fix on whatever timeline your schedule allows. On managed hosting, it's the provider's problem to resolve as quickly as their support SLA allows — and that SLA is usually the first thing worth comparing between managed hosting providers.
What managed hosting does not cover: content management (adding pages, updating copy, changing images), SEO work, marketing or analytics setup, or application-level code changes. The line between infrastructure management and site management is where managed hosting stops. For anything beyond infrastructure, you need a developer, a maintenance plan, or both. What's included in a website maintenance plan →
This tier is the right choice for most serious small business sites. The cost is meaningful but not large in the context of a business that uses its site to generate revenue. A few hosting tiers up from shared, managed hosting eliminates the most common causes of site problems (expired SSL, missed backups, outdated PHP creating security gaps) without requiring you to know anything about Linux server administration.
This is what ArdinGate's hosting plan provides: managed hosting on a dedicated Hetzner VPS with nightly backups, uptime monitoring, SSL management, and access to monthly content edits as part of the plan. See hosting plan details and pricing →
4. Dedicated and cloud hosting: the high-end tier ($100–$500+/month)
Dedicated hosting means you have an entire physical server to yourself. No virtualization layer, no shared hardware, full control over every configuration parameter, and the maximum possible performance from the underlying hardware. For sites with consistent high traffic, applications with strict latency requirements, or workloads with specific security and compliance mandates (HIPAA, PCI-DSS), dedicated hardware is the appropriate level.
The cost reflects the infrastructure: you're renting an entire server, not a fraction of one. Entry-level dedicated servers start around $80–$120/month for older hardware; modern high-performance dedicated servers for demanding workloads run $200–$500+/month. Managed dedicated hosting (where the provider handles OS and server-level maintenance) adds 30–50% on top of the hardware cost.
Cloud hosting from AWS, Google Cloud Platform, Microsoft Azure, and similar providers offers elastic infrastructure that scales on demand. Need twice the compute for a traffic spike? Add it in minutes and pay for the runtime, then scale back down. This model is extremely powerful for variable workloads and applications with unpredictable traffic patterns. The billing model is the complexity: costs scale with usage, and a configuration mistake or unexpected traffic event can produce an unexpected bill. Cloud hosting at scale almost always requires either a DevOps engineer or a managed service layer (like AWS Amplify or Google Cloud Run's abstracted interfaces) to stay cost-predictable.
For the vast majority of small business sites, neither dedicated servers nor cloud hosting is necessary. A well-configured managed VPS handles tens of thousands of monthly visitors without strain. The upgrade makes sense when you've actually hit the ceiling of a VPS — consistently maxed-out CPU and RAM even after code optimization — not before. Jumping to dedicated or cloud hosting before you need it is a reliable way to spend two to five times more on infrastructure than the site requires.
5. What the sticker price doesn't include
Hosting sticker prices are often misleading because they're promotional rates (renewable at a higher rate after the first year), they assume annual prepayment to get the advertised price, and they exclude several things you'll need to add separately. Here's the complete list of what to budget beyond the hosting line item.
Domain registration: $10–$20/year. Your domain name is a separate product from hosting. Many hosts bundle a "free domain for year one" as a promotional offer, which is fine — just check the year-two renewal price before you commit. More importantly, keep your domain registered through a registrar you control directly (Cloudflare Registrar, Namecheap, Porkbun) rather than through your hosting provider. If you ever need to move hosts, a domain registered through your host can complicate the transfer. If the relationship ends badly, recovering a domain registered in someone else's account requires legal process, not technical steps.
Security certificate (SSL): usually free, but needs to be monitored. Security certificates are effectively free through modern certificate authorities, and professional managed hosts include them automatically. Where they become a hidden cost is when a host charges for them separately (a red flag), or when nobody is watching for renewal. An expired security certificate produces a scary full-page browser warning that stops visitors dead. Managed hosting plans handle automatic renewal. On cheap shared hosting or unmanaged servers, you're responsible for renewal yourself — easy to forget, expensive when it happens.
Business email: $6–$18/month per inbox. Web hosting and email hosting are fundamentally different products. Cheap shared hosting plans often include "free email" — what that means in practice is email through the same server as your website, with weak spam filtering, low storage limits, and no reliable mobile sync. For any business using email to communicate with clients, Google Workspace ($6/user/month) or Microsoft 365 Business Basic ($6/user/month) is the right answer. Separate email infrastructure from web hosting — if your host has a problem, your email still works.
Backups: verify explicitly. "We have backups" and "your data is safe in a recoverable form" are not the same statement. Before you rely on a host's backup system, get specific answers: backup frequency (daily is the minimum), retention period (how many days of history are kept), and storage location (backups stored on the same server as your site don't protect you if the server fails). The right answer is: daily automated backups retained for at least 7–14 days, stored on a separate system from the site's primary server. Some hosts charge extra for this; managed hosting plans typically include it.
Content delivery network (CDN): free to $30/month. A content delivery network serves your site's images and style files from servers around the world, positioned geographically close to each visitor. This dramatically improves page load times for visitors far from your primary server and reduces the amount of traffic your server has to handle. Cloudflare's free tier covers this for most small business sites and adds protection against denial-of-service attacks as a bonus. Some managed hosting plans include this service built in. If your host doesn't offer it and you're not using Cloudflare, you're leaving easy performance gains on the table.
Adding domain registration, email hosting, and adequate backups to a $5/month shared plan usually lands you at $30–$40/month before you've gotten reliable support or uptime monitoring. At that total, managed hosting starts looking like a better deal across every dimension.
6. How hosting affects site speed and your Google ranking
The connection between hosting and your Google ranking is meaningful but indirect. Your host doesn't rank your site. What your host controls is the infrastructure that produces the performance signals Google measures. Bad hosting suppresses your ranking by creating slowdowns and downtime; good hosting enables the speed and reliability that Google wants to see — a prerequisite for competitive rankings, not a guarantee of them.
How fast your site responds to visitors. When a visitor clicks on your page, the server needs time to wake up and send back the first bit of data. This response time is influenced by server processing speed, the distance between the visitor and the server, and how busy the server is. Google wants this to be fast — under 200 milliseconds is excellent, under 800 milliseconds is acceptable. On shared hosting with inconsistent server load, this response time can spike to 1–3 seconds during peak periods, which drags down your Google ranking scores. On a well-configured dedicated server or a fast CDN (a network that delivers your site from locations near your visitors), response time stays under 200ms consistently.
Uptime and how often Google can find your site. Google's automated crawler visits your site regularly based on how reliable and frequently updated it appears to be. If the crawler repeatedly gets errors or timeouts when trying to reach your pages — because your shared host is down or slow — Google treats your site as unreliable and stops checking as often. Fewer visits from Google's crawler means new content takes longer to show up in search results and older content may be stale. Most managed hosting setups maintain 99.9% uptime or better; shared hosting often delivers 99.0–99.5%, which can mean 4–43 hours of downtime per year. That's not catastrophic on its own, but if the downtime overlaps with Google's crawler visits, your rankings suffer.
Where your server is physically located. A server in Germany serves German visitors fast and Australian visitors slow. Physical distance adds delay that no code trick can fully eliminate. If your customers are concentrated in a specific region, hosting in or near that region is a real performance win. A content delivery network (a system that spreads your files across locations around the world) helps with images and static files but not with custom page generation, which always happens on your primary server. For a business focused on the US market, a US-based server is all you need.
How new your server's software is. Older server software runs code slower. Newer versions run the same code 20–30% faster. Shared hosts often lag behind on software updates because updating for hundreds of accounts at once risks breaking sites that use outdated code. Managed hosting (where you control your own server's software version) keeps you on current versions, which means faster page loads and fewer security gaps.
7. How much traffic can each hosting tier actually handle?
Traffic capacity is one of the most misunderstood aspects of hosting. The numbers below are general estimates for a well-built, performance-optimized PHP site with a CDN serving static assets. Poorly optimized WordPress sites with unindexed database queries and no caching will hit ceilings much sooner.
Shared hosting: roughly 500–5,000 monthly visitors before degradation. The ceiling varies by host and by your server neighborhood, but most shared hosting plans are designed for low-volume sites. Above a few hundred daily visitors, you'll see inconsistent response times and risk hitting resource limits that some hosts enforce by throttling or temporarily suspending the account.
Entry-level dedicated server: 20,000–100,000 monthly visitors comfortably. With a content delivery network serving images and files from locations near your visitors, and memory caching for frequently accessed data, an entry-level dedicated server handles substantial traffic without slowdown. This exceeds what virtually every small business website needs and covers most mid-sized businesses. The real ceiling isn't the server hardware — it's usually slow database lookups or missing performance optimization that limits how many visitors you can handle.
Mid-tier dedicated server: 100,000–500,000 monthly visitors. With proper optimization, a well-configured mid-tier server handles traffic at a level that most small businesses will never reach. Speeding up database queries, caching frequently-accessed data, and running a content delivery network in front of all images and static files gets you most of the way to this ceiling without redesigning the entire site.
When to upgrade. The right signal to upgrade is sustained high server load during your typical daily traffic, not during occasional spikes. If your server consistently runs at 80%+ CPU usage and 90%+ memory usage under normal traffic, add more processing power before your visitors start experiencing slowdowns. A single traffic spike doesn't warrant an upgrade; a consistent baseline that's maxing out your hardware does. Before upgrading, check whether the problem is inefficient code: slow database lookups, unoptimized images, or missing performance caching. A bigger server won't fix those problems — only code changes will.
8. Switching hosting providers: how hard is it?
Switching hosts is a question people avoid asking before they sign up, which means they often discover the answer at the worst possible time. How difficult a migration is depends almost entirely on who owns the code and who controls the domain.
Hand-coded PHP site you own outright. This is the easiest migration scenario. The process: copy the site files to the new server, set up a matching PHP version and web server configuration (Nginx or Apache), update DNS to point the domain at the new server's IP, and verify SSL on the new host. For a simple PHP site without a database, a competent developer can complete this in a few hours. A database-backed site adds a database export and import to the checklist. Total elapsed time from decision to live on new host: commonly one to two days including DNS propagation.
WordPress site. WordPress migrations are more involved because of the database, the wp-config.php file that holds database credentials, and the common issue of hardcoded absolute URLs in the database that need to be updated after the move. Plugins like Duplicator and All-in-One WP Migration automate much of this, but they require someone who knows what they're doing. The bigger migration risk for WordPress is plugin compatibility: a different PHP version on the new host can break plugins that weren't tested against it. Plan for testing time, not just transfer time.
Page builder sites (Wix, Squarespace, Webflow CMS). These can't be migrated. The code is proprietary to the platform and the platform is the host. They're the same product. If you want to leave Squarespace for a different host, you're rebuilding from scratch. This is the most underappreciated cost of renting a platform: the exit cost is zero if you stay, and very high if you leave. For a Squarespace site you've built for three years with extensive content, "just migrate it" means a complete rebuild project. Custom code vs. page builders: the full comparison →
Domain transfer complication. If your domain is registered through your current hosting provider (not an independent registrar), the migration involves two separate processes: transferring the registration to a new registrar and moving the site files to a new host. Transfers require an authorization code from the current registrar and take 5–7 days by ICANN policy. It's manageable but slow. Avoid it by registering your domain through a registrar you control independently of your hosting relationship. Namecheap, Cloudflare Registrar, and Porkbun all offer no lock-in.
The tactical summary: own your code, control your domain at an independent registrar, and ensure your host doesn't hold either as leverage. Those three things make any hosting migration a logistics task rather than a hostage negotiation.
9. Hosting cost comparison: what you get at each tier
The table below maps price to the things that matter for a business site: performance consistency, who manages the server, traffic ceiling, and what you're responsible for. Use it to verify you're on the right tier — or to make the case for an upgrade to someone who's only looking at the monthly line item.
| Tier | Price range | Resources | Traffic ceiling (optimized PHP) | Who manages the server | Right for |
|---|---|---|---|---|---|
| Shared | $3–$15/mo | Shared pool; no guarantees | 500–5,000 visitors/mo | Host (basic; reactive) | Portfolios, placeholders, dev environments |
| Unmanaged VPS | $5–$30/mo | Dedicated vCPU + RAM | 20,000–100,000+ visitors/mo | You (root access, all tasks) | Developers comfortable with Linux admin |
| Managed VPS | $30–$100/mo | Dedicated vCPU + RAM | 20,000–100,000+ visitors/mo | Provider (SSL, backups, updates, monitoring) | Most small business sites — the right default |
| Dedicated server | $100–$300/mo | Full physical server | 500,000+ visitors/mo | Varies (managed add-on available) | High-traffic sites, compliance-sensitive workloads |
| Cloud (AWS/GCP/Azure) | $50–$500+/mo (usage-based) | Elastic; scales on demand | Scales arbitrarily with spend | You or a DevOps engineer | Variable-traffic apps, enterprise workloads |
The managed VPS row is the right answer for most small business sites. The gap between unmanaged VPS ($5–$30) and managed VPS ($30–$100) isn't the hardware — you get the same underlying server. The premium buys you someone who owns the reliability, security, and maintenance tasks. For most site owners, that's better value than the time required to handle those things yourself.
Two line items the table doesn't show: domain registration adds $10–$20/year regardless of tier, and business email (Google Workspace or Microsoft 365) adds $6–$18/month per inbox. Add both before comparing plans — they shift the true monthly cost of cheap shared hosting considerably closer to managed VPS pricing.
10. Common hosting questions
For most small business sites that generate leads or revenue, $30–$75/month for managed hosting is the appropriate range. That gets you SSL certificate management, nightly backups with offsite copies, uptime monitoring, and someone to call when something breaks. Shared hosting at $3–$15/month is adequate only for very low-traffic, low-stakes sites where downtime has no real consequence. The math is straightforward: if one missed contact form or one hour of downtime costs you more than the monthly hosting premium, the upgrade pays for itself. If your site is a static placeholder that no one is actively driving traffic to, shared hosting is fine until the site starts doing real work.
It depends on what the site needs to accomplish. A personal portfolio or low-traffic informational page? Shared hosting is fine — the performance inconsistency rarely matters. A lead-generation site where a slow load or missed contact form costs real money? Shared hosting introduces risks that managed hosting eliminates for a few dollars a day. The specific problems: you share a server with hundreds of other sites and have no control over them. A poorly written script on a neighbor's site can spike server load and slow yours down. Shared hosts also often run outdated PHP versions (creating security gaps), have ticket-based support with multi-hour response times, and don't proactively monitor your uptime. None of these are individually catastrophic, but they compound under a site doing business-critical work.
At a minimum, managed hosting covers: SSL certificate installation and auto-renewal (so your site never shows a browser security warning from an expired cert), nightly backups with copies stored offsite (not on the same server as your site), uptime monitoring with alerts when the site goes down, and server software updates including PHP version management. Better plans add firewall configuration, malware scanning, performance tuning, and a real support contact rather than a ticket queue. The key distinction from unmanaged hosting is accountability: someone owns keeping the infrastructure healthy. On unmanaged hosting, that someone is you. Before signing up, ask specifically: what's the backup frequency, how long are backups retained, and where are they stored? "We have backups" is not the same as "daily encrypted backups retained for 14 days, stored in a separate region from your primary server."
Yes, indirectly but meaningfully. Hosting affects two things Google measures: site speed and uptime. Site speed — specifically how fast your pages load and how quickly they respond to clicks — is a confirmed Google ranking signal. Shared hosting with inconsistent server response times makes pages slow, which drags down your Google ranking. Uptime matters because Google's crawler visits your site on its own schedule. If your host has frequent downtime and the crawler repeatedly can't reach your pages, Google treats your site as unreliable and stops checking as often, slowing how quickly new content gets indexed into search results. A faster, more reliable host won't magically boost rankings, but hosting problems that cause slowdowns and downtime actively suppress your rankings over time. Fix hosting before worrying about other SEO variables.
Technically possible, practically a bad idea for any business site. Home internet connections have several disqualifying problems: residential internet providers throttle upload speed (the speed at which your site serves traffic to visitors), uptime guarantees don't exist on residential plans, your IP address changes frequently and causes complications when moving between networks, and there's no backup if your router or modem fails. Beyond internet quality, you'd be responsible for your own security certificates, firewall configuration, intrusion detection, server software updates, and backups. The security work alone is substantial and constantly maintained by dedicated teams at professional hosting companies. The cost savings evaporate fast once you account for your time, hardware, electricity, and the business risk when things break.
These aren't mutually exclusive — a VPS is an architecture and managed is a service level, and you can combine them. A VPS (Virtual Private Server) gives you a dedicated virtualized slice of a physical server with your own guaranteed CPU cores and RAM. Managed hosting means the provider handles server configuration, software updates, security, and backups for you. An unmanaged VPS gives you root access and nothing else — you handle everything at the server level. A managed VPS puts a management layer on top of the VPS infrastructure. For small business site owners who don't want to learn Linux server administration, managed VPS hosting from Cloudways or similar providers is the practical answer: dedicated resources without the administration burden. ArdinGate's hosting plan runs on a managed VPS setup on Hetzner infrastructure, which is where the price-to-performance ratio is strongest for small business sites.
For a custom-built site you own outright, switching is straightforward: copy the site files to the new server, configure the new server to match the old one's setup, update your domain's configuration to point at the new server, and verify your security certificate. Total work is a few hours for a simple site. The complication comes if your current host controls your domain registration (not just pointing it at your site, but actually owning the domain registration), which makes transfers slightly more bureaucratic but not impossible. WordPress sites take longer because of database migration. Page builder sites (Wix, Squarespace, Webflow) are impossible to move — the code is owned by the platform. Moving away means rebuilding from scratch. This lock-in is one of the most underappreciated reasons to own a custom-built site instead of using a page builder.
Usually not until traffic grows substantially. A well-built dedicated server running a custom PHP site can handle tens of thousands of monthly visitors without strain. The upgrade signals to watch for are: your server consistently running out of memory or processing power under typical traffic (not just during spikes), your pages getting visibly slow when traffic picks up, and database queries slowing down as your content library grows. The right response to growth is usually adding more RAM and processing power to your existing server before redesigning the site's architecture. Most small business sites never outgrow a mid-tier server. If you're running lots of images or video, a content delivery network (a system that spreads your files across locations worldwide) solves most bandwidth problems without needing a server upgrade.