Litespeed vs Apache for WooCommerce performance?

Posted on

Litespeed vs Apache for WooCommerce performance? – Problems with loading a website are often blamed on the Internet connection, but even the most perfectly set up network cannot help if there is no service to reply at your destination. One of the most popular HTTP servers used for this task is Apache2. Much of Apache’s popularity can be attributed to its easy installation and use, but never the less it is possible to run into problems with even the easiest of the software. If you’ve encountered an issue loading your web page, follow these simple troubleshooting methods outlined in this guide to attempt to get your web server back up and working again. Below are some tips in manage your apache2 server when you find problem about apache-2.2, php, wordpress, litespeed, .

I currently run a wp/woocommerce site that’s been optimized as far as I can take it for an Apache server:

MySQL memory optimized WP Rocket MaxCDN

VPS: 2 cores 2 gigs of ram SSL

The site offers about 50 different services while it updates & cycles through orders every hour. It’s a WP/WC site so it has a small blog and account area for customers. There will also have some free web based tools available soon.

My biggest bottleneck is probably PHP and around 70 requests to the server on page load.

From what I’ve been reading Litespeed is still faster, but I’m not sure if I’ll see much of an improvement if my apache server is already optimized, especially if I change to fastcgi. Also, it’s not very clear to me what some of the limitations may be. The last thing I want is to change web servers to find parts of my site stopped functioning.

Do I need to worry about my PHP scripts not working with LiteSpeed, or can Litespeed handle everything you could throw at an apache server?

Litespeed has an ESI which supports section cache. Also it’s wordpress cache plugin has a particular custom thirdparty support for woocommerce.

Just give it a shot:

https://wordpress.org/plugins/litespeed-cache/

Theoretically, partly cache for your site should at least help you speed up those 70 requests per page load. Server level cache should make wordpress faster than php level cache. That is why it is faster than super cache I think:

https://ops.kickassd.com/wp-super-cache-vs-litespeed-wordpress-cache/

@Tim

The reason I recommend Litespeed for this situation is Litespeed can cache block and serve different content even using same URL. Have a look at https://nyphper.wordpress.com/2017/02/23/how-to-use-litespeed-vary-to-generate-different-caches-for-one-page-url-php/

This is a easy test to understand this smart way:)

Changing between Apache vs. Litespeed vs. OpenLitespeed will not have much affect on immediate performance, as the bigger concern is optimizing your configuration (settings) rather than just swapping servers.

That said, if you are running a high-traffic WooCommerce site than there might be a lot of uncached dynamic queries (esp. on your checkout and cart pages) going on meaning your database performance and RAM are important here, try:

MySQL + object cache (e.g. Redis) + plenty of RAM memory for Redis to use (seriously high traffic sites might consider a dedicated/managed remote database server)

Besides that, stop using janky WordPress cache plugins like WP Super Cache or WP Rocket and use actual server-level caching instead, like the pros do. Those plugins are fine on low-traffic sites that want an easy way to manage caching, but not for high-traffic.

This is why Nginx is so easy for standalone high-traffic sites like this, because you simply setup a LEMP stack server using open source software and FastCGI Cache is included in Nginx already. Free scripts like my own project SlickStack can do the entire setup for you in less than a few minutes (there are several others too, like EasyEngine, Webinoly, WordOps, CentminMod, and more).

Of course, Litespeed has server-level caching too called LSCACHE and Apache has multiple cache features as well, but there are no easy installation scripts for these that I’m aware of meaning that you will need to know exactly how to configure the OS, server, caches, etc, or you will simply need to continue using shared hosting companies that do all that configuration for you (e.g. cPanel).

TLDR both Litespeed and Apache are a better fit for shared hosting companies using e.g. cPanel than for standalone sites looking for cleaner config and faster speed/security. So if you really want to stay using Apache or Litespeed why not just keep using your shared hosting company instead, and ask to upgrade to a better plan or whatever.

As far as “reading that Litespeed is faster” see my answer here, where I briefly warn users that Litespeed has been posting propaganda:
https://webmasters.stackexchange.com/a/137195/104668

Leave a Reply

Your email address will not be published.