WooCommerce Hosting: Why the Expensive Hosts Aren't the Fast Ones

You'd expect the expensive hosts to be the fast ones. In Google's own speed data for August 2026, 21.3% of Kinsta's sites and 9.7% of Flywheel's gave phone visitors a good server response, while on Hostinger's far cheaper shared plans 30.4% did.

Across all WooCommerce sites the figure was 12.7%. So what are you paying for when you buy WooCommerce hosting? Mostly two things: ready-made copies of your pages, so shoppers get them at once, and enough computing power for the pages that can't be copied, such as the cart and the checkout. Distance to your shoppers comes third, and price on its own fixes none of them.

If you're choosing hosting for a WooCommerce store for the first time, this is for you. You'll get Google's speed data for a dozen popular hosts, prices I checked on October 5, 2026, and a step-by-step way to choose. No host paid to be in it. I recommend one provider by name, Hetzner, because I've used it for more than 15 years, and it has no affiliate program, so I earn nothing if you pick it.

What you're paying for: a cache, cores and distance

Hosting is the computer that runs your store around the clock, called a server, sitting in a data center. WooCommerce is software, so every time a shopper opens a page, that computer has to build the page from your products, prices and settings before it can send it.

I measured how long that takes on a test store with 600 products, and three things decided the result.

A page cache

A page cache keeps ready-made copies of your pages. On my test store a product page took about 100 milliseconds to build and about 1 millisecond to send from the cache, so a copy goes out roughly a hundred times faster. Every good host has a page cache; make sure yours isn't switched off.

Enough CPU cores

A CPU core (often written vCPU) is one unit of computing power, and each core builds one page at a time. That's what counts for the pages a cache can't serve, because the cart, the checkout and the account pages are built fresh for every shopper. One core built about 10 of those pages a second; four cores built about 39.

A short distance to your shoppers

Each new visitor's phone has to exchange several messages with the server before the page starts to arrive, and every one of those exchanges travels the full distance. On October 5, 2026 I tested a Hetzner server in Helsinki, and this is how long a single round trip took:

From a server in Helsinki to	One round trip
Amsterdam	28 ms
London	38 ms
New York	100 ms
Los Angeles	166 ms
Singapore	179 ms
Sao Paulo	225 ms

It's the same server, three to six times further away in time from an American shopper than from a European one.

That's the plain case for a data center near your shoppers, or for a CDN (content delivery network) in front of the server: a network of servers around the world, such as Cloudflare, that keeps copies of your images and pages close to the people who open them.

A current version of PHP, the programming language WordPress is written in, helps too, so ask your host for PHP 8.3 or newer when you compare plans. If you'd like the technical detail behind all of these numbers, the full test, layer by layer has it.

The four kinds of hosting

Hosting comes in four kinds, and they differ mostly in who does the technical work. Read the second column first. If nobody on your team wants to run a server, keep it updated and fix it when something breaks, that column answers most of the question.

Kind	Who does the technical work	Good for	Watch out for
Shared hosting	The host. You share one server with many other sites.	A brand new store with few visitors	Slowdowns when your neighbors get busy, and limits on how much the server works for you
Managed WordPress hosting	The host: caching, updates, backups	Owners who want no technical work at all	Prices that rise with your monthly visits, and plans that sell "PHP workers" without saying how many cores stand behind them
Managed cloud	A service such as Cloudways sets up a cloud server for you	Owners who want their own server without running it	Default settings nobody reviews
Cloud server (VPS)	You or your developer, or a server panel	The best price for the power; stores with a developer	You start with an empty server and keep it updated

Shared hosting is often fine for a brand new store, as long as the plan includes a page cache and a current PHP version. It stops being enough once a campaign brings many shoppers to the cart and checkout at the same moment, because a shared server limits how much it works for each site.

Between the other two, managed hosting spares you the work and a cloud server gives you more power for the money. I'd choose the cloud server if you, a developer or a server panel will look after it, and managed hosting if nobody will.

Google's speed data for a dozen popular hosts

The HTTP Archive records which host each website uses, and Google's Chrome browser reports how fast those sites really were for visitors. Put together, they grade each host. A host's row counts every site on that host, whatever software it runs and wherever its visitors are, so read it as a picture of the host's customers as much as of its servers.

Host	Kind	Sites	Answer phones fast enough
WooCommerce, all sites	Reference	557,369	12.7%
WordPress, all sites	Reference	2,752,367	23.5%
Hetzner	Cloud server	12,196	61.0%
Google Cloud	Cloud server	266,054	61.1%
Amazon Web Services	Cloud server	1,151,193	50.2%
WordPress.com	Managed WordPress	56,934	51.7%
Pantheon	Managed WordPress	14,376	48.6%
Cloudways	Managed cloud	18,658	31.8%
WP Engine	Managed WordPress	83,985	31.2%
Hostinger	Shared	349,478	30.4%
SiteGround	Shared	112,334	21.6%
Bluehost	Shared	36,414	21.6%
Kinsta	Managed WordPress	31,012	21.3%
Flywheel	Managed WordPress	10,580	9.7%

Share of each host's sites with a good server response, 800 milliseconds or less, for phone visitors in August 2026, from the HTTP Archive Technology Report with Chrome UX Report data. Hostinger also sells a website builder, and its row includes those sites.

Price clearly doesn't sort this list: two of the dearer managed hosts sit below WordPress as a whole. The WordPress hosts at the top, WordPress.com and Pantheon, have one thing in common instead. Both hand out ready-made copies of pages from close to the visitor. The cloud rows (Hetzner's included) mix every kind of website, so they say as much about who builds there as about WordPress on them.

My recommendation: Hetzner, with Cloudflare in front

Hetzner is a German hosting company, and I've rented servers there for more than 15 years, mostly because they've stayed up. It runs data centers in Nuremberg and Falkenstein in Germany, Helsinki in Finland, Singapore, and Hillsboro and Ashburn in the United States.

Every cloud server in Germany or Finland includes 20 TB of traffic a month, more than most stores will ever use, while servers in the United States include 1 TB and in Singapore 0.5 TB.

Hetzner plan, Regular Performance	CPU cores	Memory	Disk	Price a month
CPX12	1	2 GB	40 GB	EUR 11.49
CPX22	2	4 GB	80 GB	EUR 19.49
CPX32	4	8 GB	160 GB	EUR 35.49
CPX42	8	16 GB	320 GB	EUR 69.49

Hetzner Console, October 5, 2026, prices excluding VAT for a server in Germany or Finland with 20 TB of traffic; a public IPv4 address adds EUR 0.50 a month, and Singapore adds EUR 7.00. Cheaper Cost-Optimized plans showed limited availability.

For a new store, CPX22 with 2 cores is where I'd start, and a store that runs campaigns should start at CPX32 with 4. That's about EUR 20 to 36 a month before VAT, plus whatever you pay for setup and updates. Managed WordPress plans often cost more for the same power, and many add limits on monthly visits.

Traffic is where the big clouds charge most. Amazon Web Services charges $0.09 for every gigabyte sent to visitors in the first 10 TB of a month, and $0.085 after that, once the first 100 gigabytes are used. The 20 TB that come with a European Hetzner server would cost about $1,750 in data transfer alone there.

On the same day I benchmarked a 4-core Hetzner cloud server in Helsinki, a CX33 from the Cost-Optimized line, with YABS, a free test that many server owners run. Its disk read and wrote about 1.1 to 1.2 GB a second in large blocks and handled about 46,000 small operations a second (the kind a database lives on), and its network sent 5.19 Gbit/s to London.

The catch: a Hetzner server is unmanaged

A Hetzner cloud server is unmanaged, which means you get an empty computer, and somebody has to install WordPress on it and keep it updated for as long as the store runs. There are three ways to handle that, from easiest to most hands-on:

1. Hetzner's WordPress app: when you create the server, open the Apps tab and pick WordPress, and the server starts with WordPress already installed.
2. A server panel: CloudPanel is free, while RunCloud and SpinupWP are paid services. Each one installs the web server and WordPress for you and keeps them updated from a dashboard.
3. A developer, for a one-time setup and a small monthly retainer for updates.

If none of the three suits you, you're better off with managed WordPress hosting.

And if most of your shoppers are in the Americas, DigitalOcean and Vultr are the ones I'd look at, with data centers in several US cities and more traffic included than Hetzner's US servers; Cloudways can set up a managed server on either of them.

Put Cloudflare in front of any host

Cloudflare's free plan sits between your shoppers and your server. It hands out copies of your images, styles and scripts from data centers near each shopper, gives you a free SSL certificate for the padlock in the address bar, and blocks floods of fake traffic before they reach your store. Do you need it? Yes, if your shoppers come from more than one country, and the free plan is enough to start. Setting it up is a few minutes of work and then a wait:

1. Create a free account at cloudflare.com and add your store's domain.
2. Change your domain's nameservers, at the company where you bought the domain, to the two Cloudflare gives you.
3. Wait for the email that says your site is active on Cloudflare, usually within a few hours and at most a day.
4. For whole-page copies of a WooCommerce store, add Automatic Platform Optimization (APO) for WordPress: $5 a month on the free plan, included in the paid plans. It keeps whole pages close to your shoppers and skips anyone who's logged in or has something in the cart.

The cart and the checkout still go to your server, which is why the server's location still counts.

Other CDNs, such as Bunny.net or Fastly, do the same job. One thing the free plan doesn't include is automatic switching to a second server when the first one fails, which Cloudflare sells as Load Balancing from $5 a month.

Choosing your hosting, step by step

1. Measure the store you have: run the Store Speed Test on your best-selling product page and write down the server response. That's your number to beat.
2. Decide who does the technical work (you, a developer, a server panel or the host), because that decides between a cloud server and managed hosting.
3. Pick a data center near most of your shoppers: Germany or Finland for Europe, the US east or west coast for the Americas, Singapore for Southeast Asia.
4. Choose the size: 2 CPU cores and 4 GB of memory for a new store, 4 cores and 8 GB once you run campaigns or sell a few hundred orders a month.
5. Check four things before you pay: a page cache, PHP 8.3 or newer, daily backups you can restore yourself, and a staging copy for testing changes.
6. Put Cloudflare in front, free, with APO if you want whole pages cached close to shoppers.
7. Measure again after the move, with the same Store Speed Test on the same page.

While you compare plans, these lines on a price page are the ones I'd question:

• Unlimited everything. The limit is still there, usually on how hard the server will work for you, and it's written in the terms rather than on the price page.
• PHP workers with no core count. Workers are places in a queue, and it's the cores that build the pages, so ask how many cores stand behind your plan.
• Prices by monthly visits. One popular post or a busy sale can push you into extra fees, so ask what an extra 10,000 visits costs.
• An old PHP version. Anything older than 8.2 no longer gets security fixes, and 8.2 stops at the end of 2026.
• No backups you can restore yourself, when one bad plugin update can take your store down.
• A speed promise with no method. "Loads in 0.5 seconds" means nothing without the page, the place and how it was measured.

Pay for cores, a page cache and backups, and skip "unlimited". Then, after the move, put the new server response next to the number you wrote down in step 1. That's the only speed claim about a host I'd trust: your own page, measured twice.

Sources

Speed data, Test store, Hetzner and 3 more6

• Speed data: HTTP Archive Technology Report, August 2026, mobile, with Chrome UX Report results.
• Test store: CartHacker's WooCommerce benchmark, October 2026, the study behind Why your WooCommerce store is slow.
• Hetzner: Cloud server plans, prices from the Hetzner Console on October 5, 2026. Benchmark: Yet-Another-Bench-Script.
• Amazon Web Services: EC2 on-demand pricing, data transfer.
• Cloudflare: Free plan and Automatic Platform Optimization for WordPress.
• PHP: Supported versions. Google, web.dev: Time to First Byte.