Apache vs Nginx vs LiteSpeed – Best WordPress Server in 2026?

The short answer: for WordPress, what makes the biggest difference isn’t the choice of server itself but full-page caching at server level. LiteSpeed (OpenLiteSpeed or LiteSpeed Enterprise) with the LiteSpeed Cache plugin gives you that practically ‘out of the box’, and Nginx – on its own or as a reverse proxy in front of Apache – can do the same with FastCGI cache or proxy cache: in both cases the cached page is sent without running PHP, so TTFB drops dramatically. Apache on its own, without page caching and with an outdated configuration (prefork + mod_php), comes off worst in this comparison.

Installing WordPress is dead simple whichever server you choose – Apache, Nginx or LiteSpeed. Most of the hassle is actually creating the database, a user for that database and keeping track of the login details. The WordPress installation process itself is 75% waiting for files to upload to the server, 20% generating the access details you need, and only 5% the actual installation. It turns out, though, that even at this stage you can make decisions that will make your WordPress site run out-of-this-world fast! That’s because it matters that you choose the right server for your WordPress site. I don’t even mean which hosting company you pick, but what software that company uses. Some servers, it seems, are simply better suited to running WordPress than others.

Apache, Nginx or LiteSpeed for WordPress?

You’ve probably heard of Apache servers? It’s one of the oldest and most widespread server solutions in the world. Apache is free, stable, versatile and relatively easy to configure and manage (not least thanks to .htaccess files). But there are two other options that are at least as good as Apache, and in some cases better: the Nginx and LiteSpeed server software.

According to W3Techs (data from October 2026), among websites whose server can be identified, the most common is Cloudflare Server (31.5%) – although in practice that’s a CDN/proxy layer with a ‘real’ server behind it – followed by Nginx (30.7%), Apache (21.8%) and LiteSpeed (14.2%). The remaining share goes to other solutions, e.g. Node.js or Microsoft’s IIS (3.0%). In 2022, when I wrote the first version of this article, Apache was still in the lead – its share has dropped noticeably since then.

Apache and Nginx are similar in terms of what they can do, but they differ in architecture. Nginx has handled connections in an event-driven (asynchronous) model from the start, which is why it uses less memory with many simultaneous connections. Classic Apache (MPM prefork + mod_php) keeps a separate process for each connection, which can be costly under load. That’s one of the reasons sites on Nginx are often a bit faster. Bear in mind, though, that modern Apache 2.4 with the event MPM and PHP via PHP-FPM is in a completely different league from old prefork – more on that below.

Alongside Apache and Nginx there’s the commercial LiteSpeed, which according to its makers can theoretically handle twice as much traffic as an Apache-based server with the same configuration. Sure, marketing talk isn’t limited to SEO or burgers – it applies to server software too. But what if I told you there really is something to it, and that sites running on LiteSpeed are noticeably faster? And that includes WordPress!

Apache vs Nginx vs LiteSpeed – comparison (as of 2026)

	Apache 2.4	Nginx (and the Angie fork)	OpenLiteSpeed / LiteSpeed Enterprise
Licence	Apache License 2.0, free	Nginx: open source (BSD); Angie: BSD-type licence	OLS: GPLv3, free; LSWS Enterprise: commercial (there’s a free Free Starter plan: 1 domain, up to 2 GB RAM)
Current versions (October 2026)	2.4.69 (1 Oct 2026)	stable 1.30.5, mainline 1.31.6 (15 Sep 2026); Angie 1.12.2	–
Connection handling model	MPM of your choice; event MPM recommended	event-driven (asynchronous)	event-driven
PHP	PHP-FPM via mod_proxy_fcgi (or mod_php with prefork)	PHP-FPM via FastCGI	LSAPI (LSPHP)
.htaccess	yes	no (rules in the server configuration)	Enterprise: yes, changes detected without a restart; OLS: rewrite rules only, changes require a restart
HTTP/3 (QUIC)	no native support in httpd 2.4 – usually provided by a CDN or proxy in front of Apache	since version 1.25.0 (ngx_http_v3_module); Angie – also to the backend	yes, enabled by default in LSWS (requires a certificate and open UDP 443)
WordPress page cache	cache plugins (static files) or mod_cache	FastCGI cache / proxy cache + optionally a plugin	LSCache + the LiteSpeed Cache plugin
Hosting control panels	cPanel, Plesk, DirectAdmin and others	Plesk, DirectAdmin, VPS panels (often as a proxy in front of Apache)	Enterprise: Apache replacement in cPanel, Plesk, DirectAdmin; OLS: e.g. CyberPanel

OpenLiteSpeed vs LiteSpeed Enterprise

OpenLiteSpeed is the free, open-source (GPLv3) version of the server. LiteSpeed Enterprise (LSWS) is the commercial version you’ll most often find on shared hosting – it’s a drop-in Apache replacement: it reads Apache configuration, supports .htaccess and works with cPanel, Plesk and DirectAdmin. The Enterprise version also has ESI (caching page fragments, useful e.g. for logged-in users and shops), built-in protection against brute-force attacks on the WordPress login and its own ModSecurity engine. For a single site on a small VPS there’s a Free Starter licence (1 domain, up to 2 GB RAM). So if you’re choosing shared hosting ‘on LiteSpeed’, it’s almost always LSWS Enterprise.

