For most WordPress buyers, the web server matters less than whether the host gives you working server-level page caching. All three servers run WordPress well when caching is set up.
If you want the simplest path to fast pages on shared hosting, look for LiteSpeed, because its free LiteSpeed Cache plugin turns on server page caching with a few clicks.
Nginx is common on managed WordPress and cloud platforms, where the host configures caching for you. Plain Apache works, but usually needs a caching plugin to keep pages fast.
Of all the topics in the web server side of site speed, this one answers a single buying question: which server to look for when you pick a host.
LiteSpeed vs Nginx vs Apache at a glance
The three servers differ mainly in how they handle many visitors at once, whether they read .htaccess files, and how page caching is added.
| Apache | Nginx | LiteSpeed | |
|---|---|---|---|
| Connection model | Processes or threads (MPM) | Event-driven | Event-driven |
| Reads .htaccess | Yes | No | Yes (Enterprise reloads changes live) |
| How PHP runs | mod_php or PHP-FPM | PHP-FPM (FastCGI) | LSAPI |
| Built-in page cache for WordPress | No | FastCGI cache (host must configure) | LSCache, used through the LiteSpeed Cache plugin |
| HTTP/3 | Not listed in the Apache 2.4 docs | Since version 1.25.0 | Yes, both editions |
| Cost | Free, Apache License 2.0 | Free, 2-clause BSD license; paid NGINX One | OpenLiteSpeed free; Enterprise commercial with a free tier |
What a web server does
A web server is the software that receives a visitor’s request and sends back a file or a page that PHP builds.
When someone opens your WordPress site, the web server answers first. It serves images and CSS files directly, and it passes page requests to PHP, which runs WordPress.
It also applies rules such as redirects and HTTPS. On some servers, you edit those rules in a .htaccess file. On others, only the host can.
For your site, this means: the web server shapes how many visitors a plan handles at once and how page caching works. It does not change what WordPress can do.
How Apache handles connections and PHP
Apache handles requests with worker processes or threads, chosen by a module called an MPM (multi-processing module), and it reads .htaccess files in every folder.
Apache’s prefork MPM documentation describes “a non-threaded, pre-forking web server”, suited to sites that must avoid threading for compatibility with older libraries.
The newer event MPM is “a hybrid multi-process multi-threaded server”. A listener thread holds idle keep-alive connections, so worker threads stay free for real work.
A .htaccess file is a small settings file inside a folder. WordPress writes its permalink rules there, and many plugins add redirects or security rules to it.
That convenience has a cost. Apache’s .htaccess tutorial says allowing these files “causes a performance hit, whether or not you actually even use them”.
PHP on Apache runs either inside Apache (mod_php) or as a separate PHP-FPM service. Which handler is faster is covered in the PHP-FPM vs mod_php comparison.
For your site, this means: Apache is the most compatible choice for plugins that edit .htaccess. Speed depends on how the host tuned it and on your caching plugin.
How Nginx handles connections and PHP
Nginx uses an event-driven design where a few worker processes each juggle many connections, and it does not read .htaccess files.
Nginx’s architecture overview describes “one worker process per core” and “the ability to interleave multiple connections within a single worker process”.
Event-driven means a worker never waits on one slow visitor. It moves to the next connection and returns when data is ready.
WordPress’s own Nginx documentation says “there is no directory-level configuration file like Apache’s .htaccess”, and “WordPress cannot modify the configuration.”
The same page says PHP runs through a separate backend, “fastcgi or php-fpm”, and that Nginx can cache pages on its own with fastcgi_cache.
For your site, this means: on Nginx, plugin features that write .htaccess rules do nothing. The host must add redirects and cache rules, or offer a panel for them.
How LiteSpeed handles connections and PHP
LiteSpeed is an event-driven server that reads Apache configuration and .htaccess files, runs PHP through its own LSAPI, and has a page cache built in.
LiteSpeed Technologies’ product page calls it “a drop-in replacement for Apache” that “can load Apache configuration files directly”.
LSAPI is LiteSpeed’s own way of talking to PHP, in place of PHP-FPM. The built-in cache is called LSCache, and the server, not PHP, serves cached pages.
For your site, this means: a LiteSpeed host keeps your .htaccess rules working and gives you server-level caching that you control from inside WordPress.
Why page caching matters more than the server
Page caching decides most of the speed difference you will notice, because a cached page skips PHP and the database entirely.
How the cache layers fit together is covered in hosting-level caching explained. Each server gets page caching in a different way:
- LiteSpeed: the LiteSpeed Cache plugin controls the server’s LSCache.
- Nginx: the host configures FastCGI cache or another server cache; you rarely control it.
- Apache: you usually add a caching plugin. Some serve saved files through .htaccess rules; others still start PHP on each visit.
The LiteSpeed Cache plugin page says its exclusive features, including page caching, need “OpenLiteSpeed, commercial LiteSpeed products, LiteSpeed-powered hosting, or QUIC.cloud CDN”.
Its image, CSS and JavaScript tools work “with any web server”. Installing the plugin on an Apache or Nginx host does not give you its page cache.
Once you are on LiteSpeed, the LiteSpeed Cache settings walkthrough covers what to turn on.
For your site, this means: ask any host how page caching works on your plan. A clear answer matters more than which of the three servers sits underneath.
HTTP/3 support
LiteSpeed and current Nginx both support HTTP/3. Apache 2.4 does not list HTTP/3 support in its official documentation.
The Apache 2.4 module index lists HTTP/2 modules (mod_http2 and mod_proxy_http2) but no HTTP/3 or QUIC module.
Nginx’s QUIC and HTTP/3 page says support “is available since 1.25.0”. A host on an older Nginx may not offer it.
LiteSpeed’s editions comparison lists HTTP/2, HTTP/3 and QUIC in both OpenLiteSpeed and Enterprise.
Apache sites can still get HTTP/3 when a CDN sits in front. What the protocol changes is covered in checking a host’s HTTP/3 support.
For your site, this means: HTTP/3 is a useful extra, not a reason to pick a server, because a CDN can add it on any of the three.
Licensing: free and paid editions
All three servers have a free version, and LiteSpeed and Nginx also sell commercial editions with extra features and support.
- Apache: free and open source from the Apache Software Foundation, released under the Apache License, Version 2.0.
- OpenLiteSpeed: “Open Source, FREE” with community support, per LiteSpeed’s editions page.
- LiteSpeed Enterprise: “Commercial, with FREE tier”, with worker processes limited by license tier.
- Nginx open source: free, “distributed under the 2-clause BSD License” per nginx.org, with community support.
- NGINX One: F5’s paid package. F5 says it unifies “every NGINX component”, including NGINX Plus, into one package.
The editions page also lists differences that affect hosting. OpenLiteSpeed “requires a restart to load any new .htaccess file”. Enterprise “autodetects changes to .htaccess” and works with cPanel and Plesk.
F5’s open source vs NGINX One comparison lists active health checks, a built-in dashboard, a cache purge API and enterprise support as paid extras.
For your site, this means: the license is the host’s cost, not yours. A cPanel host needs Enterprise, since OpenLiteSpeed’s listed panels are CyberPanel and DirectAdmin.
Which hosts run which web server
Several hosts state their web server in their own documentation, and those statements are the only ones listed here.
| Host | Web server it states | Where it says so |
|---|---|---|
| Namecheap (Stellar shared plans) | LiteSpeed 6.2.2 | Software versions article, updated February 19, 2026 |
| Hostinger | LiteSpeed (its Cache Manager “controls only the LiteSpeed web server cache”) | Cache Manager guide |
| Kinsta | NGINX in each site container | Infrastructure documentation |
| SiteGround | “A combination of Apache and NGINX”, with no further detail | Web server explainer |
| Cloudways | Nginx plus Apache2 (default Hybrid stack) or Nginx only (Lightning stack, for apps that “don’t require htaccess”) | Application stack article |
Two of these run accounts we pay for.
Namecheap lists LiteSpeed for Stellar, Stellar Plus and Stellar Business, and the Namecheap shared hosting test ran on Stellar Plus from August 2026.
Hostinger’s server cache fits the LiteSpeed-based Hostinger shared plans we’ve used since December 2024. Our Cloud Startup review, published September 24, 2026, found HTTP/3 and QUIC active.
We also tested Kinsta, though the Kinsta WP 2 account review covers only its first 3 days. SiteGround’s short statement leaves the SiteGround stack and caching setup only partly documented.
On Cloudways, new apps use the Hybrid stack by default, one of the server choices in the Cloudways managed cloud platform.
How to check which web server a host uses
You can often see the web server in the Server response header, but CDNs and hosts may hide or replace it.
MDN’s Server header reference says the header “describes the software used by the origin server”.
To read it, open your browser’s developer tools, go to Network, reload, and click the page request.
Treat the result as a clue, because a CDN may show its own name. The host’s documentation is the safer answer.
To find which company hosts a site, not just its software, a separate lookup guide walks through the other clues.
What the speed claims mean
Most “fastest web server” numbers come from the vendors themselves, so read them as claims, not independent test results.
LiteSpeed’s product page claims it typically cuts “server load in half” and improves “TTFB by 3x” compared with Apache.
Its PHP LSAPI page claims LSAPI is “75% faster than nginx with PHP-FPM”.
The NGINX architecture overview makes a scale claim too: its design lets it reach “hundreds of thousands of concurrent connections on modern hardware”.
These are vendor statements under their own test setups. None of our account data compares the three servers.
For your site, this means: a cached page is fast on any of the three. Differences show up mostly in uncached traffic, such as logged-in users, carts and checkouts.
Which web server should you look for?
The right server depends on who manages it: buyers should judge caching, VPS owners their own skills, and agencies consistency.
Shared or WordPress hosting buyer
Look at page caching first. A LiteSpeed host with the LiteSpeed Cache plugin is the easiest setup to get right yourself.
An Nginx-based managed host is fine too, if server caching is on by default.
When you compare picks for WordPress hosting by use case, ask each host how caching works.
On plain Apache, caching depends on which plugin you add, so check that before a busy launch.
VPS owner
Pick the server you can maintain. Nginx with PHP-FPM is widely documented. OpenLiteSpeed is a free route to LSCache, but it needs a restart to load new .htaccess files.
If you run cPanel on your VPS, LiteSpeed Enterprise is the edition with cPanel support, and its license is an extra cost.
If you’re still weighing managed WordPress or a VPS, settle that first.
Agency managing many client sites
Choose one stack and use it for every client. Repeating the same caching setup, redirect method and backup routine matters more than small speed differences.
If clients use plugins that write .htaccess rules, a LiteSpeed or Apache stack avoids surprises. If your team prefers server-level control, Nginx works well.
Frequently asked questions
Is LiteSpeed faster than Nginx for WordPress?
We know of no independent answer to cite. LiteSpeed’s figures are its own, and with page caching on, both serve cached pages quickly.
Does LiteSpeed Cache work on Nginx or Apache?
Only partly. Page caching needs a LiteSpeed server or QUIC.cloud CDN. The plugin’s image, CSS and JavaScript tools work on Apache and Nginx too.
Does WordPress need .htaccess?
No. WordPress uses .htaccess for permalinks on Apache and LiteSpeed. On Nginx, the host sets the same rules in the server configuration instead.
Is Apache too slow for WordPress?
No. Apache runs WordPress well when the host tunes it and you use page caching. Its .htaccess lookups add some overhead, which Apache’s own documentation acknowledges.
Should I switch hosts just to get LiteSpeed?
Usually not. If your current host already serves cached pages quickly, switching servers adds little. Move only if caching is missing or hard to set up.
How we researched this
We read each server’s official documentation on October 3, 2026: the Apache HTTP Server docs, nginx.org and the NGINX blog, LiteSpeed Technologies, WordPress.org and MDN.
On October 4, 2026, we rechecked F5’s NGINX One comparison, the Apache module index and license, the nginx license, and the HTTP/3 and editions pages.
A host appears in the server table only if its own help center or documentation names the web server. Hosts that don’t state it are left out rather than guessed.
We have not benchmarked the three servers against each other, so every speed figure here is quoted as the vendor’s claim, consistent with the hands-on testing rules we follow.
