Web hosting. Know the full cost.

Compare plans for your website, store or client portfolio. See the full first-term price, calculate renewals and explore how your site reaches visitors worldwide.

Compare hosting plans ↗Find my plan →

Product preview · Example prices in USD

View prices and renewal terms → Check what a plan includes → Explore global request paths →

HOSTING PLANS

Compare hosting plans.

Change the billing term to see the initial payment for each plan and its monthly equivalent. Renewal rates appear alongside each price.

Billing term

Sample USD pricing and features. Initial payments and renewals exclude taxes and add-ons.

View full feature comparison

LAUNCH EXTRAS

Hosting offers and add-ons.

Compare four example offers. Check which plan and term qualify, what is included and what you would pay separately.

ANNUAL TERMSFirst-year domain credit

Example bundle for new registrations on Growth and Scale with a 12- or 36-month term. Premium names, transfers and renewals are excluded.

LONGER TERMSLower monthly equivalent

Compare the sample 36-month rate with 12-month pricing. For sample Growth, 36 months costs $179.64 upfront at $4.99/mo. The 12-month option costs $77.88 today and $437.64 over 36 months at the sample renewal rate. The longer term lowers the three-year cost by $258.00 and requires $101.76 more upfront.

SWITCHING HOSTSOne-site migration bundle

Example add-on for an eligible WordPress site on Growth or Scale. Email, custom apps and domain transfers need their own migration plan.

TEAMS & AGENCIESLaunch review bundle

Example Scale add-on covering DNS, mobile checks and a rollback checklist before a client handoff.

Illustrative offers. Availability and eligibility require confirmation.

Compare sample plans ↗

PLAN FINDER

Find the plan that fits.

Answer three questions to get a plan recommendation and an explanation of why it fits.

GLOBAL HOSTING PLANNER

See how a request reaches your site.

Choose a visitor market to explore an example request path. Use it to decide what to test before selecting a hosting region.

Visitor market

Americas Europe Asia–Pacific

Request type

Origin fetch Cache hit

VISITOR MARKETAmericas

CDN EDGECacheable assets

EXAMPLE ORIGINUS East

Origin fetch · A dynamic request or cache miss goes from the CDN edge to the hosting origin.

Planning illustration · Regions and routes are examples.

A shared workspace with long tables and large windows

BEFORE YOU SIGN UP

Check what your team can actually do.

Ask for a walkthrough of the control panel

Find the controls for DNS, SSL certificates, staging, backups and team permissions. Verify which actions you can perform yourself and when you’ll need support.

Ask for a restore demonstration

Check whether you can restore one site to staging. Confirm how long backups are retained and how the restore handles files or orders created after the backup.

Ask for the terms in writing

Verify hosting regions, support coverage, migration scope, refund exclusions and renewal costs against the provider’s published terms before placing an order.

Read the buying guide →Review common questions →

WORKED EXAMPLE / STORE MIGRATION

How to migrate a live store.

Follow a fictional WooCommerce store as it chooses a plan, tests a copy of its site and switches traffic. The figures below use the sample Growth plan.

People making a purchase at a shop counter — Illustrative scenario · Independent retailer with one online store

The brief

A retailer sells to customers in the UK and continental Europe. Its store shares a domain with business email, and orders still arrive while the team prepares the move. The owner wants daily backups and needs to know the cost after the first term.

The hosting decision

Growth is the sample fit because daily backups and a CDN are included. Before committing, the team would verify PHP and database compatibility, storage headroom, backup retention, support for WooCommerce and whether the provider can restore a single site.

12 months upfront: $77.88
Next 12 months at renewal: $179.88
24-month total: $257.76

Sample USD hosting costs before tax, domain renewal, email or paid plugins.

Load this example in the estimator →

Prepare a copy

Export the files and database and save DNS records. Restore the copy to staging. Keep it out of search results and use payment sandbox credentials so tests cannot create real orders or charge cards.

Rehearse a purchase

On mobile and desktop, test a product page, cart, shipping calculation, payment confirmation and order email. Check redirects and preserve the domain’s existing mail records if email is staying with its current provider.

Switch and monitor

Schedule a low-traffic window. Agree on how to handle new orders while making the final data sync. After switching traffic, verify HTTPS, checkout and mail, then reconcile orders on both systems before retiring the old host.

When would the store pause or roll back?