Nginx, Angie and Apache with event MPM + PHP-FPM

Nginx is developed in two branches: stable (1.30.x in October 2026) and mainline (1.31.x). HTTP/3 has been available since version 1.25.0 – all you need is to add the quic parameter to the listen directive. Angie is an Nginx fork created by former developers from the nginx team; it’s compatible with Nginx configuration and adds its own features, including HTTP/3 for connections to backend servers too.

Apache 2.4 is still actively developed (2.4.69 from 1 October 2026). If your WordPress site runs on it, check whether your host uses the event MPM – in this mode idle keep-alive connections are handled by a separate listener thread instead of blocking a whole process. The event MPM doesn’t get on well with mod_php, though (problems with PHP extensions that aren’t thread-safe), which is why the typical, recommended set-up is event MPM + PHP-FPM via mod_proxy_fcgi. There’s no native HTTP/3 in Apache 2.4 – if you want it, a CDN (e.g. Cloudflare) or Nginx placed in front of Apache will provide it.

Whatever the server, keep PHP up to date – WordPress currently recommends PHP 8.3 or newer and MySQL 8.0+ or MariaDB 10.11+. Interestingly, WordPress’s official requirements still name Apache or Nginx as the most robust servers.

WordPress test results on Apache/Nginx/LiteSpeed

In December 2021 the hosting company chemicloud.com published the results of its tests comparing the performance of servers running Apache / Nginx / LiteSpeed. According to the author, the tests were run on unmodified server configurations – the servers were simply installed and started. The site itself was a plain WordPress install with the Twenty Twenty-One theme active.

Note: the results below come from ChemiCloud’s December 2021 test and are now historical – the versions of all three servers and of PHP have changed since then. The charts from the original test are no longer available, so I’ve collected the key numbers in a table.

Metric (ChemiCloud test, 12.2021)	Apache	Nginx	LiteSpeed
Requests handled per second (more = better)	approx. 150	clearly more than Apache, fewer than LiteSpeed	over 750
Data transfer per second (more = better)	approx. 42k KB/s (42 MB)	–	approx. 71k KB/s (71 MB)

A clear win for LiteSpeed, which managed to handle over 750 requests per second while Apache buckled at 150. A rout. Note the far-from-bad result for Nginx, which did clearly better than Apache – although it fell well short of LiteSpeed.

Here you can see that LiteSpeed not only handles more requests per second, but can also transfer more data per second. Apache can deliver around 42k KB/s (42 MB), while LiteSpeed almost doubles that to 71k KB/s (71 MB).

As if that weren’t enough, they also checked the performance of the WordPress site in GTmetrix (similar kinds of tests to Google’s PageSpeed Insights) – and LiteSpeed came out best there too. Remember, though, that these were default configurations: a well-configured Nginx with page caching, or Apache with the event MPM and PHP-FPM, can narrow that gap significantly.

The LiteSpeed server and WordPress

As you know, WordPress doesn’t have many built-in options for optimising performance or loading. It’s simply a content management system. That’s why the plugin directory has lots of solutions that extend WordPress’s functionality, including plugins that let you optimise your site’s loading time.

For Apache and Nginx servers, the plugins that usually work best are:

• W3 Total Cache
• WP Super Cache
• WP Fastest Cache
• PageSpeed Ninja
• Autoptimize
• WP Rocket
• NitroPack

and many more. Practically every one of them has a paid version with extra features. Some work better on sites built with Elementor or other page builders, others with custom-made themes. There’s also always a chance that some feature won’t work the way you want, and in general you can spend quite a while testing different plugins and features.

With a WordPress site running on a LiteSpeed server, the problem of choosing a plugin practically disappears. That’s because there’s one fantastic plugin that will solve 90% of your problems: LiteSpeed Cache. It’s made by the creators of the LiteSpeed server and built to optimise sites on LiteSpeed servers as well as possible. Out of this world!

With a LiteSpeed server and the LiteSpeed Cache plugin installed in WordPress, getting high scores in PageSpeed Insights or improving your Core Web Vitals is very easy. And it’s not a plugin that fools the testing tools – it genuinely improves how fast the page loads in the browser! Of course, a lot really depends on how the site’s theme is built – for both desktop and mobile. The LiteSpeed Cache plugin won’t magically fix every problem the theme creates. It can only make the theme load a bit faster.

Does LiteSpeed Cache work on Apache or Nginx?

Partly. According to the plugin’s description in the WordPress.org directory, page caching (the ‘LiteSpeed Exclusive’ features) requires OpenLiteSpeed, commercial LiteSpeed, LiteSpeed-based hosting or the QUIC.cloud CDN. On Apache or Nginx only the general features will work – image optimisation, CSS/JS minification, lazy loading, database clean-up and CDN support. So on plain Apache/Nginx, the LiteSpeed Cache plugin alone won’t replace page caching.

