Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My site on Hostinger got slow and nobody can say why

Short answer

On Hostinger, reaching the CPU or I/O limit makes the site queue visitors and run slower, with no error message. Reaching the RAM or process limit can show a 503 error. The Websites section shows a warning when limits are reached. Check that warning first, before paying for anything.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The site used to open quickly and now every page takes a long time.
  • The slowness comes in waves, often when more visitors are on the site.
  • The admin area of my site is slower than the public pages.
  • Sometimes visitors see a 503 error and then it clears by itself.
  • My developer says it is the hosting, the hosting says it is my site.

Why does this happen?

  1. The plan's CPU or I/O limit was reached

    Hostinger lists CPU, I/O, RAM and processes, and PHP workers as the limits of a hosting plan. When the CPU or I/O limit is reached, the site slows down because visitor requests are queued instead of served straight away, and no error message appears.

  2. Memory, processes or PHP workers ran out

    Hostinger says that reaching the RAM or process limit can show visitors a 503 Service Unavailable error, and that reaching the PHP workers limit can cause delays or timeouts.

  3. Plugins, scheduled jobs and uncached pages keep the server busy

    Hostinger's own advice for the CPU and I/O limits is to revise the code, reduce plugins and scheduled jobs, and turn on caching. A site that rebuilds every page for every visitor uses far more of the plan than one that serves saved pages.

  4. Bad traffic uses the plan too

    Hostinger suggests checking analytics for loopback requests or signs of a DDoS attack, because these can use up the limits. Bots that hit the site all day look like a slow site to real visitors.

  5. The site itself may be slow for other reasons

    Large images, a heavy theme and a slow database make a site slow on any host. The plan limits explain only one family of causes.

What can I do about it today?

  1. Look for the limits warningOpen the Websites section of your Hostinger account and look at the card for your plan. Hostinger shows the message "Your hosting resource limits have been reached" there when it applies. Write down the date and time you see it.
  2. Note when the slowness happensIs it all day, only at busy hours, or only after you publish something? A short list of dates and times lets whoever helps you match it against the resource charts.
  3. Do not install more speed pluginsStacking plugins adds load to a site that may already be at its limit. Change one thing at a time and note what you changed.
  4. Take a backup before any changeUse the backup option in your hosting account or your website's own backup tool so a change that goes wrong can be undone.
  5. Ask whoever built the site what runs on a scheduleScheduled jobs, imports and backup plugins can run at busy hours. Get the list in writing.
  6. Hold off on upgrading until you know which limit was hitHostinger lists an upgrade as one option if problems persist. Moving to a bigger plan without knowing the cause can cost more and still leave the slow code in place.

When should I bring someone in?

  • The warning keeps coming back after caching and plugin clean-up.
  • Customers see 503 errors or cannot check out or submit forms.
  • Nobody on your side can read the resource charts or the error logs.

How do I handle it?

  1. Read the limit that was reachedI check the resource charts and note which of the four limits shows faults, and at what times. That decides everything that follows.
  2. Find the pages and jobs that use the mostI look at which pages, plugins and scheduled jobs run at those times, and at traffic that is not real visitors.
  3. Change the cheapest thing firstCaching, plugin removal and image weight come before any plan change. I take a backup first and change one thing at a time.
  4. Measure again against the same chartsThe result is judged on the same charts and the same hours, not on a feeling that the site is faster.
  5. Say plainly if the plan is too smallIf the site has outgrown the plan, I write down the evidence and the options, including moving to a server that is sized for it.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Will a bigger plan fix it?

It can, if a plan limit is the cause. Hostinger lists upgrading as an option if problems persist after you reduce plugins and use caching. If slow code is the cause, a bigger plan only hides it for a while.

Why is there no error message when it is slow?

Hostinger states that when the CPU or I/O limit is reached, the site queues visitor requests and no error messages appear. That is why the problem feels like random slowness.

Is this the same as my site being down?

No. A slow site still answers. A 503 error is different and, according to Hostinger, can appear when the RAM or process limit is reached.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.