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
Improving both is a good idea. You can view my list of common slow plugins where I used the WP Hive Chrome Extension to measure each plugin’s impact on memory usage and PageSpeed.
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
Slow hosting is bad for core web vitals because it affects TTFB which is also 40% of LCP.
You can use PageSpeed Insights to test them, your Search Console core web vitals report, or SpeedVitals (since PageSpeed Insights uses the Chrome UX report and takes 28 days to update).
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
Search “Hostinger scam” in Reddit. The only reason they’re cheap is because they give you less resources like CPU cores, RAM, and only 1GB email storage. Plus, they have frequent downtimes which you can test in UptimeRobot. Search Facebook groups and you’ll see many posts like this:
There Are Better LiteSpeed Hosts
NameHero is my go-to with NVMe/Redis, but their data centers are only in the US/EU. FastComet and ChemiCloud have more data centers outside US/EU and are very similar (ChemiCloud uses NVMe but has less cores/RAM). Scala is CloudVPS (faster) and uses their custom sPanel, but it costs more. All use LiteSpeed and are significantly better than Hostinger.
|Hostinger Business WordPress Plan||FastComet FastCloud Extra Plan||ChemiCloud WordPress Turbo Plan||NameHero Turbo Cloud Plan||Scala Hosting Build #1 Plan|
|Cores/RAM||2 cores/1.5GB||6 cores/6GB||3 cores/3GB (scalable to 6/6)||3 cores/3GB||2 cores/4GB|
|Storage||20GB SATA||35GB SATA||40GB NVMe||Unlimited NVMe||50GB NVMe|
|Data centers||8||11||11||2 (US + EU)||3 (US + EU)|
|Cache plugin||LiteSpeed Cache||LiteSpeed Cache||LiteSpeed Cache||LiteSpeed Cache||LiteSpeed Cache|
|CDN||QUIC.cloud ($.02-.08/GB)||QUIC.cloud ($.02-.08/GB)||QUIC.cloud ($.02-.08/GB)||QUIC.cloud ($.02-.08/GB)||QUIC.cloud ($.02-.08/GB)|
|Major incidents||Scam reports, fake reviews, 2019 breach||2022 DDoS attack on 3 data centers||None||2011 2-day node outage||None|
|Migrations||Unlimited (but screws it up)||3 free||200 cPanel + 10 non-cPanel||1 free||1 free|
|TrustPilot rating||4.6/5 (fake)||4.9/5||4.9/5||4.6/5||4.9/5|
|Intro price||$3.99/mo (1-4 year agreement)||$5.49/mo||$5.99/mo||$9.98/mo||$29.95/mo|
|View plan||View plan||View plan||View plan|
If you’ve read my blog, you probably know I use Rocket.net. They don’t use LiteSpeed (and will cost more), but they’re definitely the fastest host I’ve used with 32 CPU cores + 128GB RAM and Cloudflare Enterprise. You can read my full review but my <100ms global TTFB speaks for itself.
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.
Your site is probably the best ever for this kind of articles.
However, personally, with hostinger, I reached 25,520 clicks with 577,176 impressions (data from google search console… I don’t use google analytics so as not to slow down… I only used it once and I recorded 8.000 accesses in 30 minutes) in May 2021 and I don’t think many services allow you to reach certain numbers with 3.05€ a month spent.
ps mine is a blog dedicated to savings and I have some guides where I suggest where to follow events in streaming… for this reason I have traffic peaks in some days (and in some hours).
Thanks Nico. Yes, everyone’s experience is different and if they work for you, by all means keep using them. I just have heard many horror stories so in general, I stay clear of Hostinger. Can’t argue those numbers though.
Hostinger is the worst hosting company i have come across and the support is just horrible. Do not spend your hard earned money on this hosting provider because you will be sorry and frustrated in the end.
I bought the business hosting package and have been having issues from the very start. Nearly every week at least twice i get a CPU fault and the percentage of CPU usage is less then 10% in most cases which makes me believe that they use extremely low quality and also apply throttle limits no matter which package you are using. Support is just simply dumb and comes up with copy paste responses of plugin issues even when you have 0 plugins you will come across this issue. Secondly the logs do not point to any plugin related issues and thirdly when you ask for an RCA they just disappear and do not respond. My current issue has been ongoing for last 4 days now and still i am waiting to hear back from there technical team. I have been documenting this and if any one is interested to read the whole chat then feel free to click on this link >>>
Don’t forget you will always get low server response and DB related issues on top of this. Live support chat takes at least 1 hour before responding and they claim five mins lol.
In the document you can see the following in detail
1. Issue was with performance and as usual CPU faults. The support staff creating a blank HTML page with the words hostinger and claimed that our server response time is excellent :D. Can you imagine a blank HTML page being used to test server response lol
2. Issue is related to redirect from non www to www domain.
3. Trying to Transfer a website from Zoho Builder to Hostinger. You can see the knowledge of the support staff and how someone completely new to hosting can mess up things if they follow them
4. Error establishing a database connection. Once again i am facing this issue and this has been very consistent. This time they admitted that they are doing some maintenance and as usual no one informed about it.
5. CPU Fault once again and this time i had enough so decided to post everything online.
I swear 90% of people who comment about Hostinger have nothing but negative things to say. They create a nice illusion though! Sorry to hear your bad experience, I’m also trying to warn people to stay away/move. They’re awful.