LiteSpeed vs Nginx vs Apache: Best Server for WordPress

LiteSpeed vs Nginx vs Apache is the first question every WordPress owner hits once the site gets slow. The short answer: LiteSpeed is the best server for WordPress for most people, because its cache is built in and managed from your dashboard. Nginx wins when a technical team owns the server. Apache stays relevant for compatibility, but it is the heaviest of the three under load.

If you run a store, the answer gets more specific, so we cover which one is better for WooCommerce in its own section, with a decision chart you can follow in 30 seconds.

Quick answer: which is the best server for WordPress?

One honest caveat before we go deeper: caching matters more than the server brand. A cached page is fast on all three. What separates them is how easy it is to get caching right, and how well they behave on pages that can never be cached, such as the cart and checkout.

What does a web server do for WordPress?

The web server receives each browser request, serves static files (images, CSS, JavaScript) directly, and passes dynamic requests to PHP. PHP runs WordPress and queries the database. The server also handles HTTPS, compression, HTTP/2 or HTTP/3, and the rewrite rules behind pretty permalinks.

So the server does not run WordPress itself. It orchestrates. How it handles many connections at once, talks to PHP and caches pages decides how your site behaves in a traffic spike. That is why the choice matters most for busy sites and for stores built on WooCommerce, where many requests are personal and uncacheable.

How do Apache, Nginx and LiteSpeed work?

Apache: flexible, but heavier

Apache handles connections with processes or threads depending on its MPM (prefork, worker or event). Its signature feature is .htaccess: any folder can carry its own rules, and many WordPress plugins write redirects and security rules there automatically. The cost is performance. The Apache documentation itself notes that allowing .htaccess makes the server check for and reload those files on every request. Under heavy concurrency, Apache also uses more memory than event-driven servers.

Nginx: lean and built for concurrency

Nginx is event-driven: a few worker processes juggle thousands of connections with low memory. It ignores .htaccess, so every rule lives in the server config and needs a reload. WordPress runs through PHP-FPM, and permalinks need a try_files rule. It is superb when someone technical owns it. It is less forgiving on shared hosting, because a plugin that writes to .htaccess has no effect on Nginx. If you want to build one yourself, our guide to installing Nginx, PageSpeed, MariaDB and PHP and our tips to optimize performance with Nginx are a good start.

LiteSpeed: Nginx-style engine with Apache compatibility

LiteSpeed Web Server is also event-driven, but it reads Apache configuration and .htaccess rules, so existing plugins keep working. PHP runs through LSAPI, LiteSpeed’s native interface. There are two editions. LiteSpeed Enterprise is commercial and the most Apache-compatible. OpenLiteSpeed is free and open source, but per its rewrite rules documentation it supports rewrite rules only and needs a restart for changes to apply.

LiteSpeed vs Nginx vs Apache: performance compared

With a working page cache, all three serve a WordPress page in a few milliseconds. The differences appear in two places: uncached requests (cart, account, admin, search) and high concurrency, where event-driven servers need less memory than Apache.

Be careful with spectacular benchmark claims. Vendor tests often measure static files or an empty page. For example, one CyberPanel test reports 604 ms for Nginx against 29 ms for LiteSpeed, but it does not publish the cache setup, so it cannot be treated as a like-for-like result. Third-party comparisons tend to show the same pattern: LiteSpeed with LSCache and a tuned Nginx FastCGI cache land close together, both well ahead of an uncached setup, while Nginx has a slight edge on raw, uncached PHP-FPM proxying.

We are not publishing invented numbers here. Instead, the table below rates what each server is naturally good at, and the test section shows how to measure your own site in ten minutes.

Caching: where the real gap is

This is LiteSpeed’s real advantage. The plugin tells the server exactly which pages to cache and purge, and it also handles image optimization, CSS and JavaScript optimization and object cache connections. Note that the plugin’s server-level cache features need a LiteSpeed server or the QUIC.cloud CDN. On Apache or Nginx only its optimization features work.

Nginx can match LiteSpeed on hit rate, but you build and maintain the rules yourself. A minimal starting point looks like this:

# Skip cache for logged-in users and WooCommerce sessions
set $skip_cache 0;
if ($request_method = POST) { set $skip_cache 1; }
if ($http_cookie ~* "wordpress_logged_in|woocommerce_items_in_cart|wp_woocommerce_session") { set $skip_cache 1; }
if ($request_uri ~* "/wp-admin/|/cart/|/checkout/|/my-account/") { set $skip_cache 1; }

fastcgi_cache_bypass $skip_cache;
fastcgi_no_cache $skip_cache;

Details live in the official Nginx FastCGI module docs. Every new plugin that sets a cookie is a potential cache miss or, worse, a private page served to the wrong visitor, so test after each change.

Which one is better for WooCommerce?

A store is the hardest test for a server, because cart, checkout and account pages must never come from a shared cache, while product and category pages should. Search, filters and AJAX cart fragments add more uncacheable load. You can see how this plays out on real stores in our roundup of successful WooCommerce sites.

LiteSpeed for WooCommerce

The LiteSpeed Cache plugin ships WooCommerce-aware defaults: it excludes the cart, checkout and account pages and purges product pages when stock, price or orders change. With ESI (Edge Side Includes, a LiteSpeed Enterprise feature; not in OpenLiteSpeed), a cached page can hold one live block, such as the mini-cart, so you do not have to bypass the whole page for visitors who added something to the cart. You should still verify add-to-cart, coupon and checkout flows after enabling it.

