You enabled optimization features in LiteSpeed Cache for WordPress, and now your site is broken. Let’s find the CSS or JS file that’s causing the problem!
LiteSpeed Cache Security Patches
February 28th, 2024Last October we released two security patches to address reported vulnerabilities in LiteSpeed Cache for WordPress.
Read More
Server Improvements Under the Hood
January 8th, 2024LiteSpeed Web Server and LiteSpeed Web ADC both got significant updates at the end of 2023. Let’s look under the hood to see how these new …
Read More
Performance Testing Namespaces
February 21st, 2024Namespaces in Linux are often used to implement containers and are great at administering sandboxes where files, users, processes and just about all system resources are …
Read More
QCRAM-04 addresses the deadlock hazard, but is unable to minimize HoLB for a certain class of applications. Learn more.
LiteSpeed Cache for WordPress allows you to do simple cache management from the browser’s URL bar, if you are logged in from a known Admin IP address.
A WordPress site specializing in printable birthday cards and invitations needed a way to maximize their performance without introducing 3rd-party-plugin conflicts. See how they did it with LSCache!
One way to prevent attack is to not read from the stream until the decoder can process the stream immediately. This approach creates a deadlock hazard and is examined in this article.
You now have the ability to manage certain aspects of your Cloudflare cache from within the LiteSpeed Cache for WordPress plugin.
Compression schemes that allow head-of-line blocking are targets for memory exhaustion attacks against the decoder. One way to avoid an attack is presented.
One area in which you have the power to reduce user-perceived latency is DNS resolution. Use the new DNS Prefetch setting in LSCache.
Head-of-line blocking causes priority inversion and vice versa. Learn more.