WordPress Speed Optimization on Hostinger 2026 —
What Actually Moved My PageSpeed Scores

Why Speed Matters More Than You Think

When I first set up WordPress on Hostinger, my PageSpeed desktop score was 64. Not terrible, but not good. After 6 weeks of optimizations, it was 95. The practical difference: my pages went from 2.3 second average load time to 1.1 seconds. This coincided with a meaningful improvement in Google rankings for several of my target keywords.

I can't prove the rankings improved specifically because of speed — there are too many variables in SEO to isolate single factors. But the correlation was there, and Google has been explicit that Core Web Vitals (which speed affects directly) are a ranking signal. For an affiliate site where rankings directly affect income, this optimization was worth every minute I put into it.

Before You Start — Check Your Baseline

Go to pagespeed.web.dev, enter your homepage URL, and run the test. Screenshot both mobile and desktop scores. This is your baseline — you'll compare everything against it. Run the test 2-3 times and average the scores, as PageSpeed results vary by 3-5 points between runs on the same unchanged page.

Step 1 — Install LiteSpeed Cache (Biggest Impact)

This single step improved my PageSpeed score by 18 points. Hostinger uses LiteSpeed servers, and LiteSpeed Cache is a plugin designed specifically for these servers — the caching happens at the server level, not just in PHP, which makes it dramatically faster than generic caching plugins like W3 Total Cache.

Before LiteSpeed Cache: PageSpeed Desktop 64, Mobile 47
After LiteSpeed Cache (default settings): Desktop 79, Mobile 61
After LiteSpeed Cache (optimized settings): Desktop 91, Mobile 78

Step 2 — LiteSpeed Cache Settings That Matter

In the LiteSpeed Cache plugin settings, these specific toggles made measurable differences:

• Cache → Enable Cache: ON — this is the main caching function. Without it everything else is irrelevant.
• Image Optimization → WebP Replacement: ON — converts images to WebP format (25-35% smaller than JPEG at same quality). My page weight dropped by 380KB from this alone.
• Image Optimization → Lazy Load Images: ON — images below the fold don't load until the visitor scrolls to them. Significantly improves initial page load time.
• Minify → Minify CSS: ON — removes whitespace and comments from CSS files. Small improvement but costs nothing to enable.
• Minify → Minify JS: ON — but test your site after enabling. Some themes and plugins break with JS minification. If anything looks wrong, disable this one.
• Minify → Combine CSS: I leave this OFF — combining CSS files can break theme layouts on some WordPress setups.

Step 3 — Change to PHP 8.2 in hPanel

PHP 8.2 executes code measurably faster than PHP 7.4 or 8.0. On my test site, switching from PHP 7.4 to 8.2 reduced Time to First Byte from 340ms to 210ms — a 38% improvement in server response time.

In hPanel → Website → PHP Configuration → select PHP 8.2 → Save. Then immediately open your site in a browser and test several pages. If anything breaks — plugin conflicts are the main risk — switch back to PHP 8.1 or 8.0. Most modern WordPress plugins support 8.2, but some older ones don't.

