Why Is My Website Slow? Hosting Causes and Fixes
A practical guide to diagnosing a slow website: how to measure with Core Web Vitals, how to tell whether the hosting or the site is to blame, and what to fix first.

Compare a few hosting offers and you will see “LiteSpeed servers” near the top of the feature list. So, what is LiteSpeed, and does it make a real difference to a WordPress site, or is it just another buzzword? This guide explains it without the jargon: what a web server does, how LiteSpeed works, what its built-in LSCache does for WordPress, and how to switch it on and confirm it is working.
Every website needs a program on the server that receives requests from browsers and sends back pages, images and files. That program is the web server. The best-known ones are Apache, Nginx and LiteSpeed.
LiteSpeed Web Server is made by LiteSpeed Technologies and was first released in 2003. It comes in two main editions:
The key point: LiteSpeed Enterprise was designed as a drop-in replacement for Apache. A host can swap Apache for LiteSpeed without you rewriting your site’s configuration.
In the traditional Apache setup found on many servers, each connection gets its own process or thread. As simultaneous visitors grow, memory use climbs quickly.
LiteSpeed uses an event-driven architecture: a small number of processes juggle thousands of connections instead of dedicating one worker to each visitor. In practice that usually means lower resource use and steadier behavior under load.
This matters for WordPress. WordPress and many plugins write rules into the .htaccess file, such as permalinks and redirects. LiteSpeed Enterprise reads .htaccess and understands mod_rewrite rules the way Apache does, so those rules generally keep working unchanged. A handful of rarely used Apache modules aren’t supported, but they don’t affect a typical WordPress site.
| Apache (standard setup) | LiteSpeed Enterprise | |
|---|---|---|
| Reads .htaccess | Yes | Yes |
| Connection handling | Depends on config, often one process/thread per connection | Event-driven |
| Server-level page cache with a WordPress plugin | Not built in | Yes, LSCache + LiteSpeed Cache plugin |
| HTTP/3 | Not included in standard Apache 2.4 releases; usually provided by a CDN or proxy in front | Supported, on by default on cPanel |
WordPress builds each page on demand: it runs PHP, queries the database and assembles the theme and content. It repeats that work for every visitor, even if the page hasn’t changed in a week.
A page cache saves a finished HTML copy of the page the first time it is built and hands that copy to the next visitors.
LiteSpeed’s page cache, LSCache, lives inside the web server itself. When a page is cached, the server returns it directly, without starting PHP or touching the database. Plugin-only caches have to work from inside WordPress or through rewrite rules they write for the server; with LSCache, caching is a native server feature and the plugin simply tells the server what to store and when to clear it.
The server can’t tell on its own when a WordPress page has changed. The free LiteSpeed Cache plugin is the bridge: it tells the server what to cache, what to skip and when to purge, for example when you edit a post or change a product price. For WooCommerce, it excludes the Cart, Checkout and My Account pages by default, since those are different for every shopper.
| Feature | Needs LiteSpeed server or QUIC.cloud? |
|---|---|
| Full-page caching | Yes |
| ESI (cache a page with a personalized block inside) | Yes, and not available on OpenLiteSpeed |
| WooCommerce-aware caching | Yes |
| CSS/JS minify and combine | No, works anywhere |
| Object cache via Redis or Memcached | No, if your host provides the service |
| Image optimization and WebP | No |
So installing LiteSpeed Cache on a non-LiteSpeed host leaves out its headline feature.
HTTP/3 is the newest version of the protocol browsers use to talk to websites, and it runs on top of QUIC. It shortens connection setup and copes better with patchy networks such as mobile data.
On LiteSpeed with cPanel, QUIC is on by default for HTTPS sites with a trusted certificate, as long as UDP port 443 is open on the server. Modern browsers use HTTP/3 automatically; older ones connect the usual way. There is usually nothing for you to configure. One exception: if your site sits behind a proxy CDN, visitors connect to the CDN, so HTTP/3 then depends on the CDN rather than on LiteSpeed.
Honestly, no. LiteSpeed raises the floor, but it can’t fix:
Software vendors publish benchmarks showing big gains, but real results vary from site to site. Measure your own site before and after any change. If speed is still a problem, our guide Why is my website slow? walks through the other usual suspects.
server: LiteSpeed response header means you’re on LiteSpeed. Or simply ask your host.X-LiteSpeed-Cache: miss the first time and X-LiteSpeed-Cache: hit on reload. See the official installation docs for troubleshooting.Note: LiteSpeed’s compatibility list marks Cloudflare APO as incompatible with the plugin; regular Cloudflare without APO works.
Tip: try new settings on a staging copy of your site before touching the live one.
Every Start Bigger hosting plan runs on LiteSpeed with LSCache, NVMe storage, and Redis and Memcached. WP Toolkit lets you spin up a staging copy to test settings safely, and if your site is hosted elsewhere, we migrate it for free. Compare the options on our hosting plans page.
.htaccess and runs WordPress without changes.Yes. The plugin is free in the official WordPress.org plugin directory. Its page caching only works on a LiteSpeed server or through the QUIC.cloud CDN, while its general optimization features work on any server.
You can install it and use the general features such as CSS/JS minification, image optimization and a Redis or Memcached connection. Full-page caching will not work without a LiteSpeed server or QUIC.cloud, so on those hosts another caching plugin may suit you better.
No. LiteSpeed's documentation says to deactivate all other full-page cache plugins before activating it, because two plugins doing the same job conflict. You can keep a plugin for a different purpose if you switch off its overlapping features.
LiteSpeed Enterprise is the commercial edition built as a drop-in Apache replacement that works with control panels like cPanel. OpenLiteSpeed is the free, open-source edition; it shares the core engine but lacks some features, such as ESI support in the LiteSpeed Cache plugin.
LiteSpeed is a web server whose main job is serving pages quickly, and it supports ModSecurity firewall rules. It does not replace keeping WordPress and plugins updated, strong passwords, malware scanning and regular backups.
A practical guide to diagnosing a slow website: how to measure with Core Web Vitals, how to tell whether the hosting or the site is to blame, and what to fix first.
An honest look at what a server in Germany means for visitors in Jordan and the Gulf: what distance really adds, when it matters, how caching and a CDN reduce it, and how to measure it yourself.
A checklist for recording every online asset your business depends on, who controls it and when it renews, so a departing developer or employee never takes your domain or site with them.
We answer on WhatsApp Saturday to Thursday, 9:00 am – 9:00 pm Amman time (GMT+3)