Agree on triggers before the move, such as failed payments, missing orders or a checkout outage. Keep the old environment available. If new orders reached the new host, record and reconcile them before sending customers back to the previous system.

HOSTING BUYER’S GUIDE

What to check before choosing a host.

Use these checks to compare real hosting quotes. The answers can change the cost and the work your team needs to do after launch.

Match the plan to the workload

Starter fits a single, relatively simple site that can work with weekly backups. Growth fits projects that need daily backups or several sites. Scale is worth comparing when you need on-demand backups before releases or are managing many client sites.

Ask the provider how it handles traffic bursts, CPU or memory limits, and staging environments. Website and storage allowances tell only part of the story.

Price the whole commitment

Add the hosting bill, renewal, domain, mailboxes, tax and paid add-ons. Find out whether the quoted rate requires prepayment and whether the renewal uses a different billing term.

Ask the provider what a refund covers and what happens to your domain, email and site data if you leave.

Check that you can recover

Ask how often backups run, how long they’re kept and what you can restore. For a store, work out how many orders you could lose if you had to restore yesterday’s database.

Ask the provider whether you can restore to staging and download an independent copy of the files and database.

Know who handles incidents

Find out which support channels operate in your time zone and language. Confirm who helps with hosting outages, compromised sites and third-party plugins.

Ask the provider what support and availability commitments appear in the contract and how to escalate an outage.

HOSTING PLAYBOOK

Plan your launch around the work your site does.

Choose a deployment scenario and work through its technical checks. Use these examples to compare a provider’s documented capabilities with what your project needs.

WordPress → Ecommerce → Agencies → Custom apps → Performance budget → Troubleshooting →

Publish and maintain a WordPress site

Before choosing a host. Verify the supported PHP and database versions, access to files and database exports, and whether the plan has a staging environment. Work out how often the site changes so you can choose an appropriate backup schedule.

Before an update. Back up the database and site files. Rehearse changes to WordPress, themes and plugins on staging. Check navigation, forms and the editor before rolling the update into production.

After launch. Choose an owner for updates and a schedule for restore drills. Check media uploads, contact form delivery and redirects after each major release.

WordPress upgrade guide ↗

Prepare a store for a promotion

Before choosing a host. Ask how the plan handles sudden increases in concurrent requests and what happens when resource limits are reached. Include checkout, search and account pages in your test plan because their workload differs from browsing a product image.

Before the campaign. Rehearse a mobile order in the payment provider’s test mode. Include coupons, shipping, confirmation email and refunds. Agree on who handles urgent hosting, payment and fulfilment issues during the sale.

During the campaign. Watch checkout completion, errors and order emails. Record the time and affected flow when something fails so your team can trace the problem.

Host multiple client sites

Before choosing a host. Ask how sites, credentials, backups and billing are organised. Confirm whether you can grant a client access to their own site and export or restore that site independently.

Before handoff. Agree who owns the domain, hosting subscription and third-party accounts. Set the approval process for releases and document DNS, renewal dates, deployment steps and recovery instructions.

During maintenance. Schedule work by client, keep a record of updates and test one representative site before rolling shared changes across the portfolio.

Deploy a custom web app

Before choosing a host. Verify the required runtime, build command, database connections and any background job support. Ask about logs, environment settings, persistent storage and how to roll back a deployment.

Before production. Use separate test credentials and data. Confirm that startup, sign-in, health checks and error reporting work after a fresh deployment. Plan database changes and decide how to recover if a release fails halfway through.

After release. Record the deployed version. Verify key flows from outside your own network, check logs for errors and keep the last known working release accessible.

PERFORMANCE LAB

Set a page weight budget.

Enter a transfer-size target and the resources your page loads. Start with a representative page, such as your homepage or a product listing. Then compare it with a page that uses more scripts, fonts or photos.

Measure consistently. Use the Network panel’s transferred sizes after a fresh load. Record the page, device and network settings you tested.

Fix the largest category first. Resize images to their rendered size, review third-party scripts and remove unused font variants. Measure the same page again after each change.

Check the user experience too. Page weight helps identify expensive assets. Test real tasks such as opening the menu, searching a catalog and checking out to see how the page behaves.

Performance budget guide ↗

POST-LAUNCH TROUBLESHOOTING

Find the first thing to check.

Start with the symptom your visitors see. Record when it began, which pages are affected and what changed shortly before the issue appeared.

Back to deployment scenarios ↑

The site works in some regions only

