Shared hosting resource limits define how much server capacity an individual hosting account can use on a shared server. These limits can cover CPU, memory, disk activity and concurrent processes, helping prevent one website from consuming resources needed by other accounts.
If your website becomes slow, displays resource-limit errors or stops processing requests temporarily, the cause may be an account limit rather than a domain or DNS problem. Understanding the difference between package allowances and server resource limits helps you identify the issue and select an appropriate hosting plan.
What Are Shared Hosting Resource Limits?
Shared hosting resource limits are account-level restrictions that control how much of a shared server’s processing capacity a website can consume. Hosting providers configure these limits to distribute server resources among multiple accounts.
A shared hosting server runs websites belonging to different customers on the same physical server. Each account has its own files, databases and control panel access, but the accounts share underlying server hardware.
Resource limits may cover several areas:
- CPU usage: The processing capacity available to execute PHP scripts, database queries and other account tasks.
- Physical memory: The RAM available to processes running under the hosting account.
- Disk I/O: The rate at which an account can read data from or write data to storage.
- IOPS: Input/output operations per second, which measure how many storage operations can be performed.
- Entry Processes: The number of concurrent processes entering an account to handle requests.
- Number of processes: The number of processes that can run under an account at the same time.
These limits are not the same as disk space or monthly bandwidth allowances. A website can remain below its storage quota but still reach its CPU, memory or process limits when several requests require resources simultaneously.
Which Resource Limits Can Affect Your Website?
CPU, memory, disk activity and process limits can affect different parts of website performance. The resource that matters most depends on the application, plugins, database queries, traffic patterns and background tasks.
A hosting account may reach one limit without reaching the others. For example, a PHP application with inefficient database queries can use substantial CPU even when the website occupies little disk space.
CPU Usage
CPU usage measures how much processing capacity an account consumes while running scripts and applications. PHP execution, database-related work and scheduled tasks can all contribute to CPU demand.
If CPU usage repeatedly reaches its configured limit, requests may take longer to complete or processes may be restricted. Review resource graphs and application logs to identify scripts or tasks that consume more processing time than expected.
Physical Memory Usage
Physical memory is the RAM used by running processes. PHP workers, application scripts and other services consume memory while handling requests.
A website may reach its memory limit when multiple requests run together or when a script requires more memory than the account allows. Increasing the memory limit is not always possible on shared hosting because the provider controls the resource allocation.
Disk I/O and IOPS
Disk I/O measures data transfer between an account and storage, while IOPS measures the number of individual input/output operations. These metrics are related, but they do not describe exactly the same activity.
A website that repeatedly reads database files, creates temporary files or processes many small files may generate substantial storage activity. Repeated file operations can reach an I/O or IOPS limit even when the account has plenty of unused disk space.
Entry Processes Limit
An entry processes limit controls how many concurrent processes can enter an account to handle requests. It is not a direct measurement of total website visitors, page views or monthly traffic.
For example, visitors may open a website without all their requests executing PHP scripts at the same time. However, several simultaneous dynamic requests can occupy entry processes while the server handles them.
A website can therefore reach its entry processes limit during a busy period even if its overall visitor count does not appear unusually high.
What Is cPanel Resource Usage?
cPanel Resource Usage is a control-panel feature that displays account resource information and, when supported, reports whether resource limits have been reached. Its availability and the metrics shown depend on the hosting provider’s server configuration.
If your hosting provider has enabled the feature, sign in to cPanel and look for Metrics → Resource Usage. The exact interface and available reports can vary depending on the installed resource-management software.
The report may show:
- Current or recent CPU usage.
- Physical memory usage.
- Disk I/O and IOPS activity.
- Entry Process activity.
- Number of processes.
- Resource faults or recorded limit events.
A resource fault indicates that an account reached a configured limit during the reporting period. It does not automatically prove that the entire server is overloaded or that your website needs a larger hosting plan.
How to Check cPanel Resource Usage
You can check cPanel resource usage by opening the account’s Resource Usage section and reviewing its graphs, limits and recorded faults. Follow these steps:
- Sign in to your hosting account’s cPanel.
- Open the Metrics section.
- Select Resource Usage if it is available.
- Review the CPU and memory graphs.
- Check disk I/O, IOPS and Entry Processes.
- Inspect resource faults and their timestamps.
- Compare the affected times with website activity and scheduled tasks.
If Resource Usage is missing, contact your hosting provider to confirm whether the feature is enabled for your account. Do not assume that a missing menu means your account has no resource limits.
When investigating a fault, compare its timestamp with application activity. A scheduled backup, plugin task, import process or sudden increase in dynamic requests may explain why a limit was reached.
How Does the Entry Processes Limit Affect cPanel Resource Usage?
The entry processes limit affects cPanel resource usage by restricting the number of concurrent processes entering an account to handle requests. It is especially relevant to dynamic websites that execute PHP scripts when visitors open pages or submit forms.
Consider a website that receives several requests at once. If the requests require PHP execution and all available entry process slots are occupied, additional requests may wait or fail temporarily, depending on the server configuration.
A common mistake is to interpret an entry process fault as proof that a website has too many visitors. The actual cause may be slow scripts, repeated requests, an inefficient plugin or a background task holding processes for too long.
Check these areas when entry process faults appear:
- PHP execution: Identify scripts that take unusually long to finish.
- Plugins and themes: Review recently installed or updated components.
- Database queries: Look for inefficient queries that delay page generation.
- Scheduled tasks: Check cron jobs and imports that overlap with busy periods.
- External requests: Review scripts that wait for third-party APIs or remote services.
The correct response is to find the process causing the congestion. Simply selecting a plan with more disk space will not necessarily resolve an entry process problem.
How Can You Reduce Shared Hosting Resource Usage?
You can reduce shared hosting resource usage by improving application code, limiting unnecessary background tasks and reducing repeated database and file operations. Start by identifying the metric that reaches its limit, then investigate the activity responsible.
Use these practical checks:
- Review plugins: Remove unused plugins and investigate components that generate repeated requests.
- Enable caching: Use suitable page and object caching to avoid repeating expensive application work.
- Optimise images: Resize and compress large images before uploading them.
- Check cron jobs: Avoid unnecessary or overlapping scheduled tasks.
- Review database queries: Reduce repeated queries and investigate slow operations.
- Update applications: Keep WordPress, PHP and other application components maintained and compatible.
- Inspect access logs: Look for repeated requests to expensive pages or scripts.
For WordPress websites, caching can reduce the number of requests that need full PHP execution. However, logged-in dashboards, checkout pages and personalised content may require different caching rules.
Before disabling plugins or changing application settings, create a backup. A configuration change can affect forms, checkout processes or other important website functions.
For more information about diagnosing website performance, see [ARTICLE LINK: WordPress website speed optimisation].
Which Xenax Cloud Shared Hosting Plan Fits Your Website?
The suitable Xenax Cloud shared hosting plan depends on the number of websites, disk space, bandwidth and mailboxes your account needs. These package allowances help you compare plans, but they should not be confused with CPU, RAM or entry process limits.
Xenax Cloud shared hosting uses cPanel and LiteSpeed web server technology, includes Let’s Encrypt SSL and DDoS protection, and provides JetBackup 5 backups.
| Plan | Websites | Disk space | Bandwidth | Mailboxes |
| Silver | 1 | 5 GB | 50 GB | 3 |
| Gold | 3 | 15 GB | 100 GB | 6 |
| Platinum | 10 | 100 GB | 1,000 GB | 25 |
| Diamond | Unlimited | Unlimited | Unlimited | Unlimited |
The Diamond plan is the only shared hosting tier listed with unlimited bandwidth. Silver, Gold and Platinum have defined bandwidth allowances, so check the relevant package before hosting media-heavy websites or several projects.
Worked Example: A Varanasi Agency Hosting Four Client Websites
Consider a small digital agency in Varanasi managing four client websites. The agency needs 25 GB of website storage, separate mailboxes for client communication and enough package capacity to host all four websites under one account.
Platinum is the suitable package to evaluate because it supports 10 websites, 100 GB disk space, 1,000 GB bandwidth and 25 mailboxes. Gold would not fit the requirement because it supports only three websites, 15 GB of disk space and six mailboxes.
However, selecting Platinum does not automatically guarantee that every website can use unlimited CPU, memory or concurrent processes. The agency should confirm the account’s configured resource limits with Xenax Cloud before moving all four websites.
If your website count, storage or mailbox requirements fit the Silver or Gold allowances, a higher tier may not be necessary. If your application requires sustained processing capacity, custom server configuration or resources beyond shared hosting, a KVM VPS may be more suitable than moving to another shared package.
You can compare the Xenax Cloud shared cPanel hosting plans and select a package according to your website and account requirements.
What Should You Check Before Upgrading Your Shared Hosting Plan?
Before upgrading, identify which resource limit is being reached and confirm whether the problem comes from account capacity or application behaviour. A larger package may provide more website, storage or bandwidth capacity, but it does not automatically increase every server resource limit.
Use this decision rule:
- Choose Silver if you host 1 website, need up to 5 GB disk space, 50 GB bandwidth and 3 mailboxes.
- Choose Gold if you host up to 3 websites and need up to 15 GB disk space, 100 GB bandwidth and 6 mailboxes.
- Choose Platinum if you host up to 10 websites and need up to 100 GB disk space, 1,000 GB bandwidth and 25 mailboxes.
- Choose Diamond if you need the listed unlimited website, disk, bandwidth and mailbox allowances.
- Consider a VPS if your application needs greater control over CPU, RAM, server configuration or sustained processing capacity.
Before ordering, ask the provider to confirm the configured CPU, physical memory, I/O, IOPS and entry process limits for the specific account. These values are not provided by the package storage and bandwidth specifications.
For technical reference, cPanel explains the information available in its Resource Usage interface. The interface can help you identify account resource faults, but the hosting provider controls the limits applied to your account.
If your website continues to reach resource limits after optimisation, moving to a VPS may be worth considering. Read our guide on how much RAM a VPS needs to understand memory requirements and compare suitable server configurations.
Common Mistakes When Interpreting Shared Hosting Resource Limits
The most common mistake is treating every hosting restriction as a storage or bandwidth problem. Resource limits measure different types of server activity, and the correct fix depends on the metric involved.
Avoid these misunderstandings:
- More disk space means more CPU: Disk capacity and processing capacity are separate resources.
- Entry Processes equal visitors: Entry Processes measure concurrent processes, not total visitors.
- No resource faults means no performance problem: A website can still be slow because of application code, database queries or external services.
- A resource fault always means an upgrade is necessary: Optimising a script or plugin may resolve repeated faults.
- Unlimited package allowances mean unlimited server resources: Diamond’s unlimited website, disk, bandwidth and mailbox allowances do not mean unlimited CPU or memory.
If a website repeatedly reaches a configured limit after application optimisation, discuss the account’s resource allocation with the provider. If the workload needs dedicated control over server resources, evaluate a VPS rather than assuming a shared hosting upgrade will solve every issue.
Shared Hosting Resource Limits: FAQs
What are shared hosting resource limits?
Shared hosting resource limits are restrictions on how much server capacity an individual hosting account can consume. They may cover CPU, physical memory, disk I/O, IOPS and concurrent processes. Hosting providers configure these limits to distribute resources among accounts sharing the same server.
What is cPanel resource usage?
cPanel resource usage is account-level information that shows how hosting resources are being consumed when the provider enables the Resource Usage feature. You can look for CPU, memory, disk activity, Entry Processes and recorded faults under Metrics in cPanel. The exact metrics depend on the server configuration.
What is the entry processes limit in shared hosting?
The entry processes limit controls how many concurrent processes can enter a hosting account to handle requests. It does not represent the total number of visitors or page views. Slow PHP scripts, overlapping tasks and simultaneous dynamic requests can contribute to reaching this limit.
Why does my website reach its shared hosting resource limits?
A website may reach shared hosting resource limits because of expensive PHP scripts, inefficient database queries, repeated requests, background jobs or increased concurrent activity. Check the resource report and application logs to identify the affected process. Optimising the application may resolve the issue without changing the hosting plan.
Does upgrading my shared hosting plan increase CPU and RAM limits?
Not necessarily. An upgrade may increase package allowances such as websites, disk space, bandwidth and mailboxes, but CPU and RAM limits depend on the provider’s configuration. Ask the provider to confirm the exact resource allocation and whether an upgrade changes those limits before ordering.
How can I check entry process faults in cPanel?
Open cPanel, find Metrics and select Resource Usage if the provider has enabled it. Review the Entry Processes graph and fault information, then compare the timestamps with website activity and scheduled tasks. Contact your hosting provider if the report does not show enough detail to identify the cause.
When should I move from shared hosting to a VPS?
Consider a VPS when your application needs greater control over server configuration, sustained processing capacity, custom software or resource allocation. Shared hosting remains suitable when your website fits the package allowances and configured resource limits. Choose a VPS based on measured CPU, memory and storage requirements.
If you manage up to 1 website, evaluate Silver; for up to 3 websites, compare Gold; and for up to 10 websites with larger storage and bandwidth requirements, consider Platinum. If your website repeatedly reaches CPU, memory or process limits despite optimisation, ask Xenax Cloud to clarify the available account limits or evaluate a KVM VPS.
