What Is LiteSpeed and Why It Matters for WordPress
A plain-English look at the LiteSpeed web server and its built-in LSCache: what it really does for WordPress speed, and what it can't fix on its own.

You open your site on your phone and wait. Then wait some more. The visitor you paid to bring in from an ad gives up before anything appears. So you ask the obvious question: why is my website slow? Is it the hosting, or the site itself?
The honest answer is that it can be either, or both. The common mistake is jumping to a fix before diagnosing: moving to a new host when the real problem is a 5 MB hero image, or compressing images while the server takes two seconds to respond. This guide measures first, separates hosting causes from site causes, then fixes things in order.
Run your URL through Google’s PageSpeed Insights and look at two parts of the report:
Google’s three Core Web Vitals and their thresholds, as published on web.dev, are assessed at the 75th percentile of visits:
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | When the biggest element (hero image or headline) appears | 2.5 s or less | over 4 s |
| INP (Interaction to Next Paint) | How quickly the page responds to taps, clicks and typing | 200 ms or less | over 500 ms |
| CLS (Cumulative Layout Shift) | Whether things jump around while loading | 0.1 or less | over 0.25 |
One more number is essential for diagnosis even though it is not a Core Web Vital: TTFB (Time to First Byte), how long until the first byte arrives from the server. web.dev considers 0.8 seconds or less good and anything over 1.8 seconds poor.
This is the most useful part of the article. A simple rule of thumb:
Quick tests that help:
WordPress builds every page from scratch: it runs PHP, queries the database, then sends the result. Page caching stores a ready-made copy and serves it instantly to the next visitor, and missing page caching is one of the most common reasons for a high TTFB. An object cache such as Redis or Memcached adds another layer by keeping the results of repeated database queries in memory, which especially helps pages that cannot be fully cached, like a shop cart or the dashboard.
Newer PHP releases are generally faster and safer, and old ones stop receiving security fixes. WordPress currently recommends PHP 8.3 or newer. Check your version in your hosting panel and test the upgrade on a staging copy first, because some older plugins may not be compatible.
On shared hosting, many sites share one server. Without fair per-account limits, one busy site can eat the CPU and memory and slow yours down. And if your plan’s resources are too small for your traffic, you will see slowdowns and errors precisely at peak times.
Storage type and the web server itself affect how quickly files are read and requests answered. NVMe drives are much faster than traditional disks, and some web servers, such as LiteSpeed, include built-in caching that integrates with WordPress. We cover this in detail in what is LiteSpeed and why it matters for WordPress.
Every request makes a round trip, and distance adds a little to each one. It is usually a smaller factor than the causes above, and a CDN helps by serving static files from locations close to your visitors.
The number one cause of poor LCP. A 4000-pixel camera photo shown in an 800-pixel space is pure waste. Fix it by:
The count matters less than what each plugin does. Some load CSS and JavaScript on every page even if they are used on one; others run expensive database queries. A tool like the Query Monitor plugin reveals slow queries. A practical method: on a staging copy, deactivate suspect plugins one at a time and measure after each.
Multipurpose themes and page builders can add a lot of code, and every third-party script, from chat widgets and trackers to maps and embedded videos, adds time and often hurts INP. For each one, ask: do I really need this on every page?
Over time, post revisions, expired transients, leftover settings from deleted plugins and spam comments pile up. Clean them periodically, after taking a backup.
Sending visitors from http to https, then to www, then to another page adds needless round trips. Use the final URL directly in your ads and emails.
| What you see | Likely cause | Where to start |
|---|---|---|
| High TTFB on every page | No caching, old PHP or too few resources | Hosting settings and caching |
| Slow at peak times, 503 errors | Plan resources too small for the traffic | Review the plan or the host |
| Good TTFB, poor LCP | Large images, render-blocking fonts or scripts | Images and front end |
| Poor INP | Heavy JavaScript, third-party scripts | Theme, plugins, scripts |
| High CLS | Images or ads without dimensions, font swaps | Theme and content |
| Very slow dashboard | Heavy plugins or a bloated database | Plugins and database |
If you have done all of that and TTFB is still high, it is probably time for hosting that suits your site better. Every Start Bigger hosting plan runs on LiteSpeed with LSCache, NVMe storage, Redis and Memcached, with CloudLinux account isolation to limit how much one account can affect the others, and WP Toolkit gives you a staging copy to test updates safely. We also move your current site for free; see how to move a WordPress site without downtime. That said, good hosting will not fix an oversized image or a badly coded plugin; that part stays with the site.
If you would rather not handle updates, backups and security yourself, our Managed Site service takes care of them for one WordPress site while you keep full dashboard access.
Google uses Core Web Vitals rather than a single load time. Aim for Largest Contentful Paint (LCP) of 2.5 seconds or less, Interaction to Next Paint (INP) of 200 milliseconds or less and Cumulative Layout Shift (CLS) of 0.1 or less, for at least 75% of visits.
No. If your server response time (TTFB) is already good and the slowness comes from huge images or heavy scripts, an upgrade will barely help. Upgrading or switching hosts pays off when the server itself is slow to respond or runs out of resources at busy times.
There is no magic number. One badly built plugin can slow a site more than twenty lightweight ones. What matters is what each plugin does: whether it loads files on every page or runs heavy database queries. Remove what you do not use and test the heavy ones.
Visitors usually get a ready-made cached copy of the page, while the dashboard is built fresh on every request. A very slow dashboard usually points to heavy plugins, a bloated database or limited server resources.
Yes, distance adds time to every round trip between the browser and the server. It is usually a smaller factor than missing caching or a heavy page, and a CDN reduces its impact on static files such as images and scripts.
A plain-English look at the LiteSpeed web server and its built-in LSCache: what it really does for WordPress speed, and what it can't fix on its own.
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)