LiteSpeed vs. Apache vs. Nginx: Which Web Server for WordPress?

LiteSpeed delivers 5,200 req/s, Apache manages 600. 50x less RAM at 10,000 connections with Nginx. Benchmark numbers, feature comparison, costs, and which web server fits which WordPress setup.

WordPress powers over 40% of all websites. Most of them run on Apache. Many of those sites could load 3 to 8 times faster with a web server switch alone – no changes to WordPress itself. The web server is the invisible layer between visitor and PHP code. It determines how many concurrent requests your hosting can handle, how fast the first byte reaches the browser, and how much RAM your server burns per visitor.

This comparison puts Apache, Nginx, and LiteSpeed side by side with concrete benchmark numbers. No marketing, no opinions – just measurements. If you are currently weighing Shared vs. Managed vs. VPS hosting, read our hosting comparison first. For the full picture on hosting strategy, see our hosting overview.

Market share 2026 – who dominates

The web server landscape has shifted over the past five years. Apache held over 50% market share in 2015. Today it sits at around 25% and continues to decline. Nginx leads at 34%. LiteSpeed is the rising contender – from under 5% in 2020 to 15% now, driven by shared hosting providers looking to increase server density.

Cloudflare shows up in the statistics but is not a traditional origin server – it is a reverse proxy / CDN. For WordPress hosting, the three main players are Apache, Nginx, and LiteSpeed.

Performance benchmarks: requests per second

The most relevant benchmark for WordPress is requests per second on dynamic PHP pages – without an upstream page cache at CDN level. This shows how efficiently the web server processes PHP requests.

These numbers come from benchmarks on identical hardware: WordPress 6.x, PHP 8.2, MariaDB 10.11. Apache runs mod_php in Prefork MPM – the default configuration on most shared hosts. Nginx uses PHP-FPM. LiteSpeed Enterprise uses LSAPI with the built-in LSCache.

The gap between Apache and LiteSpeed is not a fine margin – these are different orders of magnitude. A VPS with 4 GB RAM running LiteSpeed can handle the same traffic as a dedicated server with 32 GB RAM running Apache. That translates directly to hosting costs.

TTFB – Time to First Byte

TTFB measures the time from request to first received byte. For Core Web Vitals (and therefore SEO), TTFB is an upstream signal. Nginx delivers 15 to 30% better TTFB than Apache with the same PHP configuration. LiteSpeed beats both because on a cache hit, no PHP roundtrip is needed – the response comes straight from the server-level cache.

RAM usage under load

Memory consumption is the silent killer as traffic grows. Apache creates a separate process (Prefork) or thread (Worker/Event) per connection. With 100 concurrent connections using mod_php, 5 to 10 GB of RAM is common. At 10,000 concurrent connections, Apache Prefork stops functioning – socket timeouts, 883 errors, the server is down.

At 10,000 concurrent connections, Nginx needs 15 to 50 MB of RAM. Apache Prefork needs 2,500 MB – 50 times more. The reason is architectural: Nginx is event-based with a main thread and a few worker processes. Apache Prefork spawns a separate process with its own memory space for every connection.

For WordPress sites with traffic spikes (flash sales, viral posts, newsletter sends), this is the deciding factor. A server with 4 GB RAM running Apache buckles at 200 concurrent visitors. The same server running Nginx or LiteSpeed handles 2,000+ connections.

WordPress features compared

Raw performance is one thing. Practical WordPress compatibility is another. Three points matter most: caching, .htaccess support, and plugin compatibility.

Feature	Apache	Nginx	LiteSpeed
Server-level cache	No (plugin only)	FastCGI Cache (manual)	LSCache (built-in)
.htaccess support	Yes (full)	No	Enterprise: Yes / OLS: No
PHP handler	mod_php, PHP-FPM	PHP-FPM	LSAPI (faster than FPM)
WP plugin compatibility	Maximum	High (with adjustments)	Maximum
Cache plugin	WP Super Cache etc.	FastCGI + Nginx Helper	LSCache (5M+ installs)
HTTP/3 (QUIC)	Experimental	Yes (since 1.25)	Yes (native)
Cost	Free	Free / Plus: ~$2,500/year	OLS: free / Enterprise: $79–449/year

.htaccess – why it matters for WordPress

WordPress automatically generates an .htaccess file for permalinks, redirects, and access control. Dozens of plugins (Yoast SEO, Redirection, WP Security) also write to .htaccess. Nginx ignores this file entirely – every rule must be manually translated into Nginx configuration. That works, but requires server access and Nginx expertise.

