What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
For most new or small WooCommerce stores, capable shared or managed WooCommerce hosting is the better starting point. WooCommerce does not require a VPS by default. It requires a host that meets its current PHP, database, HTTPS, memory, backup, and caching requirements.
Choose a VPS when measurements show that shared limits are slowing checkout or administration, or when you need root access for Redis, database tuning, custom services, or firewall control. A VPS gives you isolated resources, but a self-managed plan also makes you responsible for patching, security, backups, monitoring, and recovery.
What is the difference between shared hosting and a VPS?
Shared hosting places many customer accounts on one physical server. The provider manages the operating system and usually supplies a control panel, web server, PHP, databases, SSL, backups, and support. Your account receives a portion of the machine’s CPU, memory, storage, and PHP workers. Limits may be enforced per account, even when the server still has unused capacity.
A virtual private server (VPS) partitions a physical machine into virtual servers. Your VPS receives an allocated amount of CPU, RAM, and storage that is isolated from neighboring customers. You normally get root or administrator access, allowing you to install services, change web-server settings, tune the database, and configure your own firewall. Isolation improves predictability, but it does not automatically make a poorly configured store faster.
#1 Best Overall
There are two operational models for each option:
- Managed hosting: the provider handles much of the operating system, updates, security, monitoring, and support.
- Self-managed hosting: you or your administrator handle those tasks. A self-managed VPS offers the most control and the largest operational burden.
That distinction matters more than the word “VPS” on a sales page. A managed shared plan may be a safer choice for a small business than an unmanaged VPS, while a managed VPS can provide isolation without requiring an in-house system administrator.
Does WooCommerce require a VPS?
No. WooCommerce’s current server recommendations for version 10.8 and later list WordPress 6.9 or greater, PHP 8.3 or greater (tested up to PHP 8.4), MySQL 8.0 or MariaDB 10.6 or greater, HTTPS, and a WordPress memory limit of at least 256 MB. Apache or Nginx is recommended. The recommendation is about the software environment, not a particular hosting product.
“Before you install WordPress and WooCommerce, verify that your hosting environment meets the following requirements.” — WooCommerce, Server Recommendations
Recommended Free Tools
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
WordPress.org similarly asks hosts about PHP 8.3 or newer, MariaDB 10.11 or newer or MySQL 8.0 or newer, Apache or Nginx with mod_rewrite, and HTTPS. It notes that hosting is more secure when PHP applications run under the account username rather than the server’s default shared username.
Older PHP and database releases may continue to run, but they are end-of-life and can leave a store exposed to known vulnerabilities. Before comparing plans, ask the provider for the exact versions available on the account you will use, not merely the versions supported somewhere on the server.
Minimum environment checklist
| Component | Current WooCommerce baseline | What to verify with a host |
|---|---|---|
| WordPress | 6.9 or greater | Whether updates are supported and tested with your theme and extensions |
| PHP | 8.3 or greater; tested up to 8.4 | Selectable PHP version, worker limits, memory per process, and extension availability |
| Database | MySQL 8.0 or MariaDB 10.6 or greater | Actual engine and version, storage performance, and database backup method |
| Memory | WordPress memory limit of at least 256 MB | Whether the limit is available to both front-end requests and the administrator |
| Web server | Apache or Nginx recommended | HTTP/2 or HTTP/3 support, rewrite rules, compression, and access to logs |
| Transport security | HTTPS required | Included SSL certificate, renewal process, and forced HTTPS redirects |
When shared hosting is the better choice
Shared hosting is a sensible default for a starter store or a store with modest, predictable traffic. WooCommerce’s 2026 hosting guide describes a starter tier for stores making less than $10,000 per month and says dedicated servers and real-time backups are unnecessary at that stage. That $10,000 figure is a guide threshold, not a universal capacity limit: product count, checkout concurrency, extensions, and traffic patterns matter more than revenue alone.
Advantages for a small store
- Lower operational workload: the provider normally maintains the operating system, web server, PHP builds, certificates, and basic monitoring.
- Lower initial cost: you pay for an account rather than a full virtual machine and may avoid separate administration fees.
- Useful built-ins: good plans include preinstalled WooCommerce, SSL, automatic backups, a control panel, staging, and support familiar with WordPress.
- Simpler recovery: account-level snapshots or restore tools can be easier to use than assembling your own backup and disaster-recovery system.
Look for a provider that publishes current PHP and database versions, gives enough PHP workers and memory, supplies automatic backups, and offers WooCommerce-aware support. An inexpensive account that repeatedly throttles PHP or has no reliable restore process is not a bargain.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →The caching rule that determines whether shared hosting works
Catalog pages are mostly read operations and can usually be cached. Product detail, category, and informational pages should be served from a full-page cache or CDN when the content is safe to cache. Cart and checkout pages are different: prices, stock, customer identity, shipping, taxes, payment sessions, and coupons are dynamic. They must bypass full-page caching.
A correct configuration therefore has two paths:
- Cacheable: logged-out catalog and content pages, with cache purged when products, prices, or inventory change.
- Dynamic: cart, checkout, account, payment callbacks, and other session-dependent requests, with cookies and query strings handled correctly.
A host using cPanel, LiteSpeed, and CloudLinux LVE can be perfectly adequate without root access if the account has enough CPU, RAM, and PHP workers for real checkout traffic. LogicWeb’s guidance is to move when you need root access, a custom daemon, or you can measure CloudLinux limits during checkout rather than upgrading based on a vague feeling.
When a VPS becomes the better option
A VPS is justified when a measured bottleneck requires resources or controls that your shared account cannot provide. Typical triggers are persistent checkout latency, account throttling, database contention, or a requirement for services that cannot be installed in a shared environment.
For a self-managed Linux VPS in the USA East, Netherlands, or Ukraine, Antihost VPS provides full root access on AMD Ryzen 9 9950X3D with NVMe storage, 1 to 16 vCPUs, 2 to 64 GB RAM, and unlimited traffic on a 1 Gbps port.
Free tools Windows power users keep installed
One-click scans. No signup required.
Resource isolation and predictable capacity
On a VPS, allocated CPU, RAM, and NVMe or SSD storage are reserved for your virtual machine. Neighboring accounts are less likely to create sudden contention. Isolation does not guarantee a fast store: an undersized VPS, an unindexed database, or an inefficient extension can still be slow. It gives you a stable resource ceiling that can be measured and increased.
Root access and custom services
Root access lets an administrator install Redis or another object cache, tune database buffers and indexes, run a queue worker, configure a custom daemon, add firewall rules, and choose a specific web-server stack. Those capabilities are useful for unusual integrations, high order volume, or a development workflow that requires background processing.
Operational responsibility
On a self-managed VPS, you own the tasks a shared provider normally performs:
- Operating-system and kernel patching
- PHP, web-server, and database updates
- Firewall and SSH hardening
- Malware detection and security response
- Off-site backups and restore testing
- Uptime, disk, memory, and queue monitoring
- Incident response when checkout fails
- Capacity planning before campaigns
Bluehost’s current WooCommerce VPS information distinguishes these models explicitly: self-managed customers handle their operating system, configurations, and applications, while managed hosting handles updates, patches, and monitoring. Confirm the scope in writing; “managed VPS” is not a standardized level of service.
Performance: what to measure before upgrading
Do not move to a VPS solely because a store feels slow. Establish a baseline for logged-out catalog pages, logged-in administration, cart, and checkout. Test at different times and during a realistic load, because a fast homepage does not prove that payment requests are healthy.
PHP workers
PHP workers execute the code that renders product data, prices, inventory, and checkout. If all workers are busy, new requests wait even when CPU usage looks moderate. WooCommerce’s official hosting guide suggests asking about PHP-worker allocation and gives 5–10 dedicated workers as a starting point. The correct number depends on extension count, request duration, traffic, and how much work is moved to cache or background jobs.
Time to first byte and errors
WooCommerce’s guide identifies these practical signals of an undersized host:
- Checkout TTFB consistently above 800 milliseconds
- A WordPress admin that becomes slow after reaching about 5,000 products or 10,000 orders
- Slowdowns or 502 errors during a promotion
- Support repeatedly telling you to disable plugins instead of identifying the resource limit
These are guidance thresholds, not guarantees for every stack. Measure from a location near your customers, record whether the request was cached, and correlate latency with PHP-worker saturation, database CPU, memory pressure, and external payment or tax APIs.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchObject caching, CDN, and scaling
Object caching stores repeated database lookups so WordPress does not rebuild the same data for every request. A built-in CDN can serve static files closer to visitors, reducing connection and transfer time. Vertical scaling lets you increase CPU or RAM quickly when a campaign or influencer mention creates a sudden spike. WooCommerce recommends asking a host specifically about PHP workers, object caching, a built-in CDN, vertical scaling, and WooCommerce-specific support.
Shared hosting vs VPS: decision matrix
| Situation | Better starting point | Reason |
|---|---|---|
| New store, modest traffic, limited technical staff | Managed shared or managed WooCommerce hosting | Lower operational burden; current software, SSL, backups, and support matter most. |
| Existing store with measured resource throttling at checkout | VPS or a higher managed tier | Isolated resources and server tuning address a documented bottleneck. |
| Need Redis, custom daemons, unusual integrations, or root firewall control | VPS | Root access enables services and database or cache tuning unavailable on many shared plans. |
| Revenue-critical store without an internal sysadmin | Managed WooCommerce hosting or managed VPS | The provider handles more patching, monitoring, and infrastructure work. |
| Traffic spikes from campaigns or promotions | A host with vertical scaling, CDN, object cache, and WooCommerce support | Dynamic-page handling and surge capacity matter more than the hosting label. |
Cost: compare the whole first year and renewal year
Advertised introductory pricing can hide the actual cost of operating a store. Add the renewal rate, contract term, VAT or GST, control-panel licenses, backup storage, managed support, migration, monitoring, and the value of staff time.
For example, Bluehost’s current UK VPS page displays an NVMe 2 offer at £3.46 per month renewing at £4.20 per month, and an NVMe 8 offer at £9.59 per month renewing at £21.41 per month. These are provider-specific offers that may change; they are not a market-wide VPS price or a prediction of your total bill.
| Cost item | Shared hosting questions | VPS questions |
|---|---|---|
| Plan price | What is the renewal price and minimum term? | Is billing based on allocated CPU, RAM, storage, and bandwidth? |
| Management | Are PHP, web-server, and security updates included? | Is the VPS self-managed or managed, and exactly what does management cover? |
| Backups | How often are backups made, how long are they retained, and are restores included? | Are snapshots and off-site copies included, and who tests restores? |
| Licenses | Is the control panel included? | Are control-panel, security, CDN, or object-cache licenses extra? |
| Support | Can support diagnose PHP-worker and database limits? | Is there 24/7 infrastructure escalation during an outage? |
| Migration | Is migration included or charged separately? | Who configures the web server, SSL, mail, DNS, and monitoring after migration? |
How to decide, step by step
- Write down the workload. Record monthly visitors, peak concurrent sessions, product count, order count, payment gateways, subscriptions, shipping or tax integrations, and the busiest campaign.
- Check the software baseline. Confirm WordPress 6.9 or newer, PHP 8.3 or newer, MySQL 8.0 or MariaDB 10.6 or newer, HTTPS, and at least a 256 MB WordPress memory limit.
- Verify account limits. Ask for PHP-worker count, CPU and RAM limits, entry-process limits, database limits, inode or storage limits, and what happens when a limit is reached.
- Review cache behavior. Confirm that logged-out catalog pages can be cached while cart, checkout, account, and payment callbacks bypass full-page cache. Test coupons, stock changes, shipping calculations, and logged-in sessions.
- Measure real checkout traffic. Record TTFB, total response time, PHP-worker utilization, database load, and HTTP errors during a representative test. Do not use a cached homepage as the deciding metric.
- List required services. If you need Redis, a queue worker, a custom daemon, database tuning, or root firewall control, determine whether the host provides it or whether you need a VPS.
- Price both operating models. Compare first-year and renewal-year totals, then add management, backups, monitoring, migration, and staff time.
- Choose the least complex option that passes the tests. Start on managed shared hosting when it meets the requirements and metrics. Select a managed VPS when isolation is needed but administration is not your team’s strength. Select a self-managed VPS only when you can operate it reliably.
Migration and validation checklist
Whether you stay shared or move to a VPS, validate the environment before switching DNS:
- Confirm WordPress, PHP, database, HTTPS, and memory versions against the current WooCommerce requirements.
- Create a full backup of files and the database, and verify that a restore can be completed.
- Clone the store to staging and test product pages, search, filters, coupons, tax, shipping, payment authorization, webhooks, emails, refunds, and stock reduction.
- Test logged-out catalog pages and checkout separately. Confirm catalog pages can cache while cart and checkout intentionally miss cache.
- Measure checkout TTFB and error rates under realistic load before deciding that a VPS is necessary.
- Confirm backup frequency, retention, restore testing, patch ownership, security monitoring, and support escalation in writing.
- Lower DNS TTL before the cutover, schedule the change during a quiet period, and keep the old host available until orders, webhooks, and email are verified.
- After DNS propagation, monitor PHP errors, database connections, payment callbacks, abandoned carts, CPU, memory, disk, and backup jobs for at least one full business cycle.
Common mistakes and how to correct them
Choosing a VPS before proving the bottleneck
A VPS may only reproduce the same slow plugin, unoptimized query, or remote API delay at a higher monthly cost. Profile slow requests and inspect logs first. Upgrade when the evidence points to account-level throttling or a resource ceiling.
Caching checkout pages
Serving a cached checkout can expose another customer’s address, show stale totals, or break payment sessions. Exclude cart, checkout, account, and gateway callback URLs and test with separate browsers and customer accounts.
Ignoring renewal pricing
An introductory rate can make a plan appear cheaper than it is. Record the renewal amount, term, taxes, licenses, and management fees before committing.
Assuming “managed” covers everything
Ask whether management includes operating-system patches, WordPress updates, vulnerability response, backups, restore testing, monitoring, and incident response. Get exclusions and response times in writing.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteRunning an unmanaged VPS without recovery practice
Root access does not replace operations expertise. Use least-privilege accounts, key-based SSH, a firewall, automatic security updates where appropriate, off-site encrypted backups, tested restores, alerting, and a documented recovery procedure.
Final recommendation
Start with managed shared or managed WooCommerce hosting if your store is new or small, your traffic is predictable, and the account meets the current WooCommerce baseline. Configure caching correctly, verify PHP workers and memory, and test checkout rather than judging performance by the homepage.
Move to a VPS when measured checkout limits, persistent high TTFB, administrative slowdown at larger catalog or order volumes, or promotion-time errors show that shared resources are the constraint. Choose managed VPS hosting when the store is revenue-critical and no one on your team can own server operations. Choose self-managed VPS hosting only when you have the skills and time to patch, secure, monitor, back up, and recover it.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →
