Most WordPress sites are slow for a boring reason. The hosting underneath them was never tuned for WordPress in the first place. You can install every caching plugin going and still wait two seconds for the first byte, because the bottleneck is the server, not the plugin list.
At Forge, every site runs on LiteSpeed, and we tune it the same way on every server we build. Here is what that actually means.
We start with LiteSpeed, not generic Apache or Nginx
LiteSpeed is a web server built to handle high concurrency without falling over. It serves static files quickly, holds up under traffic spikes, and ships with LSCache, a server-level cache that is faster than any PHP-based caching plugin can be. Because the cache lives in the server rather than in WordPress, a cached page never has to boot PHP or query the database at all. That is where sub-second loads come from.
Object caching with Redis
Dynamic pages, like a logged-in WooCommerce cart or a membership dashboard, cannot be fully page-cached. For those we use Redis object caching, which keeps the results of expensive database queries in memory. The second time WordPress needs the same data, it reads it from memory instead of hammering the database. On a busy store this is the difference between a checkout that feels instant and one that stalls.
PHP tuned for real workloads
We run a current, supported version of PHP on every server, with worker counts and memory limits set for the size of the site rather than left on a shared default. Old PHP is one of the most common reasons a site feels sluggish, and on shared hosting you often cannot change it. On a Forge server it is set correctly from day one and kept up to date.
A CDN in front of everything
Your images, CSS, and JavaScript are served from a content delivery network, so a visitor in another country is not waiting on a round trip to your origin server for every asset. Combined with LSCache, most of what a visitor downloads is served from the edge, close to them, already compressed.
The boring details that actually matter
- GZIP and Brotli compression on by default, so pages travel smaller.
- HTTP/3 enabled, so assets load in parallel without head-of-line blocking.
- Image optimisation and lazy loading, so a heavy page does not block the first paint.
- The database kept lean, with overhead cleared and queries indexed.
None of these are exotic. The reason they make such a difference is that, on most hosting, nobody has done them. They are left to a plugin, or to you, or to nobody.
Why we do it at the server level
You could chase most of this with plugins. The problem is that plugin-based performance is fragile. A plugin update changes a setting, two caching plugins fight each other, and suddenly your fast site is slow again and you do not know why. When the tuning lives in the server, it does not break when you update a plugin, and it is the same on every Forge site we run.
The result is a site that loads in well under a second on a warm cache, holds that speed when traffic arrives, and does not need you to become a performance engineer to keep it there.
If your current host has left you fighting your own speed, we will move your site for free and tune it properly on the way in. You can see what is included on every plan on our pricing page.
