Slow Hostinger site? Diagnose it first, then apply these 9 fixes

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: 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.

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.

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.

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.

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.

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.

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.

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.

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.