LiteSpeed Enterprise is the hybrid here: it reads .htaccess files just like Apache while delivering the performance of an event-based server. This makes LiteSpeed Enterprise a drop-in replacement for Apache – you can swap the server without changing a single line of code.

OpenLiteSpeed (the free version) does not support .htaccess. That detail tends to get buried in marketing materials.

LSCache vs. FastCGI Cache vs. plugin cache

The LSCache plugin for WordPress has over 5 million active installations. It is the only cache plugin that communicates directly with the web server – no PHP detour. On a cache hit, LiteSpeed serves the page from memory without touching PHP or MySQL. That explains the high benchmark numbers.

Nginx FastCGI Cache works similarly but requires manual configuration in the server config. There is no official Nginx cache plugin for WordPress. Nginx Helper assists with cache invalidation but does not cover all scenarios (WooCommerce cart, logged-in users, dynamic elements).

Apache has no built-in server-level cache for dynamic content. You rely on PHP-based plugins – WP Super Cache, W3 Total Cache, WP Rocket. These plugins generate static HTML files that Apache then serves. It works, but is slower than a server-level cache because the cache check always runs through PHP. For more on WordPress performance architecture, see our headless WordPress comparison.

Costs and licensing

Apache and Nginx Open Source are free. LiteSpeed uses a tiered model:

Variant	Price	Limitations
OpenLiteSpeed	Free	No .htaccess, limited features
LiteSpeed Enterprise Free Starter	Free	1 domain, max 2 GB RAM
LiteSpeed Enterprise Standard	$79/year	None
LiteSpeed Enterprise (Unlimited)	$449/year	None
Nginx Plus	~$2,500/year	None (enterprise features)

For a single WordPress shop or business website, LiteSpeed Enterprise Free Starter (1 domain, 2 GB RAM) is enough. It is free and delivers full performance including .htaccess and LSCache. If you host multiple domains on a VPS, you need the Standard license at $79/year – that is $6.58 per month, less than the price difference between a 4 GB and an 8 GB VPS.

DACH hosting providers by web server

Not every host lets you choose the web server. On shared hosting, you get whatever the server runs. On VPS and root servers, you choose freely. Our hosting comparison explains the differences in detail.

Web server	DACH hosts
Apache	IONOS, Strato, All-Inkl, Hetzner (Shared), Mittwald
Nginx	Hetzner Cloud, netcup VPS, DigitalOcean, Cloudways
LiteSpeed	rack::SPEED, HostPress, webhoster.de, Hostinger

Most German shared hosts still run Apache. Managed WordPress providers like HostPress and Cloudways use LiteSpeed or Nginx. If you rent a VPS from Hetzner or netcup, you can install the web server yourself – full control. When choosing, also consider GDPR-compliant hosting, especially for providers with data centers outside the EU.

Which web server for which setup

The answer depends on three factors: technical experience, budget, and hosting type.

Choose Apache if: you are on a shared host with no control over the web server. Apache works, is stable, and has the broadest plugin compatibility. For small websites with under 1,000 visitors per day, it is enough. Optimize with WP Rocket or WP Super Cache and a CDN.

Choose Nginx if: you manage a VPS or root server, do not need .htaccess, and are comfortable with server configuration. Nginx is the standard for high-traffic setups and reverse proxy architectures. Headless WordPress with Next.js or Astro? Nginx as a reverse proxy is the best fit.

Choose LiteSpeed Enterprise if: you want WordPress performance with Apache-level simplicity. .htaccess works, LSCache is the best WordPress cache system, and you get 5x the performance of Apache at the same RAM. For WooCommerce shops with traffic spikes, LiteSpeed Enterprise is the most solid choice.

Our recommendation: switching from Apache to LiteSpeed on a VPS takes under an hour. All .htaccess rules, rewrite rules, and plugin configurations stay intact. The performance gain is immediately measurable – in Core Web Vitals, server response time, and security posture (LiteSpeed has built-in DDoS protection and anti-hotlinking).

Conclusion: the numbers favor LiteSpeed

Apache made WordPress big. Nginx showed what a modern web server could look like. LiteSpeed combines the best of both: Apache compatibility with Nginx performance – and outperforms both on WordPress-specific workloads.

For new WordPress projects in 2026, there is little reason to choose Apache when LiteSpeed Enterprise Free Starter is available. The only downside: LiteSpeed is proprietary software, not open source. If that matters, go with Nginx. If you want maximum WordPress performance with minimal configuration effort, go with LiteSpeed.