Hostinger ships with LiteSpeed servers and a pre-installed LiteSpeed Cache plugin, which already puts most WordPress sites ahead of stock shared hosting. The catch: the defaults are conservative, the hPanel toggles that actually move PageSpeed scores are spread across four different menus, and the most useful feature for logged-in WooCommerce or membership sites (Object Cache) is off by default. This guide walks through every Hostinger-specific lever, in the order they pay off, with the gotchas that catch most teams.
What This Guide Covers
Three things, in this order: (1) how the Hostinger LiteSpeed stack actually caches a request and why that matters for what you tune next, (2) the hPanel toggles that move numbers (PHP version, OPcache, Brotli, Object Cache, CDN), and (3) the boundary where Hostinger's shared plans stop scaling and you need to move to Business, Cloud, or off the platform entirely. For first-time setup or migration steps, start with the Hostinger setup and migration guide. For the full provider overview and pricing, see the Hostinger hosting guide.
Run a Performance Baseline Before You Change Anything
Optimization without a baseline is guessing. Before you toggle a single hPanel setting, capture three numbers from a tool like PageSpeed Insights or GTmetrix, run from a location near Hostinger's data centre you actually use:
- Time to First Byte (TTFB): under 500ms on an uncached request is your goal on a shared plan. If you start at 1,500ms, no caching plugin will fix it; the problem is upstream.
- Largest Contentful Paint (LCP): the headline Core Web Vital. Most Hostinger sites that "feel slow" are LCP-bound, not TTFB-bound.
- Total page weight: if your homepage is over 3MB, fix images and fonts first. Caching shaves milliseconds; deleting 2MB of unused JS shaves seconds.
Run each test three times in incognito and take the median. Save the report. You will want to compare against it after every change.
How the Hostinger LiteSpeed Stack Actually Caches
Hostinger runs LiteSpeed Web Server (LSWS) instead of Apache or Nginx, which is why the stack feels different from a typical cPanel host. LSWS has a built-in page cache that the LiteSpeed Cache (LSCWP) plugin controls from inside WordPress. There are three layers worth understanding:
- Server-level page cache: LSWS stores fully-rendered HTML for guest visitors. Hit ratios on cacheable pages run 90%+ once warmed.
- Browser cache: LSCWP sets long expiry headers on static assets. Already on by default.
- Object cache (LSMCD): caches database query results in memory. Off by default. This is the one that matters for logged-in users.
The first two are automatic. The third is where most speed gains live for sites with carts, member areas, or admin-heavy editors.
Enable Object Cache via hPanel
Object Cache (LSMCD, the LiteSpeed Memcached daemon) is enabled per-site, not server-wide. In hPanel, open the site's WordPress → Overview panel and toggle Object Cache on. Hostinger's own docs cite about a 10% response-time improvement on cached queries, but the real lift is for non-cacheable pages: WooCommerce checkout, BuddyPress feeds, LearnDash dashboards, anything that hits the database on every load.
Two gotchas. First, LSCWP must be installed and active for the toggle to do anything; if you swapped to WP Rocket or W3 Total Cache, you lose Object Cache. Second, certain plugins (especially older membership and forum plugins) write directly to the database without flushing the object cache, which can show stale data. Test thoroughly after enabling.
Turn On Hostinger CDN (and the Plan-Tier Catch)
Hostinger CDN is included on Business Web Hosting and above. On the Premium plan, the toggle is greyed out. If you are on Premium and want a CDN, your options are Cloudflare (free, manual setup) or QUIC.cloud (free tier, built to pair with LiteSpeed Cache).
If you are on Business or Cloud, enable it in hPanel under Website → Performance → CDN. After enabling, purge the LiteSpeed cache once and re-test. Expect LCP improvements of 200ms to 600ms for visitors more than 1,000 km from your data centre. Visitors near the data centre will see little change; the CDN's value is geographic.
QUIC.cloud as a Free Alternative
QUIC.cloud is the CDN built by the LiteSpeed team and integrates with LSCWP via a CNAME on your domain's DNS Zone Editor in hPanel. The free tier covers the first 20GB per month, which is enough for most small business sites. It also unlocks page-level optimisations LSCWP cannot do alone: critical CSS generation, image WebP conversion at the edge, and UCSS (Unique CSS) per page. Set it up only if you are on Premium without Hostinger CDN, or if you want the LiteSpeed-native optimisations even on Business plans.
PHP Version, OPcache, and Brotli
Three settings in hPanel Advanced → PHP Configuration that move numbers fast:
- PHP version: use PHP 8.2 or 8.3. The jump from PHP 7.4 to 8.x is typically a 15-25% throughput gain on real WordPress workloads. Verify your theme and plugins are PHP 8-compatible first (most modern ones are).
- OPcache: caches compiled PHP bytecode in memory. Enable it. There is no real downside on a production site.
- Brotli compression: a better-compressing successor to Gzip. Enable it. Browsers that do not support Brotli fall back to Gzip automatically.
While you are in PHP Extensions, disable XML-RPC if nothing on your site uses it (no Jetpack mobile app, no remote publishing, no Pingbacks). XML-RPC is a perennial brute-force target and disabling it removes one attack surface and one source of background load.
Image Optimization Beyond LSCWP Defaults
LSCWP's image optimisation runs through QUIC.cloud's queue and converts to WebP. It works, but it is a queue, which means new uploads can sit for an hour before being processed. For a site that publishes frequently, pair it with a local compressor (ShortPixel, Imagify, or the Hostinger-recommended Smush) that compresses on upload, then let LSCWP serve the WebP version once QUIC.cloud has cached it. Set the upload size limit on your theme's image sizes; many themes generate 6-10 image sizes per upload, most of which are never used.
Database Cleanup via phpMyAdmin
Open hPanel Databases → phpMyAdmin for the site, then optimise tables from the SQL tab. A practical safer path: install WP-Optimize, set it to a monthly schedule, and let it delete post revisions, auto-drafts, transients, and spam comments on its own. Sites that have been running for two years can easily carry 200MB of revision bloat that slows every admin query.
When Hostinger Isn't Fast Enough
There is a real ceiling on shared LSWS plans. If your TTFB stays above 1 second after every toggle in this guide, and your tests are running on a warm cache, the bottleneck is CPU and I/O contention with other tenants on your server. Three escalation paths:
- Upgrade to Business Web Hosting for the Hostinger CDN, more CPU, and Object Cache headroom. Reasonable for a busy WooCommerce site under 50,000 monthly visitors.
- Move to Hostinger Cloud Hosting for dedicated resources. Worth it if your peak concurrent users are in the hundreds.
- Move off Hostinger to a managed WordPress host. Read the Hostinger review for an honest read on where the limits are, then consider Cloudways for VPS-grade performance at a similar price point, or Kinsta for a fully-managed alternative.
If you are not at the ceiling yet but planning ahead, the migrate WordPress to Hostinger guide covers what a clean cutover looks like, and the same DNS-cutover pattern works in reverse if you ever leave.
Common Cache and CDN Gotchas
Three failures that happen on Hostinger more than people admit:
- Two caching plugins active at once. If you installed WP Rocket on top of LSCWP, disable one. Two cache plugins serving the same page is the fastest way to break a site silently.
- CDN purge not flushing LSCWP. When you publish a new post, LSCWP purges the local server cache automatically, but you may need to purge Hostinger CDN or QUIC.cloud from their respective panels.
- Logged-in users seeing cached pages. If admin bars look stale or carts show wrong totals, your cache exclusion rules are wrong. LSCWP's "Do Not Cache" settings need
/cart,/checkout,/my-account, and/wp-adminexcluded for WooCommerce.
Run your baseline tests again after every two or three changes, not at the end. It is easier to back out one bad setting than to debug five at once. When the page is ready to go live, head to the Hostinger setup guide for the launch checklist, then come back here to keep tuning. To get started on a plan that supports CDN and Object Cache without limits, grab a Hostinger Business or Cloud plan.