Hostinger WordPress PageSpeed Score: How to Hit 90+ on Mobile

Google PageSpeed Insights scores your site on three Core Web Vitals that directly impact SEO rankings:

• LCP (Largest Contentful Paint): How fast the main content element loads. Target: under 2.5 seconds.
• INP (Interaction to Next Paint): How fast the page responds to user clicks/taps. Target: under 200ms.
• CLS (Cumulative Layout Shift): How much elements shift during page load. Target: under 0.1.

Fresh WordPress on Hostinger Business (Astra theme, no plugins): 95-98 PageSpeed mobile. After adding a page builder, 15 plugins, and unoptimized images: typically drops to 55-70. The following steps bring you back above 90.

LCP is usually the hero image or largest text block. On Hostinger WordPress, optimize LCP with:

1. Preload the hero image: LiteSpeed Cache → Page Optimization → Preload → add the URL of your above-the-fold hero image. This tells the browser to fetch it immediately instead of waiting for CSS parsing.
2. Use WebP images: LiteSpeed Cache → Image Optimization → WebP Replacement. WebP images are 25-35% smaller than JPEG/PNG, loading the LCP element faster.
3. Enable Hostinger CDN: Serve images from CDN edge locations (200+ global PoPs) rather than your origin server.
4. Remove unused CSS above the fold: LiteSpeed Cache → Page Optimization → Load CSS Asynchronously + Generate Critical CSS. This loads only the CSS needed for above-fold content first.

These four changes typically reduce LCP from 3-4 seconds to under 2 seconds on Hostinger.

INP measures how fast your page responds when a user clicks a button, link, or form field. High INP is caused by JavaScript blocking the main thread.

• Defer JavaScript: LiteSpeed Cache → Page Optimization → JS Defer → Enable. Moves non-critical JS execution to after page load.
• Remove unused plugins: Each plugin adds JavaScript. Audit your plugins and remove anything unused. Common offenders: social sharing plugins, analytics plugins loading multiple trackers, and page builder frontend scripts.
• Reduce DOM size: Page builders generate massive DOM trees (10,000+ nodes). Simplify layouts, reduce nested containers, and prefer native WordPress blocks over page builder alternatives.
• Use Delay JS: LiteSpeed Cache → Page Optimization → JS Delayed → add non-essential scripts (analytics, chat widgets, social embeds) to delay until user interaction.

CLS happens when elements shift position during load — images without dimensions, late-loading fonts, and dynamic ad containers are the usual causes.

• Set image dimensions: Always include width and height attributes on <img> tags. WordPress does this by default for uploaded images. Check your theme's custom image elements.
• Preload fonts: LiteSpeed Cache → Page Optimization → Preload → add your theme's font files. This prevents font-swap-induced layout shift.
• Reserve space for ads: If running ads, use CSS min-height on ad containers to reserve space before the ad loads.
• Avoid injecting content above the fold: Cookie banners, notification bars, and pop-ups that push content down cause CLS. Use slide-in or overlay patterns instead.

After each optimization, measure the impact:

• Google PageSpeed Insights: pagespeed.web.dev — the definitive test. Run on both mobile and desktop.
• GTmetrix: More detailed waterfall analysis. Shows exactly which resources are slow.
• Chrome DevTools Lighthouse: DevTools → Lighthouse tab → Generate report. Runs locally for faster iteration.
• Google Search Console: Core Web Vitals report shows real-user data (CrUX data) for your site. This is what Google actually uses for rankings.

Lab scores (PageSpeed Insights, Lighthouse) may differ from field data (Search Console). Optimize for field data — that's what real users and Google experience.