Suits it well
- Local businesses whose busy hour is a spike in phone calls, not traffic.
- Visitors arriving steadily through the week rather than all at once.
Shared hosting: is it enough for a small business website? For most it is, and they never need anything else. This page is for working out whether yours is one of them, and what to do when it feels slow.
The web hosting guide covers where shared sits alongside the other plans. This is the closer look.
Your site lives in its own account on a machine that also holds other people's accounts. Split honestly, that means:
On a properly configured shared server, accounts are walled off from each other, so another customer is not browsing your files or reading your database. The fear people arrive with is the wrong one: the real risk to a shared site is its own out-of-date software, which is what website security covers.
You are buying a share of capacity, not a guaranteed amount of it. The arithmetic works because websites are quiet most of the time: yours sits idle while somebody else's is busy. That holds until your site stops being quiet.
The phrase means one account suddenly doing far more work than usual, and everybody else feeling it as a slower site. It is real, and less common than forum threads suggest. It is also not unique to shared hosting: unless you rent a whole machine, something is shared.
No host removes the effect entirely. Expect it to be bounded and occasional, not absent.
It is very good at what most business websites do: serve a modest number of pages to a modest number of people, reliably, while somebody else patches the server.
If your site is a set of pages about what you do, where you are and how to reach you, shared hosting is the right size rather than a compromise.
The hosting guide lists the usual signals. Two more belong beside them, because they are the ones people read wrongly:
One sign on its own is a symptom, not a verdict. Several of them repeating over weeks is a plan that no longer fits.
Most shared control panels keep a usage history: processor time, memory and processes running at once, plotted against your account's ceiling. Read the shape, not the height. A line that touches the ceiling for a few minutes a week is a plan doing its job; one that sits along it every weekday afternoon is a plan that has run out. Note the hours the peaks land in and work out what runs then: a backup, a feed import, or your own busiest traffic. If the panel shows nothing of the sort, ask the host where the usage figures live.
Read it properly first. A useful notice tells you which account hit the ceiling and when; if yours does not, ask the host for that detail. Then send something checkable rather than an opinion: the time window, what the site was doing in it, and your usage graph for the same window. Ask which resource hit its ceiling, and whether it was one request or a pattern. One request once is a page to fix. Every afternoon is a plan to change.
| What changes | Shared hosting | A larger plan |
|---|---|---|
| What you are buying | A share of one machine's capacity | More capacity set aside for your site |
| Who keeps your site's software current | You, or whoever built it | Unchanged, still you |
| Traffic arriving in bursts | The weak spot | Handled with more room to spare |
| A bloated, unoptimised site | Slow | Still slow |
| Ongoing cost | The entry tier | Higher, every month, for as long as the site exists |
Notice how many rows say the same on both sides. Moving up buys headroom, not maintenance, and not speed the site cannot produce.
Less than people expect, which is why buying capacity years early rarely pays. With the same host, a plan change is usually an account move rather than a rebuild: files and databases are copied across, the site is tested on the new plan while the public one carries on, and only then is the switch made. Mailboxes and the domain generally stay put. Changing host as well is the longer job, and the order that keeps mail alive is in website migration.
In most cases the plan is not the problem. Work through this in order, or hand it to whoever maintains the site.
Once first thing, once at your busiest hour. If both are slow, the site is slow all the time and capacity is not the issue.
The usual cause. A photo straight off a phone is many times larger than a web page needs, and compressing them often takes a site from sluggish to quick.
Sliders, page builders, chat widgets, popups and analytics stacked on analytics add work to every view. Fonts, maps, video embeds and review widgets are worse, because the visitor waits on another company's server and no hosting plan fixes a slow third party.
Caching serves a ready-made copy instead of building the page every time. It is the largest single saving most shared accounts have, and plenty of sites have the plugin installed and switched off.
Backups, feed imports and mailing tasks run on a timetable. Slow at the same minute past the hour is a schedule, not a neighbour, and it can usually be moved.
If the site is lean, cached and still meeting limits under ordinary traffic, the capacity problem is real and a larger plan is the right purchase.
The order matters. A bigger plan makes a bloated site slightly faster and permanently more expensive.
The specification on the sales page rarely decides anything. These questions do:
We have been building and maintaining websites for Western New York businesses since 1999, and shared hosting has been the right answer for most of the sites we build. If your site is slow, we would rather look at the site than sell you a bigger plan. We are an independent authorised reseller, so what we add is the setup, an honest read on which plan fits, and a phone number in Buffalo. Call 716-771-2536 and tell us what the site does, or start with the support pages.
Hosts do not usually publish that number and it changes as accounts come and go. It is also the wrong question. What matters is whether a ceiling is enforced per account, and how your own site behaves at your busiest hour.
Not on a properly configured server. Accounts are kept separate from one another, so a neighbour is not reading your files or your database. The realistic risk to a shared site is its own out-of-date software, not the account next door.
Only if capacity is what limits it. Oversized images, a long plugin list and slow third-party scripts are slow on any hardware, and a larger plan only makes them slightly less slow. Check the site first.
Pages usually slow down or queue for a short period, then recover once demand drops. Repeated limit notices are worth reading closely. A useful notice tells you which account hit the ceiling and when; if yours does not, ask the host for that detail.
WordPress runs on an ordinary shared plan, and most small WordPress sites stay on one. What changes on a WordPress plan is who does the updating, and that decision is set out in full on the WordPress hosting page.
The full overview: what hosting is and how the plans differ.
Read the hosting guideWhen a plan built around one piece of software earns its place.
Compare the twoMoving an existing site onto a new plan without taking the site or the email down.
How a migration worksAlso worth reading: domain name vs web hosting.
Tell us what the site does and how busy it gets. We will tell you which plan fits, including when you are already on it.