Have a slow website on Hostinger?
You can speed up your slow Hostinger website by installing LiteSpeed Cache and configuring the settings with QUIC.cloud’s CDN. Several Hostinger settings can also help (PHP 8, Brotli, OPcache, hotlink protection, and disabling XML-RPC). I’ve also listed quite a few general recommendations like optimizing your theme, plugins, images, fonts, and even core web vitals.
Hostinger is infamous for cheap hosting, but it comes at a cost. It’s still shared hosting with slow SATA SSDs and less CPU/RAM than similar LiteSpeed hosts. They also write fake reviews (which their CEO openly encourages) and trick people into buying their hosting by pretending to be customers. Sure they’re cheap and use LiteSpeed, but there are better options. For example, NameHero has more CPU/RAM with faster NVMe storage and better support/uptimes. Whether or not you switch to them, I encourage you to search Facebook Groups for unbiased feedback.
At the end of the day, they’re scammers disguised as a hosting company. But if you must continue to use them, here’s how to optimize your WordPress site on Hostinger’s crap hosting.
- Check for a slow TTFB
- Switch your DNS to Cloudflare
- Configure LiteSpeed Cache
- Setup QUIC.cloud’s CDN
- Use PHP 8+
- Enable Brotli + OPcache
- Enable hotlink protection
- Disable XML-RPC
- Schedule cron jobs
- Avoid slow plugins
- Avoid slow page builders
- Remove unused CSS/JS
- Optimize fonts
- Improve core web vitals
- Leave Hostinger
1. Check For A Slow TTFB
Most speed testing tools only measure TTFB in 1 location.
The correct way to measure TTFB is to test your site in SpeedVitals (about 3 times) to ensure your caching/CDN are working. This measures your average TTFB worldwide in 35 locations. You can use PageSpeed Insights which flags your TTFB when it’s 600ms+, but <200ms is ideal.
If your TTFB is slow, make sure to use full page caching (QUIC.cloud has this or you can use Cloudflare’s APO). While CDNs are part of TTFB, your servers (hosting) are obviously the other major contributor. Even Gijo Varghese from WP Speed Matters doesn’t recommend Hostinger.
2. Switch Your DNS To Cloudflare
Most domain registrars (Hostinger, NameCheap, GoDaddy) have a slow DNS. You’re better off using Cloudflare’s DNS which performs very well on dnsperf.com. Latency is part of TTFB, and TTFB is 40% of largest contentful paint. Which means bad latency causes a chain of problems.
Switching to Cloudflare’s DNS is easy. Sign up for a free Cloudflare account, add your website, select the free plan, then Cloudflare will assign 2 nameservers which you will change in hPanel.
Login to your Hostinger hPanel and head to the Domains tab. Copy the 2 nameservers provided by Cloudflare, then paste them here. And finally, click “Done, check nameservers” in Cloudflare.
It’s best to setup Cloudflare manually instead of the Cloudflare add-on in Hostinger’s dashboard since you have more control over Cloudflare’s settings. However, you won’t need to configure Cloudflare’s dashboard if you plan on using QUIC.cloud for your CDN.
3. Configure LiteSpeed Cache
Hostinger uses LiteSpeed servers, so you should really be using the LiteSpeed Cache plugin which has excellent reviews. It’s also faster compared to other cache plugins (including WP Rocket) since it uses server-level caching and has extensive features to address core web vitals.
LiteSpeed Cache has a lot of options and it’s key to make sure you’re using the best settings. While I highly recommend reading that complete tutorial to configure it, below are a few key things you can do in the LiteSpeed Cache setting that can help fix a slow website on Hostinger. These are general recommendations to use as a baseline, configure them for your own website!
LiteSpeed Cache Tips
- Hostinger Doesn’t Support Object Cache – this is listed in their article which means you can’t use LiteSpeed Cache’s object cache settings. The “object cache” screenshot shown above is taken from NameHero who does support object cache.
- QUIC.cloud – arguably the best CDN when using LiteSpeed Cache and can be setup using QUIC.cloud’s DNS, Cloudflare, or through CNAME records. I highly recommend using the paid (standard) version which uses all 70+ PoPs and includes DDoS protection, while the free plan uses 6 PoPs and no DDos protection.
- HTML lazy load selectors – FlyingPress has a nice video on how to do this. You can lazy load pretty much anything on your site (comments/footer are common).
- Image optimization – setup QUIC.cloud to optimize images which is an excellent image optimizations solution. Compress them, use WebP to serve images in next-gen format, and don’t preserve EXIF data unless you’re a photographer or similar.
- Font display optimization – if you see “ensure text remains visible during webfont load” in your PageSpeed report, try changing this to font-display: swap.
- Localize files – host third-party code locally which is faster than external requests.
- Database – cleans junk from your database and limits post revisions. To go a step further, install WP-Optimize and go through your actual plugin tables, then delete those left behind by old plugins you’ve deleted which are marked as not installed.
4. Setup QUIC.cloud’s CDN
QUIC.cloud’s CDN is built to work on LiteSpeed and is needed for page/image optimizations in LiteSpeed Cache. It also does HTML caching (which can significantly improve your TTFB). As I mentioned, you should ideally use the paid (standard) plan which uses 70 PoPs and includes DDos protection. If you’re planning on using a free CDN, you’re probably better off using Cloudflare. QUIC.cloud can be activated in LiteSpeed Cache (see instructions). Here are steps:
- Request a domain key in LiteSpeed Cache.
- Enable QUIC.cloud in your CDN settings.
- Link your domain to QUIC.cloud and visit the dashboard.
- Enable the CDN in QUIC.cloud’s CDN settings.
- Choose your setup method (below is for CNAME).
- QUIC.cloud will give you a CNAME record.
- Paste QUIC.cloud CNAME record in Hostinger hPane’s Zone Editor.
- Enable static cache + QUIC backend in the settings.
- Wait 24 hours for DNS to propagate, then make sure the CDN works in QUIC.cloud.
5. Use PHP 8+
Hostinger is actually good about releasing new PHP versions and supports PHP 8.
- Login to hPanel and open your Hosting Account dashboard.
- In the Advanced section, click “PHP Configuration.”
- Select the PHP version (8.0).
- Save, then check your site for errors.
6. Enable Brotli + OPcache
Brotli compresses pages to smaller file sizes. OPcache improves PHP performance and CPU utilization (which can reduce CPU usage on Hostinger). Both can be activated in PHP extensions.
7. Enable Hotlink Protection
Hotlink protection stops people from copying your images and pasting them on their website while they’re still hosted on your server (this reduces bandwidth usage especially if you have high quality images). In your Hostinger dashboard, go to Other → Hotlink Protection, then select the files you want to enable it for. If using Cloudflare, they also have hotlink protection.
8. Disable XML-RPC
XML-RPC is mainly used with JetPack or to publish content from mobile. If you don’t use either, it adds unnecessary code and can be disabled in your Hostinger dashboard (in PHP extensions).
9. Schedule Cron Jobs
Some things on your site are triggered with specific actions. For example, wp-cron runs jobs before a page loads, your entire cache is rebuilt after taking specific actions in cache plugins, and cache plugin’s preloading can increase CPU usage. By scheduling these with cron jobs, you can save resources so they don’t run automatically. The screenshots show you how to replace wp-cron with a real cron job. Also check your cache plugin’s documentation for using cron jobs.
Before setting up an external cron job, the first step is disabling the built-in wp-cron. Add the code to your wp-config.php file before where it says “That’s all, step editing! Happy blogging.”
Next, follow Hostinger’s instructions:
This is what it would look like:
10. Avoid Slow Plugins
There are also tools like Query Monitor to find your slowest plugins:
I also recommend using Perfmatters to disable plugins where they don’t need to load:
11. Avoid Slow Page Builders
12. Remove Unused CSS/JS
When was the last time you checked your coverage report in Chrome Dev Tools?
This shows your largest CSS/JS files which are often from themes, plugins, or third-party code. Since multiple PageSpeed Insights items are related to CSS/JS, it’s key to reduce/optimize them.
- Avoid CSS/JS heavy plugins/themes.
- Use CSS removal tools like PurifyCSS.
- Activate CSS/JS optimizations in Elementor/Divi.
- Disable plugins on specific pages using Perfmatters.
- Remove Gutenberg’s CSS if you don’t use Gutenberg.
- Code your header/footer/sidebar in CSS (don’t use page builders).
- Enable display dependencies in Perfmatters to see all plugins using jQuery.
- Use the “remove unused CSS” in FlyingPress, LSC, or Perfmatters (not WP Rocket).
13. Optimize Fonts
Check your GTmetrix Waterfall chart to see your font’s load times.
Reducing the number of fonts on your website is the first step. Make sure fonts are hosted locally instead of pulling from third-party sites like fonts.gstatic.com (you can do this manually or by using the OMGF plugin). Also use .woff2 format and not .ttf. Finally, test preloading fonts which you can do in LiteSpeed Cache. Divi and Elementor also have settings to optimize fonts. You can also try using font-display: swap, serving fonts from your CDN, and using system fonts.
14. Improve Core Web Vitals
Largest Contentful Paint – this is the core web vital people struggle with most. Since 40% of LCP is TTFB, you want to make sure you’re on fast servers and using a good CDN with full page caching (like QUIC.cloud). Optimizing above the fold content is also important (i.e. excluding above the fold images from lazy load and preloading them), and preloading key requests like fonts. Reducing CSS/JS, lazy rendering HTML elements in LSC, and optimizing images helps too.
Cumulative Layout Shift – use Google’s layout shift debugger to find which elements on your website shift while loading. This is usually related to fonts, CSS, elements without specified dimensions (images, iframes, etc), animations, or not reserving space for dynamic content (like advertisements). Try hosting fonts locally and preloading them, adding font-display: swap to your font’s CSS, disabling asynchronous CSS in your cache plugin, using critical CSS, and using CSS transform/translate properties when using animations. These should all help improve CLS.
15. Leave Hostinger
At the end of the day, Hostinger is cheap shared hosting with less CPU/RAM, slow SATA SSDs, and frequent downtimes which you can test in UptimeRobot. The only people recommending them are affiliate sites (including Hostinger’s own employees who write fake reviews) as well as bogus “fastest WordPress hosting” tests. Plus, I bet they locked you into a 4-year trap to get the cheapest price. Next time, do your research in the unbiased WP Speed Matters Facebook Group.
NameHero is similar to Hostinger with LiteSpeed, cPanel, and they’re cheap for 1-3 years. However, they have more CPU/RAM and their Turbo Cloud plan uses NVMe SSDs (much faster than SATA) with better uptimes/support shown in their TrustPilot reviews. The major con is their data centers are only in the US + Netherlands, but this shouldn’t matter much if using QUIC.cloud’s HTML caching. NameHero also does free migrations.
Cloudways Vultr HF is who I previously used which is cloud hosting with NVMe SSDs and Redis Object Cache Pro (faster than Hostinger, SiteGround, and pretty much any shared hosting). They also have a Cloudflare Enterprise add-on for $5/mo which can make a huge improvement to TTFB. Cloudways has excellent feedback in Facebook Groups if you read threads. The main cons are no file manager and email hosting is $1/email/month. Cloudways is a little techier because they use a custom dashboard which requires launching a server, but most people find it easy once you get used to it. It’s monthly pricing with no high renewals, 3-day trials, and includes a free migration. They also have great TrustPilot reviews and will be significantly faster than Hostinger.
Rocket.net is who I currently use with their free Cloudflare Enterprise and you can click through my posts or test my site in SpeedVitals. While they start at $25/mo, they should give you the fastest TTFB of pretty much any host (it’s private cloud hosting with 32 CPU + 128GB RAM + NVMe, Redis, and LiteSpeed’s PHP). Their Cloudflare Enterprise is better than Cloudways/Kinsta’s since it’s free, setup automatically, and uses full page caching with Argo Smart Routing. You’ll also get prioritized routing, image optimization, Brotli, HTTP/3, load balancing, and WAF. Not to mention Ben Gabler (CEO) was Chief Product Officer at StackPath and has experience building CDNs, so I trust their integration more. They also don’t limit PHP workers. You can try them for $1 your first month, check out the interview I did with Ben, or read my full review. They have a perfect TrustPilot rating.
|Hostinger||SiteGround||NameHero Turbo Cloud||Cloudways Vultr HF||Rocket.net|
|Hosting type||Shared||Shared||Shared||Cloud||Private cloud|
|CPU cores||1-2||Not listed||3||1||32|
|RAM (GB)||.768 – 3.072||Not listed||3||1||128|
|Object cache||x||Memcached||Redis||Redis (Pro)||Redis|
|CDN||QUIC.cloud||SiteGround CDN||QUIC.cloud||Cloudflare Enterprise ($5/mo)||Cloudflare Enterprise|
|Full page caching||✓||✓||✓||x||✓|
|Argo smart routing||x||x||x||✓||✓|
|CPU limits||Low resources||Common||Average||Average||None|
|Cache plugin||LSC||x||LSC or W3TC||Breeze||x|
|Major incidents||Security incident||Google blocked DNS for 4 days||2 day outage||None||None|
|Renewals||Very high||Very high||High||Monthly||Monthly|
Here are the setups I recommend depending on your budget:
|Hosting||Cache Plugin||CDN||Email Hosting||Total (Monthly)|
|NameHero ($7.38/mo)||LiteSpeed Cache (Free)||QUIC standard plan (.01 – 04/GB)||Included||$7.38 + .01 – 04/GB|
|Cloudways Vultr HF ($13/mo)||FlyingPress ($42/year)||Cloudflare Enterprise ($5/mo)||Google Workspace ($6/mo)||$27.5|
|Rocket.net ($25/mo)||FlyingPress ($42/year)||Cloudflare Enterprise (Free)||Google Workspace ($6/mo)||$34.5|
Conclusion: a slow website on Hostinger is usually caused by their cheap shared hosting which has low CPU + RAM, slow DNS, SATA SSDs, and no object cache. You’re getting what you paid for.