Page caching and TTFB: LSCache vs nginx cache vs plugins

The biggest difference in WordPress speed doesn’t come from choosing Apache, Nginx or LiteSpeed as such, but from whether and where the page is cached. Without a cache, every visit means running PHP, querying the database and building the page from scratch – hence a high TTFB (Time To First Byte). You have three main options:

• LSCache (LiteSpeed) – a cache built into the server and controlled by the LiteSpeed Cache plugin. The plugin purges the cache itself after content changes, and in the Enterprise version ESI lets you cache page fragments (e.g. for logged-in users).
• nginx FastCGI cache / proxy cache – Nginx stores the ready response from PHP-FPM (FastCGI cache) or the response from the server behind it, e.g. Apache (proxy cache). According to the nginx documentation, caching time can be controlled by response headers (X-Accel-Expires, Expires, Cache-Control), which take precedence over the settings in the configuration. The downside: you have to take care of bypassing the cache for logged-in users and the basket, and of purging it after publishing, yourself.
• Cache plugins (WP Super Cache, W3 Total Cache, WP Rocket etc.) – generate static HTML files. They work everywhere, but the request still reaches the web server, and depending on the configuration sometimes PHP too – they’re usually slower than a server-level cache, although still much faster than no cache at all.

Example: semurai.pl on nginx in front of Apache

This blog runs on MyDevil (a Polish hosting provider), where nginx sits in front of Apache. After switching on page caching in nginx in a mode controlled by WordPress’s Cache-Control headers (WordPress on this site sends anonymous visitors Cache-Control: public, max-age=0, s-maxage=600, i.e. 10 minutes in the server cache), TTFB dropped from about 2–4 s to about 50 ms for cached pages – I measured it with curl in October 2026. The first visit to a page that isn’t in the cache yet still takes a few seconds; subsequent ones are served straight from nginx, without running PHP. I didn’t have to switch the server to LiteSpeed for this – setting up the cache properly was enough.

Don’t forget to optimise WordPress

And once your site is up and running on WordPress, don’t forget to set it up and optimise it properly! In WordPress a lot of things can be done with plugins, which can seriously slow a site down. To make sure your site works as it should, you can turn to professionals for WordPress optimisation!

LiteSpeed hosting for WordPress not so great after all?

You can find critical opinions about LiteSpeed. Because LS has relatively low hardware requirements, it’s possible to run the server on a somewhat weaker spec, or to run more websites on the same configuration than with Apache.

From an SEO point of view, it doesn’t matter to me how much support a given server has. What matters is how fast it can deliver the data I care about and how much crawl budget I can save as a result. I’ve never yet come across a situation where something couldn’t be done because the server ran on LiteSpeed. In 2022 I partly put that down to there not being many hosts offering LiteSpeed – today that’s less true, because according to W3Techs LiteSpeed serves about 14% of websites with an identifiable server.

Add to that the fact that the LiteSpeed team offers a plugin for popular CMSs practically out of the box, and you might wonder whether the server would do just as well without it. In the end, though, what counts is page load time, and for WordPress it’s pretty good at the very least.

Of course, you should think hard about whether changing server software, or even your hosting company, just to save a few milliseconds makes sense, when what you really need is better optimisation of your theme or plugins – and page caching, as the semurai.pl example above shows. In 2022 I wrote that if I were launching a new site, I’d probably choose a LiteSpeed-based server – and for anyone who wants a fast WordPress site without configuring the cache by hand, that’s still a sensible choice.

FAQ – choosing a server for WordPress

LiteSpeed or Nginx – which is faster for WordPress?

In tests on default configurations (e.g. ChemiCloud, 2021), LiteSpeed won. In practice, TTFB is decided mainly by page caching: both LiteSpeed with LSCache and Nginx with FastCGI cache or proxy cache send the cached page without running PHP (on semurai.pl with nginx proxy cache that’s about 50 ms). LiteSpeed is easier to manage, because the plugin configures everything.

Is Apache still a good choice for WordPress?

Yes, especially with the event MPM + PHP-FPM set-up and page caching (a plugin, or Nginx/a CDN in front of Apache). The old prefork + mod_php combination without any cache comes off worst.

OpenLiteSpeed or LiteSpeed Enterprise?

For your own VPS with one or a few sites, the free OpenLiteSpeed is usually enough (remember that changes to .htaccess require a restart). Enterprise is useful on hosting with cPanel/Plesk, when you need full compatibility with Apache’s .htaccess and when you need ESI. For one domain on a server with up to 2 GB RAM there’s the free Free Starter licence.

Does a WordPress server need to support HTTP/3?

It doesn’t have to, but it’s a nice extra, especially on mobile devices. LiteSpeed has HTTP/3 enabled by default, Nginx has supported it since version 1.25.0, and with Apache the easiest way to get it is through a CDN or Nginx placed in front of the server.

So what’s your take on this?