# Slow Hostinger site? Diagnose it first, then apply these 9 fixes URL: https://www.savemores.store/guides/speed-up-slow-hostinger-site Author: Mr. Ahmed · Published 2026-10-18 · Updated 2026-10-18 · Fixes & support ## Short answer - Start by measuring Time to First Byte and Largest Contentful Paint in Google PageSpeed Insights; they tell you whether the server or the page is slow. - The biggest single WordPress speed-up on Hostinger is the LiteSpeed Cache plugin with page caching on, and only one page-cache plugin active. - Premium and higher plans include Hostinger's CDN at no extra cost. - Oversized images are the most common cause of a slow-feeling page; resize them and convert to WebP. - If hPanel shows you regularly hitting CPU, memory or process limits after optimizing, upgrade to Business or Cloud Startup. ## Measure before you touch anything Put your homepage and one ordinary post through Google PageSpeed Insights. Write down two figures: **Time to First Byte** (how long the server takes to answer) and **Largest Contentful Paint** (when the main content shows up). Those two numbers split the problem in half. Use the table to decide which fixes to start with, instead of trying all nine at random. | Symptom | Where the cause usually is | Fixes to try first | | --- | --- | --- | | Slow first byte | Server side: caching, PHP, resource limits, distance | 1, 3, 6, 7, 9 | | Fast first byte, slow LCP | The page itself: images, theme, plugins | 4, 5, 8 | | Slow only for distant visitors | Distance to the data center | 2, 9 | > From the bench: Change one thing at a time and re-measure. If you change five things and the site gets faster, you don't know which one mattered, and if it breaks, you don't know which one to undo. ## 1. LiteSpeed Cache: turn it on, and keep it alone **Symptom:** slow first byte on every page. **Cause:** pages are being built from scratch on each request. **Fix:** Hostinger runs LiteSpeed web servers, and the LiteSpeed Cache plugin talks to the server cache directly. It is the largest single gain for WordPress, and Hostinger usually installs it for you. Confirm it's active with page caching on. Then remove any other page-cache plugin, such as WP Rocket, W3 Total Cache or WP Super Cache. Two page caches compete and often make things slower, not faster. ## 2. Switch on the CDN Premium and higher plans include Hostinger's CDN. Enable it in hPanel for the website. It delivers images, CSS and JavaScript from locations near each visitor, which matters most when your audience is spread across countries. ## 3. Run a current PHP version Newer PHP releases execute WordPress noticeably faster. In hPanel's PHP configuration, choose the newest version your theme and plugins support. Check the site afterward; if something breaks, drop back one version. ## 4. Fix the images **Symptom:** good first byte, slow LCP. **Cause:** almost always oversized images. **Fix:** resize each image to the width it actually displays at before uploading, and convert to WebP. LiteSpeed Cache's image optimization can convert in bulk. Lazy-load images below the fold, but never the main image at the top of the page. Lazy-loading that one pushes LCP later, which is the opposite of what you want. ## 5. Trim plugins and heavy themes Each active plugin adds work to every page view. Deactivate the ones you don't use, and replace any plugin that loads scripts sitewide for a feature that lives on one page. Big page builders and multipurpose themes ship a lot of code. If the theme is the culprit, a lightweight one such as GeneratePress, Kadence or Astra can make a large difference by itself. > From the bench: Every plugin is also something that can break on an update at 2 a.m. Fewer plugins means a faster site and fewer incidents. It's the rare optimization with no downside. ## 6. Add object caching Object caching holds database query results in memory so WordPress doesn't run them again. It pays off most on WooCommerce stores, membership sites and busy admin areas. Where your plan offers it, enable it in hPanel and in the Object settings of LiteSpeed Cache. ## 7. Look at resource usage **Symptom:** the site slows or throws errors at busy times, however well it's tuned. **Cause:** shared plans cap CPU, memory and concurrent processes, and you're hitting the caps. **Fix:** hPanel shows usage per plan. If you're at the limits regularly, optimization won't save you and it's time to upgrade. Business gives more resources than Premium, and Cloud Startup gives you dedicated CPU and RAM. The trade-offs are in [Premium vs Business vs Cloud Startup](https://www.savemores.store/compare/premium-vs-business-vs-cloud-startup). ## 8. Clean the database Post revisions, spam comments, expired transients and tables left behind by deleted plugins slow queries down over time. LiteSpeed Cache includes a database clean-up tool. Take a backup first, then run it. ## 9. Put the site near its visitors Distance adds latency to every request. If most visitors are in one region and the server is on another continent, the first byte will never be quick. The CDN helps with static files, but each page is still generated at your server. Ask Hostinger support whether the site can move to a closer data center. If not, create a new site in the right location and [migrate into it](https://www.savemores.store/guides/migrate-wordpress-to-hostinger). ## FAQ ### Why is my Hostinger site slow? Most often because page caching is off, images are oversized, or too many plugins are active. Less often, the site is hitting the plan's resource limits or is hosted far from its visitors. ### Should I use LiteSpeed Cache or WP Rocket on Hostinger? LiteSpeed Cache, for page caching, because it uses the LiteSpeed server's built-in cache. Run one page cache, never both. ### Is Hostinger's CDN an extra cost? No. It is included on Premium and higher web hosting plans. ### When is it time to upgrade for speed? When hPanel shows you regularly reaching CPU, memory or process limits after the site has been optimized. Business is the next step, and Cloud Startup gives dedicated resources.