LiteSpeed web server: benefits, features, and why it matters for WordPress
LiteSpeed Web Server (LSWS) is the web server that runs on every RemarkableCloud managed VPS. It's not the default choice out of convention — it's the technical choice that consistently outperforms Apache and Nginx on the workloads that matter most to hosting customers: WordPress, PHP applications, and high-traffic sites under load.
This article covers what LiteSpeed actually does differently, the specific performance and security advantages it delivers, and why the combination of LiteSpeed and LiteSpeed Cache produces results that other web servers can't match with plugins alone.
- Up to 6x faster than Apache on equivalent hardware for PHP workloads
- Native HTTP/3 and QUIC support — faster connections on modern browsers
- Built-in event-driven architecture: handles thousands of concurrent connections with minimal RAM
- LiteSpeed Cache plugin integrates directly at server level — cache performance other plugins can't reach
- Drop-in Apache replacement: .htaccess compatible, no config migration required
- Built-in anti-DDoS, bandwidth throttling, and connection limiting
Performance: where LiteSpeed outperforms Apache and Nginx
PHP processing speed
Apache uses a process-based model: each request spawns (or reuses) a worker process. Under load, this consumes significant RAM and CPU context-switching overhead. LiteSpeed uses an event-driven, asynchronous model similar to Nginx — but with a key additional advantage: its native PHP SAPI (lsphp) processes PHP directly in the server process without the overhead of FastCGI.
In benchmark testing across PHP-intensive WordPress workloads, LiteSpeed consistently processes 3 to 6 times more requests per second than Apache with mod_php on identical hardware. The gap is most visible under concurrent load: at 50 to 200 simultaneous requests, Apache's worker pool saturates while LiteSpeed continues to queue and serve requests with stable response times.
HTTP/3 and QUIC
LiteSpeed has supported HTTP/3 and QUIC since 2020 — significantly ahead of both Apache and Nginx in production-ready deployment. HTTP/3 uses UDP instead of TCP, which eliminates the head-of-line blocking problem that affects HTTP/2 on lossy connections. For visitors on mobile networks or with variable connectivity, this translates to faster page loads even when network conditions are poor.
Nginx has HTTP/3 support in recent versions, but it's still considered experimental in most distributions. Apache's HTTP/3 support requires third-party modules and is not widely deployed. LiteSpeed's HTTP/3 is stable, enabled by default, and works without additional configuration.
Static file serving
For static files (images, CSS, JS, fonts), LiteSpeed uses kernel-level sendfile() calls and memory-mapped I/O to serve files with minimal CPU overhead. The performance difference vs Apache for static assets is less dramatic than for PHP — Nginx also performs well here — but LiteSpeed maintains the advantage in mixed workloads where PHP and static requests arrive simultaneously.
LiteSpeed Cache: server-level WordPress caching
LiteSpeed Cache (LSCache) is the performance multiplier that sets LiteSpeed apart for WordPress hosting specifically. The plugin is free, but what makes it genuinely different from W3 Total Cache or WP Rocket isn't its feature list — it's the integration layer.
Standard WordPress caching plugins operate at the PHP/application layer: they intercept WordPress requests, check if a cached version exists, and serve it. This still requires PHP to start, WordPress to boot, and the plugin to run before cache can be served. LSCache operates at the web server layer — cached responses are served directly by LiteSpeed without PHP ever loading. The performance difference is significant, particularly under load.
What LSCache includes (free)
- Full-page caching at server level, served before PHP loads
- Object caching for database query results (Redis or Memcached backend)
- Browser cache headers with configurable TTLs per content type
- CSS and JS minification and combination
- Image optimization and WebP conversion on-the-fly
- Critical CSS generation to eliminate render-blocking stylesheets
- ESI (Edge Side Includes) for partial page caching with dynamic content
- CDN integration with BunnyCDN, Cloudflare, and others
- Database optimization — auto-clean transients, revisions, spam
- Crawler to pre-warm the cache on new content
ESI: caching pages with dynamic content
Edge Side Includes is the feature that solves the hardest WordPress caching problem: pages with user-specific or frequently changing content (logged-in user bars, cart quantities, recent comments). Standard caching either skips these pages entirely or serves stale data. ESI allows LiteSpeed to cache the static portions of a page while fetching and inserting dynamic sections on each request — giving you cache performance on pages you'd otherwise have to exclude.
Security features built into the server
Anti-DDoS and connection limiting
LiteSpeed includes configurable per-IP connection limits, request rate limiting, and bandwidth throttling at the server level — before malicious requests reach your application. Apache and Nginx require modules (mod_evasive, limit_req_zone) to achieve similar results; LiteSpeed provides this natively with simpler configuration.
ModSecurity integration
LiteSpeed is fully compatible with ModSecurity rules, including the OWASP Core Rule Set. WAF rules run at the server level with lower overhead than in Apache, because LiteSpeed's event model processes ModSecurity checks asynchronously alongside request handling rather than blocking.
Hotlink and bandwidth protection
Server-level hotlink protection prevents other sites from embedding your images and consuming your bandwidth. Bandwidth throttling limits per-connection transfer rates to prevent a single client from saturating your connection — useful for media-heavy sites or hosting multiple clients on one server.
Apache compatibility: drop-in replacement
One of LiteSpeed's practical advantages for existing hosting customers is that it reads and respects Apache .htaccess files directly. WordPress permalink rules, redirect rules, security headers, and custom rewrite conditions all work without modification. Migrating from Apache to LiteSpeed requires no changes to existing site configurations — which is why RemarkableCloud can migrate cPanel customers from Apache-based hosts without application changes.
LiteSpeed also supports cPanel and DirectAdmin control panels natively, meaning the switch from Apache to LiteSpeed at the server level is invisible to clients who manage their sites through a panel.
Every RemarkableCloud managed VPS runs LiteSpeed as the default web server. LiteSpeed Cache is available for all WordPress sites hosted on the server, free, with server-level integration enabled.
See managed VPS plans →LiteSpeed, managed. From day one.
Every Cloud Cube runs LiteSpeed out of the box. No configuration, no extra cost. We handle the server so you get the performance without the overhead. From $2 your first month.
See Cloud Cube plans


