Hosting a WooCommerce Store
Set up and optimize a WooCommerce store on GoZen Host. From installation to checkout performance.
WooCommerce powers over 28% of all online stores. It runs on WordPress, which means it runs on any GoZen Host plan. But a store has different demands than a blog. Every product page runs database queries, every cart action triggers PHP, and every checkout must be fast or you lose the sale.
Here’s how to set up WooCommerce properly from the start.
Choosing the Right Plan
WooCommerce is resource-intensive. A small catalog (under 100 products, low traffic) runs fine on shared hosting. Anything bigger benefits from a VPS.
| Store Size | Recommended Plan | Why |
|---|---|---|
| Starter (< 100 products, < 500 visits/day) | WordPress Hosting | LiteSpeed + LSCache handles the load |
| Growing (100-1000 products, 1000+ visits/day) | Managed VPS | More PHP workers, dedicated MySQL, no resource ceilings |
| High-traffic (1000+ products, 5000+ visits/day) | Dedicated VPS | AMD EPYC dedicated cores, no shared resources |
If you’re unsure, start with WordPress Hosting and upgrade when needed.
Installation
Via Softaculous (Fastest)
- Log into cPanel
- Open Softaculous > search for WordPress
- Install WordPress on your domain (see Installing WordPress)
- After installation, log into wp-admin
- Go to Plugins > Add New > search WooCommerce
- Install and activate
- Follow the WooCommerce Setup Wizard
The wizard walks you through:
- Store location and currency
- Payment gateways (Stripe, PayPal, etc.)
- Shipping zones
- Tax settings
SSL Is Mandatory
WooCommerce handles payments. Your site must run on HTTPS. GoZen Host provisions free SSL via AutoSSL automatically. Verify it’s active:
- Visit
https://yourdomain.com- the padlock should be visible - If not, go to cPanel > SSL/TLS Status > Run AutoSSL
Use the GoZen SSL Auditor to confirm your certificate is valid and properly chained.
Performance Optimization
A slow store loses money. Here’s the performance stack, in order of impact.
1. Enable LiteSpeed Cache
This is the single biggest performance improvement. GoZen runs LiteSpeed, so you get server-level caching for free.
- Install the LiteSpeed Cache plugin
- Go to LiteSpeed Cache > Cache > enable Cache Logged-in Users = OFF (important for WooCommerce)
- Go to LiteSpeed Cache > Cache > WooCommerce tab:
- Privately Cache Cart = ON
- Privately Cache Cart Page = ON
See LiteSpeed Cache for WordPress for the full configuration guide.
Don’t cache checkout or cart pages publicly. Each customer’s cart is unique. LiteSpeed Cache handles this correctly with private caching, but other caching plugins might not. Stick with LiteSpeed Cache on GoZen.
2. Optimize Images
Product images are the heaviest part of any store page.
- Use WebP format (LiteSpeed Cache converts images automatically via Image Optimization)
- Set maximum image dimensions in Settings > Media (1200px wide is enough for most themes)
- Use lazy loading (LiteSpeed Cache enables this in Media Settings)
3. Reduce Database Bloat
WooCommerce creates database entries for every session, cart, order, and log. Over time this bloats the database.
Clean up regularly:
- Delete old transients: LiteSpeed Cache > Database > Clean All
- Limit post revisions: add to
wp-config.php:define('WP_POST_REVISIONS', 5); - Clear Action Scheduler logs: WooCommerce > Status > Scheduled Actions > delete completed actions older than 30 days
4. Use a CDN
A CDN serves your product images and static files from servers near your visitors. Cloudflare’s free plan works well:
- Sign up at cloudflare.com
- Add your domain
- Update nameservers to Cloudflare’s
- Set SSL mode to Full (Strict)
- Enable caching for static assets
5. Minimize Plugins
Every plugin adds PHP execution time. For WooCommerce stores:
- Keep: WooCommerce, LiteSpeed Cache, a payment gateway, shipping plugin
- Remove: social share buttons (use theme features), popup builders (use WooCommerce’s built-in), SEO plugins that duplicate functionality
- Evaluate: if a plugin adds less than 1 second to page load, it’s probably fine. If it adds 2+, find an alternative
Essential Plugins for WooCommerce
| Purpose | Recommended Plugin | Notes |
|---|---|---|
| Caching | LiteSpeed Cache | Included with GoZen. Don’t use WP Super Cache or W3TC alongside it |
| SEO | Yoast SEO or Rank Math | Pick one, not both |
| Security | Already handled | GoZen includes cPGuard at the server level |
| Backups | Already handled | GoZen runs Backuply daily |
| Payment | Stripe or PayPal | Official WooCommerce extensions |
| WP Mail SMTP | If using a transactional email service |
Security for Stores
An online store handles customer data and payments. Extra care:
- Keep everything updated: WordPress core, WooCommerce, all plugins, and your theme
- Use strong unique passwords: for wp-admin, cPanel, database, and SFTP
- Enable two-factor authentication: in wp-admin and in the GoZen client area
- PCI compliance: if you use Stripe or PayPal, they handle card processing on their servers. Your site never touches card numbers. This is the simplest path to PCI compliance
- cPGuard blocks malicious requests at the server level before they reach WordPress
Troubleshooting
| Problem | Fix |
|---|---|
| Checkout page is slow | Enable private caching in LiteSpeed Cache WooCommerce settings. Check for heavy plugins running on checkout |
| 508 Resource Limit error during sale | Traffic spike exceeded CloudLinux limits. Enable caching and consider upgrading to VPS |
| Payment gateway timeout | Usually a gateway-side issue, not hosting. Check Stripe/PayPal status page |
| Products not showing | Check WooCommerce > Status > System Status for errors. Verify PHP memory limit is at least 256M |
| Email notifications not sending | Set up WP Mail SMTP with a proper SMTP relay. Don’t rely on PHP mail() for transactional emails |
What to Do Next
- LiteSpeed Cache for WordPress - full caching configuration
- Securing WordPress - lock down your store
- CloudLinux Resource Limits - monitor your store’s resource usage
- Outgrown Shared Hosting? - when your store needs more power
Last updated 07 Apr 2026, 00:00 +0200.