WooCommerce is a WordPress plugin, and installing it is no different from installing any other plugin. But once it's on, what the site demands from its hosting moves up a level.
Most people discover this during their first promotion.
30-second overview
| Item | Conclusion |
|---|---|
| What WooCommerce is | A WordPress plugin, but the hosting load moves up a level |
| The critical difference | Cart and checkout pages can't be cached |
| Which spec to look at | CPU and object cache, not storage |
| When to upgrade | When you start paying for traffic |
| First thing to check when it's slow | How many plugins you have, not the hosting spec |
Three structural differences
An ordinary WordPress site — a blog, a brand site, a portfolio — is essentially read-only. Visitors are just looking at things you already wrote. A store is not.
1. The cart and checkout pages can't be cached
This is the critical point. The reason an ordinary WordPress site can hold up under a lot of traffic on cheap hosting is full-page caching: the page is generated once, everyone after that gets the same ready-made HTML, and PHP never has to run.
But a store has three pages that can never work that way — cart, checkout and my account. Their contents differ for every single person and can change from one second to the next. They have to be generated live, every time.
The conclusion is blunt: caching can't save a store's most important pages. Their speed is dictated directly by CPU, and they happen to be the pages closest to a completed sale.
2. The database goes from read-only to constantly writing
A browsing site almost only reads, never writes. In a store, every action is a write: adding to the cart, updating a quantity, creating an order, decrementing stock, recording a session.
WooCommerce also makes heavy use of transients and the wp_options table. As a store runs over time, that table bloats — and it is read on every single page load. This is the real reason behind a lot of stores that "suddenly got slow after six months", and it has nothing to do with visitor numbers.
3. Traffic comes in peaks, not averages
Blog traffic is flat. Store traffic isn't — ads go live, a newsletter goes out, a livestream sells, Double 11 arrives, and traffic spikes within minutes and then dissipates hours later.
Picking hosting on your monthly average traffic fails in exactly those peak minutes. And those minutes are the ones you paid for with ad spend.
So which spec should you look at?
Instinct says storage, because it's the easiest number to understand on a price list. But the real bottleneck for a store is almost never the disk.
| Spec | Importance for a store | Why |
|---|---|---|
| CPU | Highest | Checkout can't be cached, so it's computed live every time |
| Object cache | High | Cuts repeated database queries; the difference is obvious on write-heavy sites |
| Memory | Medium | The more plugins, the hungrier — and WooCommerce itself isn't light |
| Storage | Low | Product images take the bulk of it, but it's rarely the bottleneck |
Both RoamerHost WordPress plans can run WooCommerce and both have 10 GB of storage; on resources, the difference is compute: WordPress Basic at NT$3,588/year (avg. NT$299/mo) (1.5 vCPU / 10 GB) and WP × Roamer AI Pro at NT$11,988/year (avg. NT$999/mo) (2 vCPU / 10 GB). Pro also includes Business-tier Roamer AI access, so site work like building pages, changing layouts, menus, forms and SEO can be handed to the AI just by describing it. For a store we suggest starting on Pro, for the reason in the first row of that table. If your product images outgrow 10 GB, email [email protected] and we will work out more space with you.
But not every store needs better hosting
Let's be honest. If you're in one of the situations below, Basic has enough resources and there's no reason to spend more:
- Few products, single-digit order counts. For a store doing five orders a day, the compute cost of the checkout page is simply not a burden.
- No promotions, no ad spend. No peaks means no reason to pay for peaks.
- You sell digital goods or pre-orders. No live stock decrements means far fewer writes.
The right time for a store to upgrade its hosting is when you start paying for traffic — not when you open the store.
Decision table
| Your situation | Recommendation |
|---|---|
| Just opened, still validating whether anyone buys | Basic is fine; don't invest ahead of demand |
| Running ads or seasonal promotions | Pro — those peak minutes are the expensive ones |
| Hundreds of products or variable products | Pro — variable products are much more expensive to query |
| Store is already running but getting slower | Read the next section first; you may not need a different plan |
When it slows down, check the plugins first
Stores usually run more plugins than ordinary sites — payments, shipping, invoicing, marketing, reviews, memberships. Every one of them executes on every request.
And store plugins have a problem ordinary sites don't: a lot of e-commerce plugins schedule background jobs to sync stock, send reminder emails and run reports. Visitors never see the resources those jobs consume in the background, but it shows up in checkout page speed.
When the site gets slow, disable half the plugins and test before deciding whether to upgrade the plan. The test is free and very often finds the answer outright.
FAQ
Q: Can I install WooCommerce on the Basic plan?
Yes — neither plan restricts installs. Both plans have 10 GB of storage; on resources the difference is compute, and a store with few products and single-digit order counts handles perfectly well on Basic; the other difference is that Pro includes Business-tier Roamer AI access, so changes to the site can be handed to the AI.
Q: Why is the checkout page so resource-hungry?
Because it can't be cached. An ordinary page is generated once and everyone gets the same ready-made HTML, so PHP never runs; but cart, checkout and my account look different for every person and can change every second, so they can only be generated live.
Q: My store got slower over time — should I change hosting?
Check two things first: how many plugins you have, and whether wp_options has bloated. WooCommerce makes heavy use of transients and autoloaded options, and that table is read on every page load. A lot of "suddenly slow after six months" cases have nothing to do with visitor numbers; it's this.
Q: Will the site go down during a promotion?
It depends on peak concurrency and your compute resources. In practice the advice is to upgrade a week before the campaign rather than on peak day — you can upgrade from Basic to Pro with one click in your dashboard at any time, and it takes effect as soon as you pay.
Q: Do I need to install a separate caching plugin?
Full-page caching offers limited benefit to a store (the critical pages can't be cached), but object caching makes a noticeable difference: it removes repeated database queries, and a store issues a lot of queries to begin with. See Redis object cache for details.
Sources and further links
For e-commerce settings and limits, the official documentation is the source of truth:
Further reading
- How long before you notice your site is down: which pages to monitor
- When to upgrade your WordPress plan: Basic vs. Pro
- The limits of fully managed WordPress: what you can't do
- Self-hosted vs. managed WordPress: the cost table that counts maintenance time
- WordPress Redis object cache: two invisible optimizations you can feel
- Why OpenLiteSpeed: choosing the engine behind WordPress hosting
- RoamerHost managed WordPress plans
Want someone to build it for you?
When requirements go beyond what plugins can do, somebody has to touch the code. Roamer Tech takes on advanced WordPress development:
