Pick hosting that runs your site well and reaches your customers reliably. Then make sure someone owns upkeep and recovery. Compare the renewal bill, resource limits and support scope, not the signup price. If you're on Shopify or a suitable Webflow Site plan, hosting may already be covered.
Decide whether you need new hosting
Start with what's actually wrong, if anything. A hosted platform may already cover hosting. Your current host may also meet every critical need.
Staying put is a real answer. A move only pays off when it fixes a problem you can show. Our small business website guide covers the wider build decision.
Choose the hosting model your site needs
Hosting comes in five broad models. They overlap. Choose by what your site needs:
Model | Can suit | Check before choosing |
|---|---|---|
Shared hosting | Modest brochure or WordPress sites | CPU, memory and restore terms |
Managed WordPress | Owners who need defined help | Which tasks are included |
VPS or cloud server | Apps needing custom software | Who patches and operates it |
Managed cloud | Sites with proven capacity needs | Region, scaling and usage costs |
Hosted platform | Shopify stores and Webflow sites | Plan limits, extras and exports |
"Cloud" describes the infrastructure. "Managed" describes who does the work. A WordPress package can run on shared servers. A cloud server can still need a developer to run it. A common mistake is treating these as five steps every growing business must climb.
A virtual private server (VPS) doesn't necessarily come with dedicated hardware or a managed application. Ask who monitors it, patches it and fixes it when it fails.
Check what your platform already includes
Shopify's guide to improving your online store performance says your store is hosted on global servers. You don't buy separate hosting for the store.
Webflow works differently. A Site plan is what publishes a site to your custom domain. A paid Workspace plan covers collaboration and code export. On its own, it doesn't put a site on your domain.
A custom headless storefront is another matter. It can add separate infrastructure. Scope that part on its own.
Separate the services
A website rests on several services. Each can come from a different supplier:
The content management system (CMS) sits on top as the application. Keep a record of who controls each layer. If you're still choosing a platform, our platform comparison covers that decision first.
Compare the five providers on a dated basis
These five providers are a shortlist to investigate, not a ranking. We checked each page in October 2026. Every figure comes from the provider's own pages. We haven't tested speed or uptime.
We take no referral, reseller or affiliate income from these providers.
Before comparing anyone, ask each one for a quote that answers the same questions:
Provider and exact plan: [name]
Infrastructure and region: [service and location]
Currency and tax: [AUD or USD and GST basis]
First invoice: [amount and period covered]
Renewal: [rate, date and billing period]
Required extras: [itemised costs]
Management and support: [included tasks and exclusions]
Recovery and exit: [scope, timing and fees]
Don't fill a missing renewal figure with the signup price. Ask for it in writing. Never compare one provider's shared entry plan with another's cloud service on price alone.
Provider and plan | Price checked Oct 2026 | Location and note |
|---|---|---|
VentraIP Business Entry | $5.50 intro, $11 standard | Sydney listed on the plan |
SiteGround StartUp | $4.99, renews $26.99, ex GST | Sydney in its server list |
Cloudways Flexible | From US$11 a month, usage based | Sydney on all five clouds |
Digital Pacific Business Basic | $22.55 month to month | Primary services in Sydney |
DreamIT DirectAdmin Startup | $3.47 intro, $6.95 standard | Sydney, Melbourne or Auckland |
VentraIP
VentraIP's business hosting page shows Entry at $5.50 a month, against a standard $11. The fine print says the discount applies to the first invoice, for up to a year. Its terms of service say published prices include taxes unless noted. The plans list Sydney and Australian support.
It can suit a modest site on shared hosting. Confirm the invoice term before you buy, because it changes the price. We show why below.
SiteGround
SiteGround's Australian page lists StartUp at $4.99 a month, renewing at $26.99. Its plans are prepaid for 12 months and exclude GST. Only the two dearer plans list staging.
The sales page only says Australia. Its server locations page lists Sydney. Check the renewal closely, because it's more than five times the intro rate. It can suit a WordPress owner who has budgeted for that renewal.
Cloudways
Cloudways advertises Flexible hosting from US$11 a month. That's an entry headline, not a quote for your setup. Your chosen provider, server size and extras set the real price. Offsite backup storage adds US$0.033 per GB per server. Taxes and promotions change the bill too.
Its infrastructure list shows Sydney on all five cloud providers. Pay as you go means hourly billing. The bill moves with usage. It can suit a compatible site that needs more capacity and a defined management scope.
Digital Pacific
Digital Pacific's business hosting page shows Business Basic at $22.55 month to month. Prepaying lowers the monthly equivalent. One year costs $227.27, two years $405.85 and three years $527.59. The $14.66 a month figure needs that three year payment.
The page doesn't state GST or renewal terms. Its data centres page says primary services run in Sydney, with redundancy in Melbourne. Get a written quote before you treat any total as final.
DreamIT
DreamIT's $3.47 card is DirectAdmin Startup shared hosting, normally $6.95. Prices include GST. The discount covers the first invoice, up to 12 months. Its cPanel Startup plan is a separate card, at $4.47 then $8.95. Don't mix one plan's price with the other's features.
The DirectAdmin plans list Sydney, Melbourne or Auckland. It's shared hosting. Plan site maintenance separately. Check the checkout total too, because the page's headline and title prices disagree.
Calculate the first bill and two year cost
"Per month" is often a monthly equivalent of a year or more paid upfront. A first invoice discount isn't always a first year discount either. Record these for every option:
the exact plan and currency
the GST treatment
what the first invoice covers and costs
the renewal rate and term
the date you checked
Then run a simple formula. Two year cost is the first term charge plus the remaining months at the renewal rate. Add any required extras. Cash needed now is the first invoice plus any setup or migration fee.
Here's how the displayed offers play out over 24 months at current prices:
Example | First 12 months | Next 12 months | 24 month total |
|---|---|---|---|
VentraIP Entry, yearly | $66.00 | $132.00 | $198.00 inc GST |
SiteGround StartUp | $59.88 | $323.88 | $383.76 ex GST |
SiteGround StartUp with GST | $65.87 | $356.27 | $422.14 inc GST |
DreamIT DirectAdmin Startup | $41.64 | $83.40 | $125.04 inc GST |
Year two uses each plan's current standard or renewal rate, with no other promotion or price change. VentraIP's GST basis comes from its terms. We added 10% GST to SiteGround's figures, rounded per yearly invoice.
These totals leave out extras such as domains, mailboxes and migration. Care and paid plugins aren't in them either. They compare billing patterns, not service quality.
Don't read the lowest total as the best host. DreamIT's figures multiply rounded monthly rates. Check the real checkout total before you rely on it.
Watch the first invoice trap
The first invoice is where people get caught. Take VentraIP Entry on monthly billing. The $5.50 rate covers month one only. Months 2 to 12 cost $11 each, for $126.50 in year one. Over 24 months that's $258.50, against $198 on a yearly first invoice.
Assume $5.50 applies to every month of the first year
Check the invoice term. Monthly billing gives $5.50 once, then $11 a month
Yearly billing costs more today: $66 upfront against $5.50. So more money sits in the prepayment. VentraIP's business page offers a full refund within 45 days. After that, unused prepaid time comes back as account credit. Digital Pacific says its hosting can't be refunded after 30 days.
Before prepaying a long term, ask whether unused months are refunded, credited or transferable.
See the renewal step
The second year costs $264 more than the first. That's a current price scenario. Prices can change.
Count tax, currency and extras
If you're registered for GST, you can usually claim the GST on business hosting. The ATO's GST credit rules need a tax invoice for purchases over $82.50. Overseas suppliers shouldn't charge you GST if you give your ABN and confirm registration. Ask your accountant how this applies to you.
Keep US dollar plans in their own column. US$11 isn't A$11. Convert at a dated rate and allow for card or exchange fees.
Only the hosting line is a checked price. The mailbox, domain and migration figures are teaching assumptions. Drop any line already included. Our guide to website costs puts hosting inside the full budget. The website cost estimator gives a planning range, not a quote.
Understand what hosting can change about speed
Time to First Byte (TTFB) is the wait from starting a page load to its first byte arriving. Google's TTFB guide counts redirects, DNS, the connection and the server's work. It suggests 0.8 seconds or less as a rough guide. TTFB isn't a Core Web Vital. A slow result doesn't prove the host is overloaded either.
What you see | Possible cause | Next evidence |
|---|---|---|
Slow first response everywhere | Redirects, distance or server work | Timing breakdown and cache status |
Fast response, late content | Images, scripts, fonts or layout | Load timeline and largest element |
Cached pages fine, checkout slow | Uncached database or app work | A safe test of the real journey |
Errors in busy periods | Capacity limits or app faults | Timestamped errors and usage |
Good lab test, poor real results | Different test conditions | Real user data and repeat tests |
Hosting affects how soon content can arrive. On its own, it can't fix heavy images, scripts or layout shifts. The field Core Web Vitals are what Google's ranking systems use. Our Core Web Vitals guide explains them and their limits.
One PageSpeed Insights result isn't a hosting certificate. If it shows no field data, that isn't a pass either.
A common mistake is buying a bigger plan before anyone reads the timing breakdown. Our guide to why a website is slow walks through the diagnosis.
What hosting can't buy you
Hosting doesn't set your Google Ads costs. Quality Score is a diagnostic rating for Search keywords, not an input in the ad auction. Our Quality Score guide explains what it measures. Better hosting can fix a measured delivery problem. It can't promise cheaper clicks or better enquiries.
Search works the same way. Google says server errors and 429 responses slow crawling. If they persist, indexed pages can eventually drop out. That's a solid reason to fix recurring faults. A pricier plan is still no ranking promise.
Choose a location for your actual visitors
Three location questions often get mixed up:
where your site's main server, the origin, runs
where a cached copy reaches the visitor
where customer information is stored or accessed
An Australian origin can cut network travel for Australian visitors. But it's not the only factor. Routing, load, caching and the application shape the result too.
A Sydney server won't always beat an offshore setup. A Melbourne business doesn't need a Melbourne data centre. Ignore distance rules like "within 50 kilometres of your office". So choose for where your customers actually are, interstate and overseas included.
A content delivery network (CDN) keeps copies closer to visitors. With the right rules, it can serve whole pages as well as images and scripts. Cloudflare, for example, doesn't cache HTML by default. A cache rule can change that. On a cache miss, the request still goes back to your server.
Don't cache everything just to win a test. Logged in pages, carts and live prices need careful rules. A fast cached page also says nothing about checkout speed. So test both paths.
Production location isn't the whole data story either. SiteGround's 24 June 2024 server page says Sydney sites are backed up in Singapore. Confirm the backup location for the plan you choose. We come back to it under data handling.
Read or commission a fair performance test
We haven't run hosting speed tests for this guide. So there's no fastest host chart here. If someone shows you one, ask how it was run. A fair test holds these steady:
Control | What to record or hold steady |
|---|---|
Site and workload | An approved test copy with the same content and plugins |
Plan and region | The exact service, region, resources, date and price |
Delivery setup | CDN, origin cache, cache headers, hit or miss |
Visitor conditions | Australian test locations, device, browser, connection |
Repeats and timing | Several runs in more than one time window |
Results and limits | Median, spread, failed runs and what it can't prove |
A workable protocol uses at least five first view and five repeat view runs. Do that for each setup and location, in two agreed time windows. That's ten page loads per window, because each repeat view is its own load. First and repeat views describe the browser's state. They don't show whether the CDN had a cached copy, so record that separately.
If you serve eastern and western Australia, test from locations that represent both. Say which locations you couldn't test. Compare an Australian and an offshore origin on equal terms. Never compare a blank demo on one host with a busy store on another.
Don't load test a live revenue site without an agreed scope and a safe environment. A short page load study can't prove uptime, support quality or campaign spike performance.
Purpose: [origin comparison or customer experience]
Site and version: [same page and application]
Plan and region: [exact configuration]
Client conditions: [location, device and connection]
Cache and CDN: [first view, repeat view and cache state]
Runs and times: [repeat count and test windows]
Results: [median, spread and failed runs]
Evidence: [saved reports and limitations]
Check resources, support and service promises
Translate each capacity term into the question it answers:
Storage and file count (inodes): how much the account can hold
CPU, memory, disk activity (I/O) and processes: how much work it can do at once
Bandwidth and transfer: how much it can deliver, and at what charge
Providers measure CPU differently. Their percentages don't compare across hosts. "Unlimited visits" isn't unlimited uncached work at the same moment.
Check your application's real needs too, from its software version and database to scheduled jobs. A WordPress plan won't automatically suit a custom app, such as one built with Node.js. Ask how you'd scale up. Then ask whether scaling back down needs a move.
Name who does each job
"Managed" isn't a complete promise. Each of these jobs needs a named owner, in writing:
Task | Question to settle in writing |
|---|---|
Server and operating system | Who monitors, patches and repairs it? |
CMS, themes and plugins | Who tests updates and keeps licences paid? |
Backups and restores | Who checks jobs, restores and reconciles records? |
Malware and security incidents | Is scanning included? Who cleans up? |
Forms, payments and integrations | Who fixes an app fault when the server is up? |
After hours incidents | Which channel reaches a person? Who approves changes? |
Bottom line Buy the responsibilities you actually need
Support has three separate measures: when it's available, how fast someone responds and how long a fix takes. A 24/7 chat promise doesn't mean every problem gets solved straight away. Ask what's covered, what's escalated and what costs extra.
Local support can help. Location alone doesn't prove competence. Outsourced support isn't automatically poor either.
Hosting and maintenance can be priced separately. Our guide to website maintenance costs covers the care side.
Read the uptime promise
An uptime service level agreement (SLA) is a contract about a defined service. Read what it measures and what it excludes. Then check the claim deadline and the remedy.
Digital Pacific's SLA, as we read it in October 2026, is a useful example. It promises 99.9% network uptime on shared hosting, paid as account credits. Claims must arrive within 30 days. It aims to replace failed hardware within two hours. That window excludes restoring data.
The SLA also rules out liability for lost business. So the hardware clock isn't a promise that your checkout works again within two hours.
Those figures are maths. They don't predict outages, promise recovery or set an allowed data loss. Use an independent monitor on key public pages. Then test the essential customer functions separately. A healthy status page doesn't prove your form or payment path works.
Check whether you can recover the business
Backups only matter if you can restore a working business. Ask which of these each backup covers:
files and databases
uploaded media and configuration
email
connected services
A WordPress site needs both its files and its database to recover. An export of a few posts isn't the same thing. Then ask how often backups run, how long they're kept and where they're stored.
Put your recovery goals in plain words first. How many hours of orders or enquiries can you afford to lose? How long can the essential service be down? A common mistake is trusting a daily backup on a store that takes orders all day.
Ask what happens if the hosting account is locked, compromised or deleted. Keep recovery access and an independent copy where the contract allows. On a hosted platform, confirm what you can export or restore. Don't assume a file and database backup exists there.
Test the restore
Test a restore in an isolated copy. Record what came back, how long it took and anything missing. Don't send real order emails or take live payments during the test. A support ticket or restore fee doesn't make a backup fake. It does affect whether the service suits you.
Restoring an older database can overwrite orders or bookings made since that snapshot. Preserve and reconcile current records first. Our guide to backing up your website covers the full process.
Essential function: [enquiry, booking or sale]
Acceptable interruption: [business requirement]
Acceptable record loss: [business requirement]
Backup contents and location: [verified scope]
Recovery owner and access: [roles, not credentials]
Restore test: [isolated test date and result]
New record protection: [preservation and reconciliation]
Missing dependency: [issue and action]
Keep security practical
The ACSC's small business guide covers the basics. Turn on multi factor authentication (MFA), starting with your most important accounts. Give each person only the access they need. Keep software updated and back up regularly. Then decide who handles alerts, cleanup and recovery.
An SSL certificate protects the connection. It doesn't prove the business is trustworthy or remove malware. Our guide explains SSL certificates in more detail. A firewall, scan or backup each does one job. None of them prevents every breach.
Separate email from website hosting
Email covers three different services. A mailbox receives and stores normal business email. Forwarding passes incoming messages to another address. A transactional service sends website messages, such as enquiry alerts.
A free forwarding address isn't a full mailbox. It may not let you reply from your own domain. Some shared plans include mailboxes. Shopify doesn't provide email hosting, though you can connect a provider. Before calling email included, check storage and sending limits.
Separate email hosting can make a host change easier. It isn't mandatory for every small site. Domain expiry, DNS changes or a lost login can still hit both services. So record who controls each one.
When nameservers change, keep the mail routing and authentication records your provider specifies. A common mistake is switching nameservers and forgetting those records. Test inbound and outbound mail separately. Then send a real enquiry through the website. A success screen doesn't prove the right person got it.
Map where customer data is handled
The Privacy Act generally doesn't cover a small business with annual turnover of $3 million or less. Some are covered regardless, including health service providers and businesses trading in personal information. The OAIC's checklist helps you check. Our guide to Australian privacy law changes for websites explains which businesses are covered.
An Australian server doesn't settle compliance on its own. Personal information can travel well beyond the web server:
Ask each supplier where data goes and who can reach it. Then ask about retention and deletion. Australian ownership, an Australian server and Australian only processing are three different claims.
Where the Australian Privacy Principles apply, APP 8 covers sending personal information overseas. It generally requires reasonable steps so the overseas recipient doesn't breach the APPs. A tightly controlled cloud arrangement can count as a use, not a disclosure. That depends on the contract and your effective control. So don't label every overseas backup or support session automatically.
Remember SiteGround's Singapore backups for Sydney sites. They show why the location question has more than one answer. They say nothing about compliance either way. Nor does a broad compliance badge replace your own requirements.
For health, legal or other sensitive information, check sector and contract rules with an adviser first. Ask suppliers for their data processing terms and an incident contact. Don't collect sensitive details in a plain enquiry form without a process to handle them.
Protect ownership and a practical exit
Record who controls every account the site depends on. Use business owned recovery emails, named users and MFA. Don't rely on a former employee's personal email or one agency login.
Agency or reseller hosting can work fine. You don't need the provider's master server account. You do need documented rights and real access to your own site and data. You also need a workable transfer route. Ask for the export and handover steps in writing, with any fees.
Check what can actually move. A self hosted site needs its files and data. It also needs a compatible runtime and any licences. Webflow's code export leaves out CMS content and Ecommerce. Forms and password protection stop working too.
A Shopify store isn't a generic site you can copy to cheap shared hosting. Our guide to transferring a website to a new developer covers the handover.
Domain and DNS: [business owner and recovery route]
Hosting or platform: [account rights and billing owner]
Site and data export: [method and limitations]
Licences and integrations: [transfer requirements]
Renewal alerts: [date and named recipients]
Handover scope: [files, data, access and documentation]
Cancellation and deletion: [notice, timing and terms]
Verification owner: [person accepting the transfer]
Record renewal dates, payment owners and alert recipients. Don't assume auto renew works after a card expires. Agree the cancellation notice, refund basis and backup retention. Then confirm the new service works before you cancel the old one.
Treat these as questions to resolve before you sign:
unclear renewal terms
capacity limits nobody explains
a restore route nobody has tested
no support for your application
weak recovery access to the account
unsupported software versions
an export the provider can't explain
Match the plan to the business
Start from your situation, then let the evidence decide:
Situation | Starting point | Evidence that decides |
|---|---|---|
Small brochure site | Quality shared or your platform | Full cost and clear recovery |
Tradie or local service | Shared or managed WordPress | Mobile and enquiry delivery tests |
WordPress lead site | Enough capacity, named upkeep | Resource use and plugin support |
Paid campaign landing pages | Your current plan may be enough | Customer paths under real demand |
WooCommerce or bookings | Proven dynamic capacity | Uncached journeys and payments |
Large site or custom app | Requirements led specialist host | Runtime, load and an operator |
A cheaper plan is fine when it meets the requirements. A costly plan can still fail if nobody maintains the application. An enquiry's value helps set priorities. It doesn't prove an extra $20 of hosting wins an extra customer.
Treat critical requirements as pass, fail or unresolved before you compare extras:
Score features and pick the highest total
Drop any plan that fails a critical requirement, then compare cost
Critical requirements include application compatibility, an acceptable data arrangement and safe recovery. Clear account rights count too. So does someone able to run the service. A lower price can't make up for a missing one.
Stay with your current host when it meets them and the evidence shows no hosting problem. Fix the page or the integration if that's the real issue. Upgrade or move only when a requirement can't be met at a fair total cost. Then check that the change solved it.
If you're unsure where the problem sits, our DIY website audit checks the wider site first. If WordPress itself is the question, our guide on whether WordPress is still worth it covers it.
Move hosts with an agreed acceptance check
A hosting move can be short if you sequence it and check each stage:
If the public URLs stay the same, you don't need new redirects. Change of Address doesn't apply either. Google's guide to hosting moves covers testing, DNS timing and monitoring. If URLs or structure change too, use our migration checklist.
A free transfer offer may not cover email or every integration. Old redirects and search checks can fall outside it too. Ask what it includes.
Keep the old service until validation and data reconciliation are done. Be wary of zero downtime promises. TTL is how long other networks may keep your old DNS answer. Lowering it at the last minute won't clear answers they've already cached. Google suggests lowering it at least a week ahead.
Our free audit is a short, prioritised read on what to fix first.
What we recommend at Elev8d
Pick the smallest service that meets your real requirements. Compare the full two year bill, including the renewal. Then name who maintains the site and who restores it. If your current host passes those checks, stay put.
On our builds, the domain, hosting and site are in your name from day one. We set clients up on hosting matched to each site's needs, usually in Sydney. Hosting, domain and maintenance costs sit outside the build price. You can take a care plan or look after it yourself.
Don't get taken for a ride by a low headline price or a vague "fully managed" label. Ask what it actually covers.
Frequently asked questions
What is the best web hosting for a small Australian business?
The one that meets your site, support, recovery and cost needs. There's no universal winner. Use the dated shortlist above as a starting point, then test the fit.
How much should I pay for hosting?
Work it out from named plans and the renewal bill. Our 24 month examples run from $125.04 to $422.14 including GST. Hosting is only part of a website's running cost.
Is shared hosting enough?
Often, yes. It suits a modest site whose workload fits. Check the real resource limits and recovery terms. A site's revenue doesn't decide the server model on its own.
Do I need a Melbourne server?
No. There's no postcode rule. Test delivery to your actual audience, including interstate and overseas visitors.
Does Google offer web hosting?
Yes, in two different forms. Google Cloud sells hosting infrastructure for applications. Google Sites is a builder for team and project sites. Neither is a Business Profile feature or business email.
Does Shopify or Webflow include hosting?
A Shopify store includes hosting. A Webflow site on a custom domain needs a suitable Site plan. A Workspace plan alone doesn't cover every site's hosting.
Does hosting include email?
Sometimes. It depends on the plan. Treat mailboxes, forwarding and website messages as separate services. Shopify stores need a third party for mailboxes.
Will better hosting improve SEO or Google Ads results?
It can fix a measured delivery problem. It can't promise rankings, cheaper clicks or better customers.
Are Australian servers automatically privacy compliant?
No. Start with your actual obligations. Then check where the data goes, who can reach it and what the contracts say.
Can my web designer manage hosting?
Yes, with documented responsibilities and your business controlling its own accounts. Keep recovery access and an agreed exit route.
Next steps
Get a complete quote
Use the quote template above for every shortlisted plan. Compare the same currency, tax basis and term.
Diagnose before you upgrade
Read the timing breakdown first. Fix page or integration problems where the evidence points.
Test the recovery route
Run an isolated restore and record the result. Name who restores the site and reconciles new records.
Arrange a scoped review
For implementation help, see our web design service. It sets up hosting in your name.
