Speed & performance · Explainer
Nginx vs Apache vs LiteSpeed for WordPress
Short answer
Nginx, Apache and LiteSpeed all run WordPress well, but they differ in how they handle connections. Nginx and LiteSpeed use an event loop that serves many connections with few workers, while Apache assigns a process or thread to each connection. LiteSpeed adds Apache .htaccess support and a built-in page cache, so it often suits WordPress hosts best.
Key takeaways
- Nginx and LiteSpeed use an event loop, while Apache assigns a process or thread to each connection.
- Nginx has no .htaccess support, Apache reads .htaccess per request, and LiteSpeed Enterprise reads it live.
- LiteSpeed includes LSCache built in, while Nginx and Apache need a plugin or extra cache setup.
- W3Techs counted Nginx on 30.0%, Apache on 21.1% and LiteSpeed on 13.8% of sites with a known server in November 2026.
- LiteSpeed Enterprise starts free for 1 domain and costs $10 to $92 a month for larger licences, as of November 2026.
- WordPress.org recommends PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.4 or greater, and HTTPS support.
What is the core difference between Nginx, Apache and LiteSpeed?
The core difference is how each server handles many connections at once: Nginx and LiteSpeed use an event loop, while Apache assigns a process or thread to each connection.
A web server is the software that takes a browser request, finds the right file or hands the request to PHP, and sends the page back. WordPress needs PHP and a database for most pages, so the server also decides how PHP work is queued. That choice shapes memory use, traffic spikes and cost.
Nginx runs a small set of worker processes, and each worker moves many connections forward in turn. LiteSpeed uses a similar event-driven design, but it reads Apache rules. Apache uses Multi-Processing Modules, called MPMs, to decide between processes and threads.
How does Nginx handle WordPress requests?
Nginx handles WordPress requests with one master process and a small set of worker processes, and each worker serves many connections through an event loop.
The NGINX architecture guide states that there is one worker process per core, and a worker can switch between connections as traffic arrives. The master process reads the config and manages workers, while workers handle requests.
Nginx does not run PHP itself. It passes PHP requests to PHP-FPM, a separate pool of PHP workers, and serves images, CSS and JavaScript files directly. Our guide to how many PHP workers you need for WordPress explains how to size that pool.
Memory use is a clear Nginx strength. The nginx.org home page notes that 10,000 inactive HTTP keep-alive connections take about 2.5 MB of memory, as of November 2026. Idle visitors therefore cost very little while they wait.
Nginx has no .htaccess file. You put rewrite rules, redirects and headers in the central config and reload the service. WordPress permalinks still work, but the rules must be written in Nginx form.
How does Apache handle WordPress requests?
Apache handles WordPress requests by assigning each connection to a process or a thread, using one of its three Multi-Processing Modules: prefork, worker or event.
Prefork gives each connection its own single-threaded process. Worker uses several processes, each with many threads. Event is like worker, but idle keep-alive connections go to a listener thread, so a worker thread is freed sooner.
The Apache 2.4 new features page states that the event MPM is fully supported in version 2.4, as of November 2026. Most modern Apache hosts should run event with PHP-FPM, not prefork with mod_php.
Apache reads .htaccess files in each directory, so plugins and site owners can add redirects, security rules and caching headers without server access.
That freedom has a cost, since Apache checks .htaccess files along the path of each request. The Apache performance tuning guide says to use AllowOverride None in the main config for the highest speed when you can edit it.
WordPress.org names Apache as one of its two recommended server families, and it asks for mod_rewrite on Apache for pretty permalinks. That support is a big reason Apache still runs so much shared hosting.
How does LiteSpeed handle WordPress requests?
LiteSpeed handles WordPress requests as an event-driven server that reads Apache config files and .htaccess directly, so it can replace Apache without rewriting rules.
LiteSpeed Technologies describes its server as a drop-in replacement for Apache that can load Apache config files directly and work with control panels built for Apache, including cPanel, Plesk and DirectAdmin. The product page lists that Apache compatibility, plus its LSCache engine with ESI.
LSCache is built into the server. It stores full pages and serves them without running PHP, and the free LiteSpeed Cache plugin for WordPress controls it. If you already use that plugin, read our guide on whether a cache plugin helps on LiteSpeed hosting.
LiteSpeed runs PHP through LSAPI, its own PHP interface, rather than PHP-FPM. It also supports HTTP/3 over QUIC, which can help visitors on slow or lossy mobile links. HTTP/3 does not change much on a fast wired link.
There are two editions. LiteSpeed Enterprise is paid and closed source, while OpenLiteSpeed is free and open source under GPLv3. The OpenLiteSpeed comparison states that both share the LSCache engine and HTTP/3 support, but OpenLiteSpeed lacks ESI and needs a restart to load new .htaccess rules.
Which server is fastest for WordPress?
No single server is fastest for every WordPress site, because caching, PHP version and hosting limits often matter more than the server name.
For a cached page, all three can serve it fast, since PHP never runs. For uncached pages, the PHP version and the number of PHP workers set the ceiling. Our guide to whether the PHP version affects WordPress speed explains why an old PHP release can slow every uncached page.
Under heavy traffic with many idle connections, Nginx and LiteSpeed tend to use less memory than Apache with prefork, because one worker handles many connections at once. Under light traffic with few visitors, the gap is small and hard to notice.
Vendor speed claims need care. Some hosts publish large speed multiples for cached pages, but those figures come from their own setups and do not match every site. Judge a host by a speed test on your own site, not by a marketing number.
WordPress.org recommends PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.4 or greater, and HTTPS support, as of November 2026. The WordPress.org requirements page lists those numbers. A host that meets them on any of the three servers beats a host that runs old PHP on a faster-named server.
How do Nginx, Apache and LiteSpeed compare side by side?
The table below compares the three servers on the points that matter most for a WordPress site, as of November 2026.
| Point | Nginx | Apache | LiteSpeed |
|---|---|---|---|
| Connection model | Event loop, few worker processes | Process or thread per connection, by MPM | Event loop, like Nginx |
| .htaccess support | No | Yes, read per request | Yes, Enterprise reads it live |
| Built-in page cache | No, needs a plugin or FastCGI cache | No, needs a plugin | Yes, LSCache built in |
| PHP handling | PHP-FPM | PHP-FPM or mod_php | LSAPI |
| Cost to run yourself | Free | Free | Free Starter, then paid licences |
| Best fit | Busy sites, VPS, reverse proxy | Shared hosting, .htaccess sites | WordPress hosts, cPanel sites |
W3Techs counted Nginx on 30.0% of sites with a known web server, Apache on 21.1% and LiteSpeed on 13.8%, on 4 November 2026. The W3Techs web server overview notes that a site can use more than one server, so the shares add up to more than 100%.
Cloudflare Server led the same count at 33.2%, but it sits in front of sites as a CDN, so it is not a direct pick here. W3Techs also named LiteSpeed as one of the fastest-growing web server technologies in its 2025 review, behind Cloudflare Server and Node.js.
How much does each server cost?
Nginx and Apache cost nothing for the software itself, while LiteSpeed Enterprise charges a licence fee per server, as of November 2026.
Nginx is free open source software under the 2-clause BSD licence, according to nginx.org. Apache is also free open source software. Your cost for either is the hosting plan and the time to manage it, not a licence.
LiteSpeed has a free Starter licence for 1 domain, 1 worker and under 2 GB of memory. The LiteSpeed pricing page lists Site Owner at $10 a month for 5 domains, Web Host Enterprise at $65 a month, and Web Host Elite at $92 a month, as of November 2026.
Most WordPress owners never pay LiteSpeed directly. The host pays the licence and folds it into the plan price, so compare hosting plans, not licence pages. Our guide to how to choose WordPress hosting shows what else to check in a plan.
OpenLiteSpeed costs nothing and is free under GPLv3, but it lacks ESI and full .htaccess support, so it suits a single site on your own server more than a shared host.
Which server should you pick for your WordPress site?
Pick LiteSpeed if your host offers it and you want Apache rules plus built-in caching, pick Nginx for a busy VPS, and pick Apache if your site or plugins depend on .htaccess.
| Situation | Best pick | Why |
|---|---|---|
| Shared hosting with cPanel | Apache or LiteSpeed | .htaccess works, and the host manages the server |
| Busy blog or store on a VPS | Nginx | Low memory per idle connection, strong with PHP-FPM |
| WordPress host with caching built in | LiteSpeed | LSCache serves pages without PHP |
| Many plugins that write .htaccess rules | Apache or LiteSpeed Enterprise | Rules apply without a config rewrite |
| Tight budget, own server | Nginx or OpenLiteSpeed | No licence fee |
If you are on shared hosting, you often cannot choose at all. The host picks the server, and your job is to pick a good host. Our guide on whether hosting affects WordPress speed explains the signs of a weak plan.
If you run your own VPS, Nginx with PHP-FPM and a caching plugin is a solid default. Add LiteSpeed only if you need .htaccess rules or its built-in cache, and add Apache only if a plugin or workflow needs it.
How do you find out which server your site uses?
You can find out which server your site uses from the response headers, from WordPress Site Health, or by asking your host.
- Open WordPress admin, go to Tools, then Site Health, then Info, then Server.
- Look for the web server name and PHP version in the Server section.
- If the name is unclear, ask your host in a support ticket.
Site Health also shows your PHP version, so check it against the WordPress.org recommendation of PHP 8.3 or greater. If the site still feels slow after that check, follow our guide to how to speed up WordPress.
Do not change servers just to chase a speed claim. A cached page, a current PHP version and enough PHP workers usually change load time more than a server swap.
What mistakes should you avoid?
The main mistake is picking a server for a marketing claim instead of checking caching, PHP version and host limits first.
- Choosing a server for a speed claim instead of checking caching, PHP version and host limits first.
- Moving Nginx rules by copying .htaccess lines, which Nginx ignores and can break permalinks.
- Running Apache with prefork and mod_php on a busy site, when event with PHP-FPM uses less memory.
- Paying for a LiteSpeed licence on a quiet site that a free server would serve well.
- Judging a server by market share alone, since the largest share does not mean the best fit for your site.
Frequently asked questions
Can I switch from Apache to Nginx without breaking WordPress?
Yes, but you must rewrite your .htaccess rules in Nginx form first, since Nginx ignores .htaccess files. Permalinks, redirects and security rules all live in the Nginx server block. Test the move on a staging copy, check every permalink and form, and keep a backup of the old Apache config until the new setup works.
Is LiteSpeed better than Nginx for WordPress?
LiteSpeed is often easier for WordPress because it reads Apache rules and includes LSCache, its built-in page cache. Nginx can match it on a well-tuned VPS with PHP-FPM and a caching plugin. The better pick depends on your host, your budget and whether your plugins rely on .htaccess rules.
Do I need to choose a web server on shared hosting?
No, the host chooses the server on shared hosting, and most shared plans run Apache or LiteSpeed. You cannot change it yourself, and you do not need to. Focus on the PHP version, caching, backups and support quality instead, and ask the host which server your plan uses if you are curious.
Does the web server change my WordPress speed a lot?
It can help under heavy traffic, but caching, PHP version and host limits usually matter more. A cached page loads fast on all three servers, since PHP never runs. An old PHP version or too few PHP workers will slow uncached pages on any server, so fix those first.
Is OpenLiteSpeed the same as LiteSpeed Enterprise?
No, OpenLiteSpeed is the free open source edition, while LiteSpeed Enterprise is the paid edition. Both share the LSCache engine and HTTP/3 support. Enterprise reads Apache config and .htaccess changes without a restart and adds ESI, while OpenLiteSpeed reads only rewrite rules and needs a restart for changes.
Which server works best with WooCommerce?
Any of the three can run WooCommerce, but caching matters less for logged-in shoppers and checkout pages, which cannot use full-page cache. Pick a host with enough PHP workers, a current PHP version and a fast database, then use a server your host supports well. LiteSpeed and Nginx both suit busy stores when the host tunes them.
Sources
- nginx nginx.org
- NGINX Architecture NGINX Community Blog
- Apache Performance Tuning Apache HTTP Server
- Overview of new features in Apache HTTP Server 2.4 Apache HTTP Server
- Requirements WordPress.org
- LiteSpeed Web Server Pricing LiteSpeed Technologies
- Usage Statistics and Market Share of Web Servers W3Techs
- Should You Upgrade to LiteSpeed Enterprise? OpenLiteSpeed
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