Step 4 — Switch to Astra Theme (If You Haven't Already)

Theme choice has a larger impact on PageSpeed than most people expect. Heavy themes with elaborate animations and large CSS frameworks add 200-400KB to every page load. Astra adds under 50KB.

I moved one of my sites from a popular premium theme to Astra and PageSpeed desktop went from 71 to 88 in a single change — with nothing else modified. That's a 17-point improvement just from the theme. If you're on a heavy theme, consider whether the design benefits justify the performance cost. You can make Astra look professional with minimal customization — the default is clean and fast. This is especially important for a WordPress site competing in a crowded niche.

Step 5 — Optimize Your Images Before Uploading

LiteSpeed Cache's WebP conversion helps, but images that are already oversized before conversion still cause issues. My rule of thumb:

• Featured images: maximum 1200px wide, 150KB maximum file size
• In-content images: maximum 800px wide, 80KB maximum
• Use Squoosh.app (free, browser-based) to compress images before uploading — it shows you the file size reduction in real time

After adopting this habit across all new uploads, my average page weight dropped from 1.8MB to 420KB. That's a 77% reduction in data transferred per page view — meaningful for mobile visitors on slower connections.

Step 6 — Remove Unused Plugins

Every active plugin runs code on every page load. I audited my plugin list and found I had 6 plugins installed that I wasn't actively using. Removing them took PageSpeed from 91 to 95 on desktop. It's a small gain per plugin but adds up. My current rule: keep active plugins under 12, never install something "just to try it" without being willing to remove it promptly.

Full Before/After Summary

Advanced Optimization — Beyond the Basics

The steps I covered earlier get most sites from 64 to 91+ on PageSpeed. If you want to push further — into 95+ territory — these additional optimizations make incremental but real differences.

Google Fonts — Host Them Locally

Themes that use Google Fonts make a request to Google's servers on every page load. This external request adds latency — typically 200-400ms — to your page load time. LiteSpeed Cache has a built-in option to download Google Fonts and serve them locally from your own server, eliminating this external request. In LiteSpeed Cache → Page Optimization → CSS Settings → find "Google Fonts" → enable "Load Google Fonts Locally." This single change improved my PageSpeed score by 3 points on one site where Google Fonts was the main remaining bottleneck.

Eliminate Render-Blocking Resources

Render-blocking resources are CSS and JavaScript files that prevent the page from displaying until they finish loading. PageSpeed Insights reports these specifically under "Eliminate render-blocking resources." LiteSpeed Cache's "Defer JS" setting delays non-critical JavaScript until after the main content loads. This directly improves Largest Contentful Paint (LCP) — one of the Core Web Vitals metrics Google uses for ranking. Enable it in LiteSpeed Cache → Page Optimization → JS Settings → check "Load JS Deferred."

Preload Critical Resources

For resources that are essential for the first visible page content (your hero image, primary font, main CSS), preloading tells the browser to fetch them immediately rather than waiting to discover them during page parsing. In LiteSpeed Cache → Page Optimization → CSS Settings → enable "Critical CSS" — LiteSpeed analyzes your page and generates inline CSS for the above-fold content, making it appear before the main stylesheet finishes loading.

Database Optimization

WordPress databases accumulate overhead over time — post revisions, deleted content, expired transients, spam comments. This database bloat slows queries that WordPress runs on every page load. LiteSpeed Cache includes a database optimizer: go to LiteSpeed Cache → DB Optimizer → run the optimization. On an active blog with 100+ posts, this can reduce database size by 20-40% and meaningfully improve Time to First Byte. I run this monthly.

Testing Your Optimization — The Right Approach

One mistake I made early: I changed multiple settings at once and couldn't identify what helped. The correct approach:

1. Run PageSpeed Insights and screenshot the baseline score
2. Make one change
3. Run PageSpeed Insights again (3 times, take the average — scores vary by 3-5 points between runs)
4. Record the delta
5. Repeat for the next change

This methodical approach takes longer but gives you actionable data. You know exactly what each change contributed. When I shared my site's before/after data with Hostinger support once, the agent immediately identified that my Google Fonts were the biggest remaining bottleneck — which I'd missed by looking at the aggregate score rather than the detailed recommendations.

Core Web Vitals — What Google Actually Measures in 2026

Google has updated the Core Web Vitals metrics over time. As of 2026, the three metrics that matter for ranking are:

• LCP (Largest Contentful Paint): How quickly the largest visible element loads — usually your hero image or main header. Target: under 2.5 seconds. My Hostinger sites average 1.4s.
• CLS (Cumulative Layout Shift): How much the page layout jumps around while loading. Target: under 0.1. Common causes: images without specified dimensions, ads that load late and push content down. My CLS is consistently 0.02-0.04.
• INP (Interaction to Next Paint): Replaced FID in 2024. Measures how quickly the page responds to user interaction — clicking a button, selecting text. Target: under 200ms. JavaScript-heavy sites with many plugins tend to struggle here.

To check your Core Web Vitals: Google Search Console → Experience → Core Web Vitals. This shows real-world data from actual Chrome users visiting your site, which is more accurate than synthetic tests like PageSpeed Insights. Aim for all three in the "Good" range.

Quick Reference — Summary and Next Steps

Before you close this article, here are the most important points worth remembering, plus concrete next steps based on where you are in building your site.

If You're Just Getting Started

The single most important decision at the beginning is your hosting foundation. Fast hosting (Hostinger's LiteSpeed servers) gives you a speed advantage that compounds over time — better Core Web Vitals mean better rankings, which means more traffic, which means more affiliate commissions and AdSense revenue. Choosing cheap slow hosting to save $1/month costs you far more in ranking potential than it saves in fees.

Get started on Hostinger Premium — it includes everything you need: fast LiteSpeed servers, free domain, free SSL, professional email, 100 websites, and 24/7 support. Install WordPress using the one-click installer in hPanel. Then focus entirely on content for the first 6 weeks — 2-3 quality articles per week targeting specific keywords your audience searches for. The technical setup matters, but content is what Google actually ranks.

If You're Already Publishing and Want to Accelerate Growth

At this stage, the leverage points are: internal linking (connecting new articles to existing ones distributes ranking authority across your site), content updates (Google rewards freshly updated content — revisit your top-performing articles every 3-6 months and improve them), and keyword expansion (identify which articles are ranking on pages 2-3 and improve them specifically to reach page 1).

Review your Google Search Console data weekly. The "Queries" report shows exactly which keywords are bringing impressions — these are your best clues for what content to write next and which existing articles to strengthen. A page getting 500 impressions but only 5 clicks (1% CTR) has something wrong — usually a title or meta description that doesn't match search intent. Fixing that one thing can double your traffic from that keyword without writing a new article.

If You're Waiting for AdSense Approval

While AdSense reviews your site, keep publishing. More indexed content means a better overall quality signal. Make sure your About page clearly identifies you as a real person with real experience — AdSense reviewers specifically check this. Ensure all four required pages (About, Contact, Privacy Policy, Disclaimer) are complete, properly written, and linked from every page's navigation.

The common reasons AdSense rejects sites in 2026: insufficient original content, author identity unclear, required pages missing or thin, site too new (under 4-6 weeks), or content that appears AI-generated without genuine personal expertise. Address whichever of these applies to your situation before requesting review.

Recommended Reading on HostLaunch

If this article was useful, these related guides on HostLaunch.online cover connected topics in depth:

• Hostinger Review 2026 — My complete 3-year assessment with real data, honest weaknesses, and who it's best suited for
• Best WordPress Hosting 2026 — 7 hosts tested simultaneously for 6 months, real comparative data
• How to Start a Blog in 2026 — The complete guide from niche selection to first commission, including what I'd do differently
• About Tabid — Who I am, how I test hosting, and why I write about this topic specifically

Questions about anything covered here? Use the contact page — I read every message and reply to most of them within 48 hours.