Compare DNS resolution and HTTPS from an affected region and one that works. Note the exact browser error and hostname. If this followed a DNS change, verify the intended records and certificate coverage before making further changes.

Images load slowly on mobile

Inspect transferred image sizes and the image selected by the browser. Compare the downloaded dimensions with the rendered dimensions. Check caching and repeat the same page test after replacing the largest file.

Checkout fails while the rest of the site works

Identify the failing step, such as shipping, payment or confirmation. Record the timestamp, test order reference and browser error. Check application and payment logs while keeping customer details out of screenshots and support notes.

Contact forms submit but messages never arrive

Confirm the form shows a success state and check whether it recorded the submission. Review delivery logs, sender settings and spam folders. Test the form using an address you can monitor.

The site shows old content after a release

Check whether the new version reached the origin. Then compare cached and uncached requests. Review browser and CDN cache settings and refresh only the affected assets if the provider supports targeted invalidation.

The site started failing after an update

Record the version change, error and affected pages. Compare production with staging and check relevant logs. Before rolling back, confirm how the rollback would affect new orders, submissions or edits.

GLOBAL LAUNCH GUIDE

Make the site work where your customers are.

Start with the countries you can support well. Work through these checks before expanding to the next market.

Colleagues working together around a table

Choose a hosting region and test real user flows

List the countries where your audience lives and choose an origin region to test. A CDN can help with cacheable assets such as product photography. Check search, account pages and checkout separately because they often depend on requests to the origin server.

Localize the path to purchase

Review currency labels, shipping zones, addresses, phone fields and payment methods. Translate the cart, order emails, returns policy and help pages. When customers switch language, keep them on the same product when a translated version exists.

Test accessibility and low-bandwidth browsing

Check keyboard navigation, text zoom, clear error messages and photo descriptions. Test on a mid-range phone with a slower connection. Verify that menus, images and forms stay usable and that checkout remains understandable when a request fails.

Plan for privacy and customer support

Document which services handle account, analytics and payment data. Check whether your markets or customer contracts have data location requirements. Publish support hours with time zones and confirm which languages your team can cover.

Watch the first week by market

Compare page load times, form errors and checkout completion by region and device. Review common support questions alongside those metrics. Start by fixing steps where customers repeatedly get stuck.

Open the global launch checklist →

FIELD GUIDES

Your first week online.

Choose a project to get a step-by-step checklist. Your progress is saved on this device.

DOMAIN WORKSHOP

Find a name
worth keeping.

Enter a brand or project name for short domain ideas. Open any result to check the registration details with ICANN.

COMMON QUESTIONS

Frequently asked questions.

What to check when comparing hosting terms and planning your move.

What am I paying upfront?

Multiply the advertised monthly equivalent by the number of months in your initial term. The calculator shows this amount separately from the next 12 months of hosting.

What changes at renewal?

Introductory rates typically end after the first term. Check the next billing amount, renewal date and any separate renewal prices for your domain, email or add-ons.

Can I move a site without interrupting email?

Copy and test the site first. Save your DNS records, especially MX, SPF, DKIM and DMARC. During the website cutover, preserve your existing mail records unless you are also moving email.

How do I choose a region?

Start with the region closest to most of your visitors. Check any data residency requirements, then use a CDN for cacheable assets. Test performance from at least two representative markets.

How can I verify a first-year domain offer?

Check which extensions qualify, whether the offer covers a new registration or transfer, and the second-year price. Confirm the domain is registered under an account you control.

Does hosting include email migration?

Website and mailbox migrations are often separate. Inventory mailboxes, aliases and shared addresses, then ask who moves old messages and updates mail records.

What should I test in staging?

Start with actions that affect revenue or support. Test checkout, form delivery, sign-in, redirects and password reset. Confirm the test environment cannot send production messages or take real payments.

What is the difference between a backup and a restore?

A backup is a copy of data. A restore puts that copy back into a working environment. Verify how long a restore takes, whether it overwrites newer records and whether it can run in staging.

Will a CDN make every page faster?

It can help with files and pages that are safe to cache. Cart, checkout and logged-in pages often still depend on the origin. Measure them separately.

When should I move up a tier?

Upgrade when a specific limit or requirement is blocking the work, such as site count, backup frequency or restore options. If pages are slow, check image sizes, caching and server timings first.

Can I purchase a plan here?

This is a planning preview. You can compare examples, save a plan summary and make a launch checklist. Billing and live provisioning require a provider connection.