Nginx for WooCommerce

Nginx handles uncached WooCommerce traffic very well: its event loop is efficient at feeding PHP-FPM pools, and you can tune upstreams, rate limits and load balancing precisely. The price is manual work. Without native ESI, logged-in or cart-holding visitors usually bypass the cache entirely, and you maintain the cookie rules yourself. It is the right pick when you have a developer or DevOps person.

Apache for WooCommerce

Apache works, especially on the event MPM with PHP-FPM and a caching plugin. On a small store it is fine. As concurrent shoppers grow, its memory use rises faster than the other two, and there is no native HTTP/3.

HTTP/3, security and control panels

HTTP/3 (standardized as RFC 9114) runs over QUIC instead of TCP, which speeds up connection setup and copes better with packet loss, mostly helping mobile visitors. LiteSpeed supports it natively. Nginx offers it through a module available since 1.25.0, which the official docs still describe as experimental and which must be enabled at build time. Apache httpd 2.4 has no HTTP/3 module, so Apache sites usually get it from a CDN. HTTP/3 will not rescue a slow site, but it shortens a step every first-time visitor pays.

Security. LiteSpeed Enterprise includes ModSecurity-compatible rules and connection-level throttling. Nginx relies on community modules or an upstream WAF, and its limit_req_zone rate limiting works well against login brute force. No server replaces application security. Follow our WordPress security checklist and always run HTTPS with a valid SSL certificate.

Control panels. LiteSpeed and OpenLiteSpeed work with CyberPanel, cPanel, Plesk and DirectAdmin. Nginx pairs with panels such as aaPanel and RunCloud, or is configured by hand.

LiteSpeed vs Nginx vs Apache: comparison for WordPress stores

Decision chart: which server should you pick?

How to test your own server in ten minutes

1. Identify the server. Run:

   curl -sI https://your-site.com/ | grep -i -E "^server|x-litespeed-cache|alt-svc|cf-cache"

   A server header shows LiteSpeed, nginx or Apache unless a CDN hides it. x-litespeed-cache: hit confirms a cache hit, and alt-svc mentioning h3 means HTTP/3 is offered. In WordPress you can also check Tools > Site Health > Info > Server.

2. Measure time to first byte.

   curl -o /dev/null -s -w "TTFB: %{time_starttransfer}s  Total: %{time_total}s\n" https://your-site.com/

   Run it twice. The second run should be faster if the cache works.

3. Test uncached pages separately (cart, checkout, a search URL). These reveal real server and PHP limits.
4. Load test a staging copy with a tool such as k6 or ApacheBench, never your live store.
5. Track Core Web Vitals. Server speed mostly affects TTFB and LCP. See Google’s Web Vitals guide.

Switching servers safely

• Apache to LiteSpeed: usually seamless thanks to .htaccess compatibility. Disable your old cache plugin, install LiteSpeed Cache and re-test checkout.
• Apache to Nginx: translate rewrite, redirect and access rules from .htaccess into server blocks. Plugins that write .htaccess will no longer take effect.
• Nginx to LiteSpeed: rebuild caching from the plugin dashboard and remove the old FastCGI bypass rules.

Always take a full backup, switch on a staging copy first and keep an eye out for server errors afterwards. If something breaks, our guides on the 500 internal server error and common WordPress errors will help. Testing locally first? See how to run WordPress on localhost.

Frequently asked questions

Is LiteSpeed faster than Nginx for WordPress?

With a properly configured cache on both, the difference visitors notice is small. LiteSpeed’s edge is that its cache is built in and managed by a plugin, so more sites actually reach a high hit rate. Nginx can have a slight advantage on raw, uncached PHP-FPM workloads.

Which is better for WooCommerce, LiteSpeed or Nginx?

LiteSpeed is easier for most stores thanks to WooCommerce-aware cache rules and ESI. Nginx is a great choice when you have a developer who will tune bypass rules, upstream pools and Redis.

What is the best server for WordPress overall?

For the majority of site owners, LiteSpeed with the LiteSpeed Cache plugin. For self-managed, developer-run infrastructure, Nginx.

Can Nginx read .htaccess?

No. Nginx ignores .htaccess files. Rules must be moved into the server configuration and reloaded.

Does the LiteSpeed Cache plugin work on Nginx or Apache?

Its image, CSS and JavaScript optimizations work anywhere. Its page cache and other LiteSpeed-specific features need a LiteSpeed server, LiteSpeed-powered hosting or the QUIC.cloud CDN.

Is Apache still good for WordPress in 2026?

Yes. WordPress’s own requirements page lists Apache and Nginx as recommended servers. It works well with a page cache but uses more memory under heavy load and has no native HTTP/3.

OpenLiteSpeed or LiteSpeed Enterprise?

OpenLiteSpeed is free and fine for many WordPress sites. Enterprise adds fuller Apache configuration compatibility, ESI and commercial support, which matters most on multi-site or multi-tenant hosting.

Final verdict

If you want one recommendation: use LiteSpeed for WordPress and WooCommerce unless you have a reason not to. Use Nginx when you control the server and want fine-grained tuning. Keep Apache for compatibility. Then focus on what moves the needle more than the server: page caching, Redis, a fast theme and lean plugins. Browse our best free WooCommerce themes and must-have WordPress plugins to finish the job.

Facts checked against official Apache, Nginx, OpenLiteSpeed and W3Techs sources in October 2026. Ratings in the chart are editorial opinion, not benchmark data.