Understanding Your GoZen Hosting Stack
What CloudLinux, LiteSpeed, cPGuard, and NVMe actually do for your site, and how they work together.
GoZen Host shared and WordPress hosting doesn’t run on a generic LAMP stack. Every account runs on a specific combination of technologies chosen for performance and security: CloudLinux + LiteSpeed + cPGuard + NVMe storage. Here’s what each piece does and why it matters.
The Stack at a Glance
| Component | What It Replaces | Why GoZen Uses It |
|---|---|---|
| CloudLinux | Standard CentOS/AlmaLinux | Isolates every account so one bad neighbor can’t crash your site |
| LiteSpeed | Apache | Serves pages faster, uses less memory, and has built-in caching |
| cPGuard | No equivalent (add-on) | Real-time malware scanning, WAF, and brute force protection, included free |
| NVMe SSD | SATA SSD / HDD | 5-10x faster disk I/O than traditional SSDs |
CloudLinux
Standard shared hosting puts every account on the same OS. If one site gets a traffic spike or runs a runaway PHP script, everyone on that server feels it. CloudLinux fixes this.
How It Works
CloudLinux creates a Lightweight Virtualized Environment (LVE) around each hosting account. Every account gets its own resource allocation:
- CPU - percentage of CPU cores available to your account
- Memory - physical RAM limit
- I/O - disk read/write speed limit
- Entry Processes - number of concurrent PHP processes
- Inodes - maximum number of files
What This Means For You
- Your site’s performance doesn’t depend on what other accounts on the server are doing
- If you hit a resource limit, only your account is affected, not the whole server
- You can see exactly how much of each resource you’re using
Checking Your Resource Usage
In cPanel, go to Metrics → Resource Usage. You’ll see:
- Current and historical usage for CPU, memory, I/O, and processes
- Whether you’ve hit any limits (shown as “faults”)
- Usage trends over the past 24 hours
If you see frequent faults, you’re outgrowing your current plan. Either optimize your site or upgrade to a higher plan.
LiteSpeed Web Server
Apache is the default on most cPanel hosts. GoZen runs LiteSpeed instead.
Why LiteSpeed
- Faster static file serving - serves HTML, CSS, JS, and images with less overhead than Apache
- HTTP/3 support - the latest protocol, faster connection setup, especially on mobile networks
- Built-in page caching - LiteSpeed Cache (LSCache) can cache entire pages at the server level, bypassing PHP entirely
- Lower memory footprint - handles more concurrent users with the same hardware
- .htaccess compatible - your existing Apache rewrite rules work without changes
LiteSpeed Cache (LSCache)
LSCache is the biggest performance win. Instead of running PHP on every page load, LiteSpeed serves a cached HTML copy directly. This drops your Time to First Byte (TTFB) from hundreds of milliseconds to single digits.
For WordPress users: Install the LiteSpeed Cache plugin to control caching from your WordPress dashboard. See LiteSpeed Cache for WordPress for the full configuration guide.
For other applications: LSCache can be controlled via .htaccess rules or the LiteSpeed API. Check the LiteSpeed documentation for your specific framework.
cPGuard
cPGuard is a server-level security suite included with all GoZen Host cPanel plans at no extra cost. It runs in the background and protects your account from common threats.
What cPGuard Does
| Feature | What It Protects Against |
|---|---|
| Real-time malware scanning | Detects and quarantines infected files as they’re uploaded or modified |
| Web Application Firewall (WAF) | Blocks SQL injection, XSS, and other common web attacks |
| Brute force protection | Rate-limits login attempts on cPanel, WordPress, and other apps |
| Outgoing spam detection | Catches compromised accounts sending spam before they damage your IP reputation |
| CMS vulnerability scanning | Checks WordPress, Joomla, and other CMS installs for known vulnerabilities |
For a detailed walkthrough of cPGuard’s dashboard and configuration, see Using cPGuard.
NVMe Storage
All GoZen Host plans use NVMe (Non-Volatile Memory Express) SSDs instead of traditional SATA SSDs.
The Difference
| Metric | SATA SSD | NVMe SSD |
|---|---|---|
| Sequential read | ~550 MB/s | ~3,500 MB/s |
| Sequential write | ~520 MB/s | ~3,000 MB/s |
| Random I/O (IOPS) | ~90,000 | ~500,000+ |
| Latency | ~100 μs | ~20 μs |
In practice, this means database queries run faster, file operations complete sooner, and your site loads faster under concurrent traffic. The difference is most noticeable on database-heavy applications like WordPress with WooCommerce, where every page load triggers dozens of queries.
How They Work Together
Here’s what happens when a visitor loads your page:
- LiteSpeed receives the request. If the page is cached in LSCache, it serves the cached copy immediately (sub-5ms response). Done.
- If not cached, LiteSpeed passes the request to PHP. CloudLinux ensures your PHP processes run within your resource allocation.
- PHP queries your database. NVMe makes those disk reads fast.
- cPGuard inspects the request at the WAF level, blocking anything malicious before it touches your application.
- LiteSpeed caches the generated page for next time.
The result: fast page loads, isolated resources, and built-in security without needing to configure anything yourself.
What to Do Next
- LiteSpeed Cache for WordPress - configure caching for the best performance
- Using cPGuard - check your security dashboard and scan results
- PHP Configuration - tune PHP settings for your application
Last updated 07 Apr 2026, 00:00 +0200.