Speed Up WordPress on Hostinger (2026)

Hostinger runs LiteSpeed web servers, which is genuinely good news for WordPress speed — LiteSpeed’s free cache plugin can make a basic site load in under a second. But the server is only half the story. Most slow WordPress sites are slow because of unoptimized images, plugin bloat, and missing caching, all of which you can fix in an afternoon with no coding.

This guide walks through the five steps that matter, in order of impact: LiteSpeed Cache configuration, image optimization, a CDN, cutting dead weight, and PHP/database tuning. Do all five and measure before and after — the difference is usually dramatic.

Step 0: Measure first

Run your homepage through PageSpeed Insights (Google’s free tool) and note the mobile and desktop scores plus the LCP (Largest Contentful Paint) time. Screenshot it. You need a “before” number or you will never know what worked.

Step 1: Set up LiteSpeed Cache properly

LiteSpeed Cache is free in the WordPress plugin directory and talks directly to Hostinger’s LiteSpeed servers — that direct line is why it beats generic caching plugins here.

1. Install and activate LiteSpeed Cache from Plugins → Add New.
2. Apply a preset. Go to LiteSpeed Cache → Presets and apply the Advanced preset. It enables page caching, browser caching, and sensible defaults in one click. (The Simple preset is too timid; the aggressive ones can break layouts on complex sites.)
3. Enable page cache. Under Cache settings, confirm Cache is ON. This stores a static HTML copy of each page so PHP and the database are skipped for most visitors.
4. Enable browser caching. Set a long TTL for static resources (images, CSS, JS) so returning visitors barely download anything.
5. Turn on lazy loading. Under Page Optimization → Media Settings, enable Lazy Load Images. Below-the-fold images then load only when scrolled to — this alone can halve initial page weight.
6. Generate Critical CSS (CCSS). Under Page Optimization, enable CCSS generation. It inlines the CSS needed for above-the-fold content so the page paints faster. If your layout breaks, regenerate or disable it — this is the one setting most likely to need tuning per theme.
7. Connect object cache if available. If your plan includes object caching, enable it under Cache → Object and select the available method. (Our Redis object cache guide covers this in depth.)

After configuring, purge the cache once (top admin bar → Purge All) and re-test in an incognito window — admins often see uncached pages, which makes the plugin look like it is doing nothing.

Step 2: Optimize your images

Images are the #1 cause of slow WordPress sites. A single 4 MB phone photo in a hero banner can outweigh the entire rest of the page.

1. Resize before uploading. If your content area is 800 px wide, a 4000 px image is pure waste. Resize to the display size (2x at most for retina).
2. Convert to WebP. LiteSpeed Cache → Image Optimization can convert your library to WebP, which is typically 25–35% smaller than JPEG at the same quality. Run it once on the existing library; new uploads convert automatically.
3. Compress. The same Image Optimization screen offers lossy compression. “Lossy” sounds scary but at the default settings the visual difference is invisible while the savings are real.
4. Lazy-load everything below the fold (enabled in Step 1) — and consider lazy-loading iframes/embeds too, since YouTube embeds are heavy.

Step 3: Put a CDN in front

A CDN serves your static files from servers near each visitor instead of from Hostinger’s data center alone. Two free options:

• QUIC.cloud CDN — built by the LiteSpeed team, integrates with the LiteSpeed Cache plugin in a few clicks, and has a free tier generous enough for most blogs and small business sites.
• Cloudflare (free plan) — change your nameservers to Cloudflare’s, and it caches static assets globally plus adds a layer of security. Slightly more setup, very mature.

Either one typically shaves 0.3–1 second off load times for distant visitors. If your audience is mostly in one country, pick the Hostinger data center closest to them at signup and treat the CDN as a bonus rather than a necessity.

Step 4: Cut the dead weight

Every active plugin adds code that runs on (or around) every page load. Audit ruthlessly:

• Deactivate and delete anything you do not actively use. Deleted beats deactivated — deactivated plugins can still be a security liability.
• Replace heavy multipurpose plugins with lighter single-purpose ones where practical. Two plugins doing overlapping jobs (e.g., two SEO plugins, two security plugins) is pure overhead.
• Watch page builders. Elementor/Divi-style builders are convenient but heavy. If you use one, keep it to pages that need it and use the block editor elsewhere.
• Limit external scripts. Chat widgets, social feeds, and ad scripts each add DNS lookups and downloads you do not control. Keep only the ones earning their keep.
• Pick a lightweight theme. If you are still choosing, a lean block theme will always beat a feature-stuffed multipurpose theme on speed.

Step 5: PHP and database tuning

1. Use the newest PHP your site supports. In hPanel → Advanced → PHP Configuration, select the latest stable PHP version (8.x). Each major PHP release has been measurably faster than the last. Test the site after switching; a very old plugin may complain.
2. Clean the database. LiteSpeed Cache → Database has a one-click optimizer for post revisions, trashed posts, expired transients, and spam comments. Run it monthly.
3. Limit post revisions. WordPress saves unlimited revisions by default. Cap them (e.g., 5) via wp-config.php or the database settings — old revisions bloat the database on long-lived sites.
4. Schedule regular cache purges. If you publish often, set sensible cache TTLs so new content appears promptly without manual purges.

Measure again and keep a routine

Re-run PageSpeed Insights on the same pages. Typical results from all five steps: mobile scores jumping 20–40 points and LCP dropping by a second or more. Speed is maintenance, not a one-time project — re-check quarterly, after theme changes, and whenever you add a new plugin.

Frequently asked questions

Is LiteSpeed Cache enough, or do I need a paid speed plugin?

For most sites on Hostinger, the free LiteSpeed Cache plugin — properly configured — outperforms paid generic caching plugins, because it communicates directly with the LiteSpeed server. Paid plugins mainly add convenience features, not fundamentally better caching on this stack.

Will a CDN help if my visitors are all in one country?

Somewhat, but less dramatically. If your audience is local, choosing the nearest Hostinger data center at signup matters more. A CDN still helps with traffic spikes and adds a security layer, so it is worth enabling — just expect modest gains rather than miraculous ones.

Why is my site still slow after enabling caching?

The usual suspects: you tested while logged in (admins bypass cache — test incognito), Critical CSS broke the layout and you disabled everything in frustration (re-enable selectively), or one heavy plugin/script dominates load time (check the PageSpeed “diagnostics” section to find it).

Does upgrading my Hostinger plan make WordPress faster?

It can, mainly through more resources (RAM, CPU) and features like object caching on higher tiers — but a bloated site stays slow on any plan. Optimize first; upgrade when optimization shows the server itself is the bottleneck (high Time to First Byte even on cached pages).