Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My host says I hit a resource limit and my site is being throttled

Short answer

Shared hosting gives each account a fixed share of CPU, memory, disk activity and simultaneous processes. When the share is used up, the host slows the site or shows an error. Ask the host which limit was hit and when, then reduce what uses it. A bigger plan is one option, not the first step.

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

Does this sound like your situation?

  • My host emailed me that my account reached its resource limit.
  • Visitors sometimes see a "Resource Limit Is Reached" page.
  • The site is fine at night and crawls in the afternoon.
  • Pages that normally take a second now take many seconds.
  • The host's answer is to upgrade, with no detail about what used the resources.

Why does this happen?

  1. A shared account has a fixed share of the server

    Hostinger lists CPU, I/O, RAM and processes, and PHP workers as the limits of a plan. Other hosts use different names and numbers, but the idea is the same: one account may not take the whole server.

  2. Each limit fails in a different way

    According to Hostinger, the CPU and I/O limits make the site slower with no error message, the RAM and process limits can show a 503 error, and the PHP workers limit causes delays or timeouts. Which symptom you see tells you which limit was hit.

  3. A few heavy requests use most of the share

    Uncached pages, search and filter pages, plugins that call other services, and scheduled jobs all start PHP processes. Hostinger advises keeping CPU below 80% at peak hours and reducing plugins, scheduled jobs and scripts that start PHP processes.

  4. Robots and attacks count as visitors

    Hostinger says to check analytics for loopback requests or signs of a DDoS attack, because these can cause overages. A bot that requests thousands of pages uses the same share as real customers.

  5. The PHP code is memory hungry

    Slow scripts keep processes busy for longer, so fewer fit in the share. This is a coding problem that the host cannot fix for you.

What can I do about it today?

  1. Ask the host three questions in writingWhich limit was reached, at what times, and which account or site used it. Keep the reply.
  2. Open the resource usage view in your control panelMost hosts show charts of CPU, memory and processes. Take screenshots of the busy hours before they scroll out of view.
  3. Check who is visitingLook at your analytics for a sudden jump from one country or one page. Do not block anything yourself unless you know what it is.
  4. Pause what you added lastA new plugin, import or newsletter that matches the date the trouble started is the first suspect. Take a backup, then switch off one thing at a time.
  5. Do not move to a different host in a hurryA rushed move can break email and the domain, and the slow code comes with you. See the related page about changing hosts.
  6. Keep the host's emailsIf the host later suspends the account, these messages are your evidence of what was said and when.

When should I bring someone in?

  • The host has set a deadline or warned of suspension.
  • The limit is hit every busy hour even after caching.
  • You cannot tell real visitors from bots in the charts.

How do I handle it?

  1. Identify the limit by its symptomSlow with no error, 503 errors and timeouts point to different limits, so I match the symptoms and the charts first.
  2. Separate real visitors from bot trafficI read the access logs and the analytics to see how much of the load is not customers, and what can safely be filtered.
  3. Reduce what runs per requestCaching, fewer plugins, lighter queries and moved scheduled jobs come before a plan change. I back up first and make one change at a time.
  4. Prove the result on the same chartsI compare the same busy hours before and after.
  5. Write the options down if the plan is too smallIf the share is genuinely too small, I list the choices with the evidence, including a server sized for the site.

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?

Is throttling the same as being suspended?

No. Throttling slows the site while it stays online. A suspension takes it offline. Read the host's message carefully, because the wording decides which one you have.

Does the error mean I was hacked?

Not by itself. Hacked sites do use up resources, so check for unknown files and users, but most limit errors come from plugins, uncached pages and ordinary bots.

Should I just buy more resources?

Hostinger lists an upgrade as an option if problems persist after reducing plugins and using caching. Find the cause first, or the same problem returns on the bigger plan.

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.