LiteSpeed Cache Setup Guide for WordPress on SNBD HOST

LiteSpeed Cache is not just another caching plugin. When your WordPress site runs on a LiteSpeed web server — as SNBD HOST's hosting plans do — LiteSpeed Cache communicates directly with the server to cache pages at the server level. That's fundamentally faster than plugins that cache pages at the PHP level. The result: your pages are served before PHP even runs, cutting typical load times from 800-1500ms down to 50-200ms for cached pages.

But the plugin needs proper configuration to realize that potential. The default settings are conservative. This guide walks through the full setup, section by section, with the specific settings that work well on SNBD HOST's infrastructure.

Installation

If you haven't installed LiteSpeed Cache yet:

1. Go to WordPress Dashboard → Plugins → Add New
2. Search for "LiteSpeed Cache"
3. Install and activate the plugin by LiteSpeed Technologies (it's the official plugin, not a third party)

After activation, you'll see a new LiteSpeed Cache menu in your WordPress sidebar. The plugin detects whether it's running on a LiteSpeed server automatically — if you're on SNBD HOST's BDIX shared hosting, it will confirm server-level caching is available.

Dashboard Overview

The LiteSpeed Cache dashboard shows you key metrics: cache hit rate, saved bandwidth, and image optimization status. Initially all zeros — they'll fill in as traffic comes in. Your target cache hit rate once the site is running is 80%+ for a typical blog or business site.

Cache Settings

Go to LiteSpeed Cache → Cache → Cache.

Enable the following:

• Enable Cache: ON — the master switch
• Cache Logged-in Users: OFF for most sites. Logged-in users (admins, members) see personalized content that shouldn't be cached.
• Cache Commenters: OFF unless you have a high-traffic comment section
• Cache REST API: ON — speeds up REST API responses used by Gutenberg blocks and many plugins
• Cache Login Page: ON — the login page itself is static
• Cache favicon.ico: ON
• Cache PHP Resources: ON

Under the TTL tab, set Default Public Cache TTL to 604800 (one week in seconds). Pages that don't change often should stay cached for a long time. WordPress automatically purges cached pages when you update content.

Cache Purge Settings

Go to LiteSpeed Cache → Cache → Purge.

Enable Auto Purge Rules for Publish/Update and check:

• Purge All on Upgrade: ON
• Auto Purge Rules: Enable purging the home page and relevant category pages when a post is published

This ensures stale content is cleared automatically when you update your site.

Excludes

Go to LiteSpeed Cache → Cache → Excludes.

If you're running WooCommerce, add these to the Do Not Cache URIs list:

/cart
/checkout
/my-account
/wc-api

Cart and checkout pages are user-specific and must not be cached. LiteSpeed Cache's WooCommerce integration handles most of this automatically, but it's good to verify these are in the exclude list.

Image Optimization (QUIC.cloud)

Go to LiteSpeed Cache → Image Optimization.

LiteSpeed Cache uses QUIC.cloud (LiteSpeed's CDN/optimization service) for image compression and WebP conversion. You get 5,000 image optimizations per month free.

Steps:

1. Click Request Domain Key — this links your site to QUIC.cloud (free account)
2. Once the key arrives (takes a few seconds to a few minutes), go to Image Optimization → Image Optimization Settings
3. Enable Auto Request Cron: ON — automatically sends new images for optimization
4. Enable Auto Pull Cron: ON — automatically pulls optimized images back to your server
5. Enable WebP Replacement: ON — serves WebP to browsers that support it (Chrome, Firefox, Edge, Samsung Internet)
6. Set Lossy JPEG: ON with quality 85 — good balance of file size and quality
7. Click Send Unoptimized Images to queue your existing media library for optimization

WebP images are typically 30-50% smaller than JPEG at equivalent quality. For a site with many product or portfolio photos, this alone can cut your page weight significantly.

Page Optimization

Go to LiteSpeed Cache → Page Optimization.

This section minifies and combines CSS and JavaScript files. The settings below work for most WordPress sites, but if something breaks on your site after enabling, try disabling one setting at a time to find the culprit.

CSS Settings

• CSS Minify: ON — removes whitespace and comments from CSS files
• CSS Combine: ON — merges multiple CSS files into one, reducing HTTP requests
• CSS Combine External and Inline: Leave OFF initially — can cause issues with some themes
• UCSS (Used CSS): ON — generates per-page CSS containing only the styles actually used on that page. This is a significant optimization for sites with large CSS frameworks. Uses QUIC.cloud credits.
• Critical CSS (CCSS): ON if your PageSpeed score shows render-blocking CSS as an issue

JavaScript Settings

• JS Minify: ON
• JS Combine: ON — fewer HTTP requests
• JS Deferred Loading: ON — defers non-critical JavaScript from blocking page rendering. This typically provides the biggest improvement in Time to Interactive scores.

After enabling these, open your site in a private browser window (to see it uncached) and click through several pages. Check that navigation works, forms submit correctly, and any interactive elements function. If you see issues, disable JS Combine first as it's most likely to cause conflicts with complex plugins.

Browser Cache

Go to LiteSpeed Cache → Page Optimization → Browser.

• Browser Cache: ON — tells visitors' browsers to cache static files (images, CSS, JS) locally so they don't re-download on subsequent visits
• Browser Cache TTL: 31557600 (one year for static assets)

This dramatically speeds up repeat visits from the same user. First visit downloads everything; second visit loads instantly from local cache.

Object Cache

Go to LiteSpeed Cache → Cache → Object.

Object caching stores the results of database queries in memory so they don't need to be re-run for every page view. If SNBD HOST has Memcached or Redis available on your plan, enable Object Cache here and connect it.

Contact SNBD HOST support to ask whether Memcached is available on your plan. If it is, they'll provide the connection details. Object cache makes a meaningful difference for database-heavy sites like WooCommerce stores.

CDN Settings

Go to LiteSpeed Cache → CDN.

QUIC.cloud offers a free CDN tier. For Bangladesh sites primarily serving local visitors, a CDN adds less value than the server-level caching already provided by LiteSpeed — but it still helps for serving static assets (images, CSS, JS) faster.

If you have international traffic or want to use QUIC.cloud's additional features (online CSS, online JS minification), set up the CDN by following the QUIC.cloud setup wizard under LiteSpeed Cache → Dashboard → CDN Setup.

Checking Your Results

After configuring everything, test your site speed at:

• Google PageSpeed Insights (pagespeed.web.dev) — tests both mobile and desktop, gives specific improvement suggestions
• GTmetrix (gtmetrix.com) — more detailed waterfall breakdown
• WebPageTest (webpagetest.org) — test from a Dhaka server to see what local visitors actually experience

A well-configured WordPress site on SNBD HOST with LiteSpeed Cache should score 85+ on PageSpeed Insights and load in under 2 seconds on the first visit, under 1 second on repeat visits.

If you're not hitting those numbers, look at the PageSpeed Insights "Opportunities" section for specific items to address. Common remaining issues are: unoptimized images (the QUIC.cloud optimizer handles this), render-blocking third-party scripts (like Google Analytics — load these asynchronously), and unminified JavaScript from themes.

Maintenance

LiteSpeed Cache is largely set-and-forget once configured. The main ongoing task is purging the cache when you make significant design changes (use LiteSpeed Cache → Toolbox → Purge All). Content updates purge relevant pages automatically.

Check the Image Optimization section monthly to process any new images added to your media library. If you go over the free QUIC.cloud monthly quota, optimization pauses until the next month or until you upgrade to a paid QUIC.cloud plan.