"We need a website" covers two different purchases, and Perth businesses often buy one while assuming it includes the other. Building is the pages: the words, the layout, the forms, the photos. Business website hosting is where those pages run, how they stay online, and who can put them back when something breaks. A designer who is good at the first may be a poor fit for the second. A host who is good at the second will not write your service pages.
You can see the split when something goes wrong. The phone number on the site is wrong: that is content, a build or an edit. The site will not load at all: that is hosting, DNS, or the server. The site loads and then looks broken after an update: that can be either, and arguing about which is how a Friday afternoon disappears. Knowing the split in advance is cheaper than discovering it during the outage.
What building includes
A build, whether you do it in a website builder or pay someone, produces the thing visitors see. Done properly it includes the page structure, the words, the way the site behaves on a phone, the enquiry form, and the basic technical tags a search engine needs. It should also include a list of old addresses if you are replacing a site, so people and Google do not hit a dead page. That work is website design. It has a start and a finish. When the site is launched and the logins are handed over, the build is over unless you have agreed a change budget.
Building does not, by itself, renew your domain next year. It does not notice that a contact form plugin stopped sending mail. It does not restore yesterday's pages if today's edit wrecks them. Those are operating tasks. Folding them into "the designer will just handle it" without a written arrangement is how both sides end up annoyed.
What hosting actually is
Hosting is the service that answers when a browser asks for your domain. At the small-business end it is some combination of:
- A place the files or the platform run, with enough resources that the site is not fighting its neighbours.
- DNS, the records that point the domain at that place, and at your email if mail is elsewhere.
- A TLS certificate so visitors are not warned that the connection is unsafe. "Free SSL" is normal now. An expired one is still a problem.
- Backups that live somewhere other than the live machine, and a way to restore them.
- Updates to the platform, if you are on WordPress or something like it. A static site has far less of this.
- Someone to talk to when it is down, during the hours your business actually cares.
"Unlimited" traffic and "unlimited" storage on cheap plans are marketing words. Every host has a point where a noisy neighbour, a broken plugin, or a genuine traffic spike gets you throttled or suspended. You do not need a giant plan for a brochure. You do need to know what happens if the site is suddenly busy, and you need the plan to include backups rather than a footnote that backups are your problem.
Where the server sits
For a business whose customers are in Perth and WA, a server in Australia is the sensible default. The round trip is shorter than to a budget box in another hemisphere, which visitors feel on image-heavy pages and on mobile. Keeping the site's files in Australia also matches what many clients expect when they ask where their data goes. It is not a magic ranking switch, and it does not fix a slow theme. Stride IT's website hosting uses Australian servers for that reason, with daily backups and certificates included rather than added as a surprise.
Offshore hosting is not automatically negligent. A platform you have chosen, such as a hosted builder whose servers are overseas, can still be the right tool if the pages are light and the operational side is clear. The mistake is choosing the cheapest offshore plan by habit, then wondering why the site feels sticky for local customers and why support replies arrive outside your business day.
Email is a third job
Website hosting and email hosting get bundled in old cPanel plans, and then get split the first time someone moves the site. Mail for a real business belongs in Microsoft 365 or Google Workspace, with the domain's MX records pointing there. The website can move without touching those records. If a well-meaning person "just updates the nameservers" during a redesign, mail can stop while the new homepage looks great. Before any move, write down where mail is, and test sending and receiving after the change. Do not discover it on Monday when the quotes are bouncing.
Who is responsible when it breaks
Write this down while everyone is still polite. A simple split that works:
- The business owns the domain registration. Not the designer, not a former staff member.
- The host is responsible for the server, the certificate, the backups, and telling you when the plan will renew.
- The person who can edit content knows how, and knows what they must not edit.
- Platform updates, malware cleanup, and form testing are either in a maintenance agreement or explicitly left with you. Silence means they will not happen.
- There is one phone number for "the site is down" during business hours, and you know what after-hours means.
If the same company builds and hosts, that can be simpler. It is still two jobs, and the invoice should not hide which one you are paying for. If they are different companies, introduce them. The classic failure is a designer blaming the host and a host blaming the theme, while the business just wants the contact page back. Our maintenance notes in why a site needs ongoing care and the maintenance service are about that gap. A build without a caretaker is a project. A host without updates on a WordPress site is a countdown.
Different sites, different hosting
A static site, built as plain pages and put on a CDN, has little software to patch. Hosting it is mostly "is it published, is the certificate valid, can we roll back a bad deploy". That is a good fit for brochure sites and for many trade and professional sites that do not need a login. A WordPress site needs a place that runs PHP and a database, updates that are tested, and a backup taken before those updates. An online store adds payment, stock, and a stronger reason to care about uptime during a campaign. Do not buy store hosting for a five-page brochure, and do not put a store on a plan that suspends you for using the database.
Moving hosts is ordinary. It goes badly when nobody has a backup, when email is tangled up with the old server, or when the domain is locked in an account you cannot access. Before you agree to a move, ask for the steps in writing: backup, a test address, DNS cut-over, mail check, and what the rollback is if the new copy is wrong. "We will just point it over on the weekend" is not a plan if Monday's bookings depend on the site.
What to check on the plan you have
- Whose name is on the domain, and which email receives the renewal?
- Where does the site run, in which country, and how do you log in?
- When was the last backup, where is it, and has anyone restored it?
- When does the certificate expire, and does it renew on its own?
- Where does email go, and is that separate from the website server?
- Who applies updates, and what is the arrangement if a plugin update breaks a page?
- What do you pay at renewal, not just this year?
If you can answer those, you are in better shape than most businesses that "have a website guy". If you cannot, the next step is not a redesign. It is getting the logins and the backups into the business's hands. Design changes on top of a site you cannot restore are how a small edit becomes a rebuild. The design-versus-DIY side of that choice is in website design versus DIY.
Questions that save a move
If my web designer hosts the site, is that enough?
Sometimes. Ask where it actually runs, who can restore a backup, what happens if that person is away, and whether the domain is in your name. "We host it" can mean a proper server with backups, or it can mean a login only they know. Those are not the same product.
Does the website host also host my email?
Not necessarily, and for most Perth businesses email should not live on the same little server as the website. Microsoft 365 or Google Workspace are the usual homes for mail. The website host only needs to publish the right DNS records so mail keeps flowing. Mixing the two is how a website move accidentally breaks email.
Is Australian hosting worth it?
For a site whose visitors are mostly in WA, a server in Australia usually responds faster than one in the US or Europe, and it keeps the copy of the site in the country. It does not, by itself, make the site well designed or secure. Location is one decision. Updates, backups, and who you call are the others.
What is a reasonable backup?
A copy taken automatically, stored somewhere that is not the same machine as the live site, and a restore that someone has actually tried. A backup on the same disk as the website does not help when that disk fails. "We can probably roll back" is not a backup policy.
Want hosting that is separate from the design argument?
Australian servers, certificates, daily backups, and a local team who will say if the site itself is the problem.
Website hostingRelated reading
Stride IT hosts websites on Australian infrastructure and builds them when a build is actually needed. If you are unsure who currently holds the site, contact us with the domain name. The first job is usually finding the logins, not redesigning the homepage.