Shared Hosting
Whether it is enough for you, the signs you have outgrown it, and why a slow site is usually the site rather than the plan.
Read the guideWeb hosting for small business is renting the machine that answers when somebody types your address. Here is what you are actually paying for, how to pick a plan by what your site does, and how to move from another host without losing your email.
Every website sits on a computer that stays switched on and connected to the internet. When a visitor types your address, that computer answers and sends back the pages and images that make up your site. Hosting is renting space on that machine, along with the people who keep it running.
Hosting is not the same purchase as your domain name. The domain is the address; the hosting is the building the address points at. You can hold an address with nothing built on it, which is why a newly registered domain shows a blank or parked page. If that split is still fuzzy, read domain name vs web hosting first.
Your website files could sit on the laptop in your office. They do not, because visitors need something awake at three in the morning that answers quickly from anywhere and does not go down when somebody unplugs a power strip. Hosting is paying for a machine like that instead of running one.
That is also why it is a recurring cost. The server has to stay powered, patched, monitored and backed up every day your site is live, so it is billed monthly or yearly for as long as the site exists. Treat the renewal the way you treat the domain renewal: card current, notices going somewhere a person reads. A lapsed hosting bill takes a site offline as effectively as a lapsed domain does.
You need a plan if your website is a set of files that has to live somewhere: most sites a designer builds for you, every self-hosted WordPress site, anything with a shopping cart or a database, and any business taking its site off a platform it has outgrown. Just as usefully, here is when you do not need one:
We would rather say that now than sell you a server with nothing on it.
Hosting is usually advertised on storage and bandwidth, because those are easy to print in big numbers. For an ordinary business site, neither is what will limit you. What decides which plan fits is what the site does, and who is on the hook for keeping its software patched.
| Plan type | What it suits | Who maintains the software | What makes you outgrow it |
|---|---|---|---|
| Shared hosting | Brochure sites, local service businesses, steady and modest traffic | You, or whoever built the site. The host maintains the server, not your site | Sustained traffic, a store, or a site that grew into an application |
| WordPress hosting | A WordPress site somebody at the business updates themselves | A plan arranged around one piece of software, so the version running your site does not quietly fall years behind | The same pressures as shared hosting, plus plugin-heavy sites needing more headroom |
| Business hosting | Stores, busy sites, and sites that got slow on a shared plan | You keep the site current; the plan gives it more room to run | Genuinely heavy or specialised workloads, where a managed server is the next step |
Your site sits on a server alongside other sites and shares its processor, memory and disk. Think of an office building: your suite is yours, the lift and the heating are everybody's. It is the entry-level way to be online, tenants are kept separate from one another, and the trade-off is capacity, and it is the right answer for most small business websites. The trade-off is capacity, which is why hosts cap what any single site may consume.
Sites rarely announce that they have outgrown a plan. They just get slower. The signals worth watching:
Before buying a bigger plan, check whether the site is the problem. Uncompressed images and a long plugin list are slow on any hardware, and a costlier server just makes them slow more expensively.
Shared hosting arranged around one piece of software, with core updates and caching handled for you so the version running your site does not quietly fall years behind. Worth paying for when the site runs WordPress and nobody wants to think about update notices. Not worth paying for otherwise: a hand-built site gains nothing from a plan tuned for a content management system it does not use.
More dedicated resources without you having to administer a server. The honest reason to be on it is that something specific pushed you there: a store, a genuinely busy site, or an application that slowed down where it used to be quick.
The poor reason is buying it before launch in case the site takes off. Moving up later is a straightforward job. Years of unused capacity is money you do not get back.
Brochure site, WordPress site or store. That single answer picks the plan better than any specification on a comparison chart.
The domain has to be told where the website now lives, which means changing its DNS records or its nameservers. This is the step people get stuck on, and where a careless change takes email down along with the site.
Install WordPress and build there, or upload the files your designer produced, whether that is our own design side at aldomedia.com or somebody else. Any database is created and connected here.
Install the certificate so browsers stop showing the "not secure" label. SSL certificates are a separate product from hosting, and every site needs one, including sites with nothing but a contact form.
Confirm backups are running, that they include the database and not just the files, and that somebody can actually put the site back.
Migrating a website is mostly an exercise in doing things in the right order. The site itself copies across without much drama. What breaks, when something breaks, is email, and for a predictable reason: somebody rebuilt the DNS at the new host from scratch and left the mail records out.
Two rules prevent almost every migration disaster. Keep the old service running until the new one is proven, and never move the hosting and transfer the domain in the same session. Everything else is sequence.
The full order of operations, the pre-flight checks, how to test the new site before anything public points at it, and what to verify before you cancel the old account are on the website migration checklist. If the mailboxes are moving too, treat that as its own piece of work and follow email migration step by step rather than doing both in one afternoon.
If you are also moving the domain to a new registrar, do that as its own step rather than alongside the hosting change. How to transfer a domain explains the procedure and the order that keeps the site up.
Every host talks about backups. The specific questions are better ones. Are the copies kept somewhere other than the server they came from? Do they include the database as well as the files? How far back can you go, so an infection that sat unnoticed is still recoverable? Who can trigger a restore?
Then do the thing almost nobody does and restore one. A backup nobody has ever restored is a rumour, not a safety net. Malware scanning and cleanup sit alongside it on the website security page.
AldoMedia has been building and maintaining websites for Western New York businesses since 1999. Hosting was something we managed for our own clients long before we offered it on its own, which is why the help here is practical rather than scripted: choosing the plan that matches the site, setting up the DNS, copying an existing site across, and being reachable when something needs changing.
We are an independent authorised reseller for these products, not the operator of the underlying platform. What we add is the setup, the judgement about which plan you need, and a phone number in Buffalo. Call 716-771-2536, describe what you have now, or read the support pages first if you would rather.
No. Those platforms include the hosting in what you already pay them, so a separate hosting plan would sit empty. You still need your own domain name, and it is worth holding that at a registrar rather than inside the platform, so you can point it somewhere else if you ever leave.
They are two separate things, even when a host bundles a domain with a plan. The important question with a bundled domain is whose name it is registered in and whether you can move it out later. Check that before you rely on the bundle.
Usually yes, if you copy first and switch last. Build a working copy on the new server, test it there, then change the DNS so visitors start arriving at the new one. The site stays up because the old server keeps answering until the change reaches each visitor.
The usual signs are pages that slow down at your busiest hours, an admin area that lags when you edit, backups that fail to finish, or notices from the host about resource limits. Before buying a bigger plan, check whether the site itself is the problem, because oversized images and heavy plugins are slow on any hardware.
Nothing, as long as the mail records in your DNS are recreated exactly as they were. Email breaks during a migration when somebody rebuilds the DNS zone from scratch and leaves out the MX and authentication records. Write the existing records down before you change anything.
Each of these goes further than this page does on one thing.
Whether it is enough for you, the signs you have outgrown it, and why a slow site is usually the site rather than the plan.
Read the guideWhat a WordPress-tuned plan arranges for you, and the question that actually decides it: who is responsible for the updates.
Read the guideA checklist you can work from, with the order of operations that keeps your email alive through the move.
Read the guideEighty-three guides written for one trade each: what a restaurant, a law firm or a funeral home actually needs from a website, and what each one can safely skip.
Find your tradeIf your business is on that list, start there. The advice is the same underneath, but the thing that usually goes wrong is not. There are also pages for 80 US cities, if you would rather start from where you are than from what you do.
Why they are separate purchases, and what happens when you buy only one.
Read the guideRegistering, transferring and renewing the name your hosting points at.
Read the domains guideMailboxes on your own domain, and the part of a migration that needs its own plan.
About business emailAlso worth reading: SSL certificates for the HTTPS side of a launch, website security for backups and malware, or all of the guides.
Tell us what the site has to do and we will tell you which hosting fits, including the times when the honest answer is that you do not need to move at all.