Web Hosting for Small Business: How to Size the Plan Before You Shop
Most small businesses overbuy hosting by one tier and underbuy it on the one specification that actually breaks their site. A $3-per-month shared plan and a $30-per-month managed plan differ far less in raw speed than the marketing implies; they differ enormously in PHP worker allocation, entry-process limits, and what happens on the day traffic triples. Sizing the plan against real numbers before opening a comparison page is what separates a host that lasts three years from a migration in month seven.
Start With Four Numbers
Before evaluating any host, write down four figures about the site being hosted. Every meaningful hosting decision falls out of them.
The four numbers: monthly visits, peak concurrent visitors, total storage including backups and media, and how much revenue an hour of downtime costs. The fourth one determines the budget; the first three determine the tier.
Monthly visits
Pull this from analytics rather than estimating. Hosts advertise monthly-visit allowances as the headline limit, and those allowances are the number most likely to be exceeded quietly and then billed as an overage or a forced upgrade.
Peak concurrency
This is the number that actually determines whether a site stays up. Average traffic is spread across a month; concurrency is what arrives at 9am after an email goes out. A site averaging 20,000 monthly visits with a flat distribution and one averaging 20,000 with a weekly spike need different plans, and only the second one will fail on shared hosting.
Storage including backups
Count the media library, the database, and the retained backups. Backup retention is where storage allowances are quietly consumed, particularly on plans where daily backups are stored on the same volume as the site.
Cost of an hour down
A brochure site for a local service business loses very little in an hour offline. A store taking orders loses the hour's orders plus the customers who do not return. That figure is what justifies moving from shared to managed hosting, and without it the upgrade decision is guesswork.
What the Tiers Actually Buy You
| Tier | Fits | Real Constraint | Where It Breaks |
|---|---|---|---|
| Shared | Brochure sites, low-traffic blogs, sites under roughly 25,000 monthly visits with flat traffic | PHP workers and entry processes, not disk or bandwidth | Concurrency spikes; a single slow plugin queues every other request |
| Managed WordPress | Business sites where downtime has a dollar cost; sites with a WooCommerce store under moderate load | Visit allowances and plugin restrictions | Overage billing on traffic spikes; disallowed caching or backup plugins |
| Cloud VPS | Multiple sites, custom stacks, predictable scaling needs | Your own administration time | Nobody patches the server unless you buy managed on top |
| Dedicated | Sustained high traffic or compliance requirements needing isolation | Cost and provisioning lead time | Almost always overbought by small businesses |
Pricing and plan structures change frequently. Pricing as of July 2026. Verify current pricing on the provider website before purchasing.
The Specification Nobody Advertises
Shared hosting plans are marketed on storage and bandwidth, and both are close to irrelevant for a small business site. A typical business site with 500 images and a year of backups uses a few gigabytes; every plan on the market covers that.
The constraint that determines whether the site stays responsive is the PHP worker count -- the number of simultaneous non-cached requests the plan will process. Static pages served from cache do not consume a worker. Logged-in users, cart pages, checkout, and search do. That is why a store on shared hosting can look fast in testing and fall over on a promotion: the tested pages were cached and the transactional pages were not.
Ask any prospective host two questions: how many PHP workers the plan allocates, and what happens when they are exhausted. Some queue, some return 508 errors, some throttle. Hosts that will not answer either question in writing are telling you something.
A useful sanity check: take the number of orders or form submissions the site handles in its busiest hour, and assume each one occupies a worker for one to two seconds. If that figure approaches the plan's worker count, the plan is already at its ceiling during normal operation and has no headroom for a promotion, a newsletter send, or a seasonal peak. Sites fail on the day they succeed, and shared plans are sized for the average rather than the spike.
Renewal Pricing Is the Real Price
Introductory shared hosting rates commonly run for the first term only, and the renewal rate is frequently two to four times the intro rate. A plan advertised at a low monthly figure for a three-year initial term renews at the standard rate for every term after, which means the honest comparison is the three-year total rather than the first-year cost.
Two practical rules. First, compute the total across the intro term plus one renewal term for every host being compared, and rank on that. Second, check whether the intro rate requires prepaying the full term -- most do, and a low monthly figure that requires 36 months up front is a different product from a monthly plan. The mechanics of this are covered in more depth in the guide to negotiating hosting renewal pricing before you renew.
What to Verify Before Buying
- Migration terms in writing. Free migration is common; the limits are not advertised. Confirm how many sites are included, whether it covers the database, and the turnaround.
- Backup location and restore process. Daily backups stored on the same server are not disaster recovery. Confirm off-server retention, how many days are kept, and whether a restore is self-service or a support ticket.
- The uptime guarantee's actual remedy. Most guarantees pay a service credit proportional to the outage, which for a small account is a rounding error. The guarantee number matters less than the measurement method, as covered in the breakdown of what an uptime guarantee actually means.
- Support channel and hours. Live chat at 2am and a ticket queue at 2am are different products. Confirm the channel, the hours, and whether the first line can escalate to a server engineer.
- Exit terms. Confirm you can export a full backup yourself without a support request, and check the refund window against the term length you are being asked to prepay.
- Whether staging is included. Any site that will be updated needs a staging environment. Buying it separately later usually costs more than the tier that included it.
Which Tier Is Right for You?
For a brochure or local-service site under about 25,000 monthly visits with no store, shared hosting is the correct answer and upgrading is wasted money -- the constraint will be the theme and plugins, not the server. For a business site where an hour of downtime has a measurable revenue cost, or a store processing orders through uncached pages, managed hosting earns its premium through PHP worker headroom and a support line that understands the stack. For multiple sites or a custom stack, a VPS sized for small business is generally more economical than stacking managed plans, provided someone is going to administer it. The distinction between the first two tiers is worked through in detail in the shared versus managed WordPress comparison.
Size against the four numbers first. A plan chosen against measured traffic and a known downtime cost rarely needs revisiting; a plan chosen against a price comparison usually does.
Compare hosting options on HostingDive -- with current intro and renewal pricing for shared, managed, and VPS plans.
Frequently Asked Questions
- Is shared hosting good enough for a small business?
- For a brochure or local-service site with flat traffic under roughly 25,000 monthly visits and no store, yes. The limiting factor is PHP worker allocation rather than storage or bandwidth, so the question is whether the site serves many uncached requests. A site that is mostly static pages served from cache runs fine on shared hosting.
- What actually causes a site to go down on shared hosting?
- Almost always exhausted PHP workers rather than exceeded bandwidth. Uncached requests -- checkout, cart, logged-in sessions, internal search -- each consume a worker, and when the allocation runs out requests queue or return errors. This is why traffic spikes break stores before they break blogs.
- Why is renewal pricing so much higher than the advertised rate?
- Introductory rates apply to the first term only and renewal commonly runs two to four times higher. Compare hosts on the total across the intro term plus one renewal rather than on the first-year figure, and check whether the intro rate requires prepaying 24 or 36 months.
- Do I need managed hosting for WooCommerce?
- It depends on order volume rather than on the platform. Store pages are largely uncacheable, so a store consumes PHP workers at a much higher rate than a content site at the same traffic. A low-volume store can run on shared hosting; one taking regular orders through checkout generally cannot without visible slowdowns at peak.
- How much storage does a small business site need?
- Less than any current plan offers. A typical business site with a full media library, database, and a year of retained backups sits in the low single-digit gigabytes. Storage allowances are a marketing specification rather than a real constraint, which is why they should not drive the tier decision.