Hosting Limits Guide: Find the Capacity Check Your Website Needs
Guides / Hosting limits
Guide index reviewed: October 5, 2026. Use this page to find HRL’s detailed capacity and operational checks. It does not set a universal plan size or certify a provider’s performance.
Start with the workload or warning you need to understand. A storage figure, visitor allowance or “unlimited” label does not answer every hosting question. This index connects the relevant explanations so you can collect the right evidence before buying or upgrading.
Choose the right capacity guide
| Your question | Guide | What to record |
|---|---|---|
| Is the account running out of processing capacity? | CPU and account resources | Metric, unit and incident time |
| Are PHP requests waiting? | Workers, threads and queues | Concurrency scope and queue evidence |
| Does a task hit a memory limit? | WordPress memory versus RAM | Effective setting and exact error |
| Is space or data transfer the issue? | Storage and transfer | Usage measure and billing period |
| Why are file counts near the cap? | Inodes and files | Directory breakdown and included services |
| Does a database or import reach a limit? | Database constraints | Size, count, tool and connection limits |
| What does an unlimited offer mean? | Unlimited hosting claims | Exact advertised dimension and policy |
If the site works but a background workflow fails
Use WordPress cron to investigate how a task starts and WooCommerce scheduled actions to inspect the relevant job and logs. For missing notifications, follow the email delivery checklist. These checks separate the trigger, execution and observed outcome.
If you need a usable recovery route
Start with backup coverage, then check retained recovery points and a restore rehearsal. Stores should also review newer-order recovery. An upgrade decision should account for the recovery procedure as well as capacity.
Use a consistent comparison record
HRL recommends recording the exact plan, measured workload, applicable limit, source, verification date and next action. Distinguish a published plan specification from an observation on your own site. Where a provider has not supplied a limit or enforcement rule, mark it unknown and request clarification.
As one primary-source reference, Hostinger’s resource documentation lists CPU, RAM, files, database and PHP limits separately. The linked HRL guides explain which questions to ask without treating one provider’s model as universal.
Route an observed symptom to the right guide
A failed large import starts with tool and database limits; a logged allocation error starts with effective memory limits. Slow uncached requests need timing and queue evidence. These are investigation paths, not diagnoses. Record the actual error and incident time before choosing which allowance to buy more of.
Connect the diagnosis to a buying decision
First establish whether the current issue is a required workload exceeding confirmed capacity or an operation needing repair. Compare a proposed change against the constraint identified, then repeat the important workflow. For a store, use the hosting requirements guide as the compatibility checklist.
Get the effective limits, recurring price and support scope in writing before choosing another tier or supplier. Use stay, renegotiate or switch for the cost decision. If moving wins, complete the migration checks before ending old hosting.