English
Magyar
Imagine that, right in the middle of your most important campaign, just as your adverts are starting to convert, your website suddenly becomes inaccessible, accompanied by a mysterious 508 error message. This is the moment when the limitations of shared hosting turn into tangible, gut-wrenching business losses, and what was once cost-effectiveness suddenly becomes a risk.
You’ve probably experienced slow loading times during peak periods, or seen technical error messages that require expert help to understand. It’s a completely natural process for a successful website to outgrow shared resources over time, as fixed CPU and RAM limits can hinder further growth. In this guide, you’ll gain a clear understanding of the technical limitations of shared hosting and learn when it’s time to upgrade. We’ll analyse the cPanel statistics report in detail and provide you with a clear decision-making framework, enabling you to confidently determine the optimal time to switch to a VPS.
What is shared hosting and how do its physical limitations work?
The basic logic behind shared hosting is based on cost-effectiveness. Hundreds, and in some cases thousands, of websites share a single high-performance physical server. This model allows you to use professional-grade infrastructure for the price of a couple of scoops of ice cream a month. However, the laws of physics also apply in the digital realm. The server’s processor (CPU), main memory (RAM) and the read/write speed of the hosting (I/O) are finite resources. When we talk about the limitations of shared hosting, we are actually referring to these hard hardware limits, which determine how many visitors your site can serve at any one time.
The term ‘unlimited’ is often used in marketing messages, but it is important to clarify that there is no such thing as infinite resources. Providers regulate usage in line with their Fair Usage Policy. This safety net protects the community. If a single website were to start using up all the server’s memory, the websites of all other customers would go down. In modern web hosting plans, speed is now underpinned by NVMe SSD technology. These drives are orders of magnitude faster than traditional hard disk drives, which helps to push the boundaries, but does not remove the software-imposed limitations.
The logic behind shared resources
Server resources can be likened to a shared pot. If a website requires too many CPU cycles due to unoptimised code or a sudden surge in traffic, the system must intervene. This is known as the ‘noisy neighbour’ effect. To maintain stability, providers limit the number of concurrent processes (Entry Processes) and the traffic per second on the disk. If your site reaches these limits, your visitors will experience slowdowns or error messages. This is a constant balancing act between individual performance requirements and overall server stability.
CloudLinux and LVE: The role of isolation
The technological backbone of modern web hosting services is provided by the CloudLinux operating system and its LVE (Lightweight Virtual Environment) module. This solution isolates users within virtual containers, thereby bringing order to the shared environment. This isolation ensures that you cannot view other tenants’ files, and they cannot access your data either. LVE technology also guarantees fixed base resources. This means that the amount of RAM specified in your plan is genuinely available to you, and other users’ spikes in traffic cannot ‘steal’ the necessary capacity from your site. This type of isolation is the first line of defence for security and predictable operation.
The most important technical limitations: CPU, RAM and Entry Processes
Many people make the mistake of focusing solely on storage space when choosing a plan. Yet storage capacity rarely becomes a bottleneck in day-to-day operations. The real challenge lies in managing computing capacity and concurrent connections. The CPU limit, for example, determines what percentage of the processor the server can allocate to running your code. If a complex database query or a poorly written plugin performs too many operations, the system will throttle the process. It is at times like these that the limitations of shared hosting become noticeable to visitors as well.
Physical memory (RAM) is also a critical factor. Every PHP script that runs on the site takes up a certain amount of memory. A modern WordPress site, particularly one using many plugins, can easily reach the 256 or 512 MB limit. If the RAM runs out, the server is forced to terminate the process. This results in an immediate error message for the visitor, and the site simply stops working.
Entry Processes (EP) is perhaps the most misunderstood metric. It does not refer to the number of daily visitors. It shows how many requests can run concurrently at any one moment. If this figure is, for example, 20, and 21 people happen to click on your site at the same time, the last visitor will receive an error message. I/O speed is also linked to this. It determines how quickly the system can read data from the disk. Even the fastest NVMe SSD is of no use if software limitations restrict the data flow. If these limitations regularly hinder your business growth, it is worth considering the flexibility offered by our VPS servers.
The dreaded 508 and 503 error codes
When the message ‘Resource Limit Is Reached’ appears in your browser, your website has hit a wall. This is usually error code 508. Error code 503, on the other hand, indicates that the server is temporarily unable to fulfil the request due to overload. It’s worth regularly checking the “Resource Usage” module on your cPanel hosting dashboard. Here, you can see from the graphs which resource has been exhausted and when the error occurred. In the short term, caching and optimising images can help, but these are merely stopgap measures.
Process Limit
It is important to distinguish between web requests and processes running in the background. The ‘Number of Processes’ limit counts every active process. This includes SSH connections, cron jobs and email sending processes. A poorly configured cron job running every minute, for example, can quickly use up the quota. In modern systems, PHP-FPM helps to manage processes more efficiently, but even this does not eliminate the physical limitations. If you notice that the statistics are consistently in the red zone, it is worth considering switching to a VPS to gain access to dedicated resources.
File system and database limits: Inodes and queries
As well as physical resources such as the CPU and RAM, there are also limitations that affect how files are stored and data is accessed. Many users are surprised when their storage space fills up, even though, based on the amount of space used (GB), there should still be plenty of room left. This is when the specific rules of the file system come into play. The limitations of shared hosting govern not only performance but also scalability, ensuring that the server’s file system remains manageable and fast for all tenants.
One of the most important, yet least frequently mentioned, metrics is the inode. Every single file, folder, email or symbolic link on the server occupies exactly one inode. Providers impose an inode limit because too many small files can drastically slow down backups and file system checks. If you reach this limit, you will not be able to create any more files, even if your storage space would otherwise allow it. This is a critical error, as it means the website cannot cache content, emails will not be delivered, and updates will also fail with an error message.
Managing the inode limit
The number of files can be increased most rapidly by poorly configured caching plugins and accumulated emails. Tens of thousands of small files can be created in the cache folder of a single WordPress site in a matter of moments. It is worth regularly deleting old log files and backups that are no longer needed. On the aWh cPanel hosting interface, you can check your current inode usage at any time in the statistics bar on the right-hand side. If the number is approaching the maximum, cleaning up is the first step, but in the long term, the solution lies in carefully managing the number of files.
MySQL and database limits
Databases serving the dynamic content of websites also operate within strict limits. In a shared environment, the number of concurrent MySQL connections is restricted. This is why an online shop might suddenly crash during the payment process or a promotional period. The system does not allow more simultaneous queries in order to protect the server from freezing. Slow queries are particularly dangerous because they can lock database tables for long periods, thereby paralysing the entire site. Database optimisation, indexing and keeping table sizes under control are essential for smooth operation.
Oversized database tables, such as log or session tables containing hundreds of thousands of rows, significantly increase response times. On shared hosting, efficiency is key. The fewer and faster the queries your site runs, the further you’ll be from technical limitations. However, if your business processes already require more complex database operations, moving towards dedicated resources will be the next logical step.
Security and software limitations: The ‘Noisy Neighbour’ effect
Existing in a shared environment is not just about physical resources, but also about the rules of communal coexistence. The ‘Noisy Neighbour’ phenomenon occurs when the activity of one website on the server indirectly affects the performance or security of the others. Although modern isolation technologies have greatly improved the situation, the limitations of shared hosting remain present in the network layers and the use of shared IP addresses. If attackers gain access to the server by exploiting security vulnerabilities on a neighbouring site, this can increase the security risks to your site as well, even if they do not gain direct access to your data.
A lack of software flexibility is also a significant constraint. PHP settings, such as memory_limit or max_execution_time, are strictly limited for security reasons. These restrictions prevent faulty code from entering an infinite loop and crippling the server. However, when running a more complex online shop or a resource-intensive import process, these limits can quickly become an obstacle. In such cases, no matter how much you optimise the code, the physical limitations of the environment simply won’t allow the process to continue.
Email restrictions and reputation
One of the most sensitive issues with shared hosting is sending emails. Providers impose an hourly limit on the number of emails that can be sent to prevent spam. This limit is usually sufficient for day-to-day business correspondence, but may prove insufficient during a newsletter campaign. As emails are sent from a shared IP address, if another tenant sends emails unethically, the IP address may be blacklisted. This means that your important business emails could also end up in your partners’ spam folders. If stable, high-volume communication is critical for you, our dedicated email service could be the secure solution.
Software and environmental constraints
From a developer’s perspective, the biggest challenges are the lack of root access and the fixed nature of the server configuration. You cannot modify the Apache or Nginx settings, nor can you install custom system-level modules (such as specialised image-processing libraries). You must also adhere to the provider’s schedule when updating PHP versions and installing security patches. This kind of standardisation ensures server stability, but it ties the hands of those who require a bespoke technology stack or specialised environmental settings for their projects. If your development processes have already outgrown these constraints, choose from our flexible VPS plans for complete control.
When is the right time to switch to a VPS? A decision-making checklist
As a website grows, there comes a point where previous optimisation techniques no longer yield noticeable results. If your cPanel statistics show that CPU or RAM usage regularly reaches 80 or 90 per cent, your site will become unstable. At this stage, the limitations of shared hosting are no longer merely theoretical constraints, but technical barriers that hinder conversion rates. As visitor numbers rise, technological requirements may also change. Whether you’re running a Python-based application, need a Node.js environment, or your project requires a custom database structure, you’ll find yourself constrained by the limitations of a shared hosting environment.
Security and data protection can also be decisive factors in your decision. If you handle sensitive customer data or operate in an industry where complete isolation is a fundamental requirement, a shared server may pose a risk. Upgrading means not only more resources, but also business security and scalability for your organisation.
The advantages of VPS versus its limitations
The main advantage of a Virtual Private Server (VPS) lies in the guaranteed amount of resources. Whilst in a shared environment, fluctuations in traffic from neighbouring sites can indirectly affect you, with a VPS, the processor cores and memory are exclusively at your disposal. You gain complete control over the system: with root access, you can install any software and customise the operating system settings to suit your own needs. Whilst shared hosting is like a flexible but restrictive block of flats, a KVM VPS offers you the freedom and security of your own detached, fenced-in house.
Checklist for upgrading
The questions below will help you decide whether the time has come to make a change. It is worth taking an objective look at the current state of your website and your plans for the future:
- Do you find the admin interface (e.g. the WordPress Dashboard) slow, even when there are no visitors on the site?
- Do you regularly encounter 503 or 508 error codes during peak periods or campaigns?
- Do you need custom server-side modules or settings that your provider doesn’t allow?
- Is your website’s traffic and the number of database operations constantly increasing, and are you already feeling the limitations of shared hosting on a daily basis?
If two or more of the above statements apply to you, then it’s time to find out more about the process and benefits of renting a server. Making the switch will not only boost your speed but also, in the long term, eliminate the uncertainty caused by technical limitations.
How can you ensure your website’s future growth?
The limitations of shared hosting are not obstacles, but important milestones that indicate the success of your website. Technical limits, such as CPU, RAM or the number of inodes, essentially safeguard the stability of the server. Beyond a certain point, however, these constraints can hinder you from achieving your business goals. Conscious resource management and making the right decision at the right time to upgrade ensure that your visitors always experience a lightning-fast website. Growth is a natural process, and the technical infrastructure must support this, not hinder it.
With over 10 years’ professional experience, the aWh team is here to help you find the ideal solution for your needs. Our infrastructure is built on lightning-fast NVMe SSD technology, and our expert support team is available 24 hours a day. We’ll help you focus on building your business rather than getting bogged down in technical details. Don’t let old limitations hold back your future success.
Choose stable and fast NVMe hosting from aWh! Build a reliable digital foundation for your business and enjoy the benefits of seamless operation every day.
Frequently Asked Questions
What does it mean for a hosting plan to be ‘unlimited’ if there are still limits?
In marketing, the term ‘unlimited’ most often refers to hosting or traffic, but it never means infinite physical resources. Providers regulate CPU and RAM usage based on the principle of fair use, to ensure that no single user can overload the entire server. The limitations of shared hosting therefore always exist in the background to maintain stability and predictable operation.
How can I check how many resources my website is using?
The easiest way to check your current and past resource usage is via the cPanel interface, under the ‘Resource Usage’ menu item. Here you can view detailed graphs showing trends in CPU, memory and concurrent processes. If you regularly see red warnings or error messages in the statistics, this is a clear sign that your website’s technical requirements have exceeded the limits of your current plan.
What is an inode limit and how can I reduce the number of my files?
The inode limit determines the maximum number of files, folders and emails that can be stored on your hosting account. Each individual item on the server occupies exactly one inode from your quota. The most effective way to reduce the number of files is by deleting unnecessary backups, regularly archiving emails and clearing cache folders. Once the limit is reached, the site will be unable to save new data, which will lead to errors.
Why is my WordPress site slow on cheap shared hosting?
WordPress’s speed depends largely on the amount of CPU and RAM available to run PHP processes. Cheap hosting providers often cram too many users onto a single server, meaning that individual sites are allocated very few resources. A large number of plugins and heavy themes can significantly slow down loading times if the server does not have sufficient free capacity or modern NVMe SSD storage.
Can another website cause my site to go down?
Although modern isolation technologies protect your site from direct downtime, certain indirect effects may still seep through. If a neighbouring website places an extreme load on the server’s network card, or if the IP address is blacklisted for sending spam, you may well feel the effects. This kind of technical dependence on the activities of other tenants is one of the limitations of shared hosting.
How many visitors can an average shared hosting plan handle?
There is no single exact figure for this, as capacity depends on how well the site is optimised and the number of concurrent visitors. A well-cached site with static content can serve up to several thousand visitors a day without any issues. In contrast, a complex online shop may reach its limits even with just a few hundred visitors a day if serving them requires a large number of concurrent database operations and PHP processes.
Can I upgrade to a larger plan without moving to a VPS?
Yes, with most providers, you can choose from several hosting plans, each offering different resource limits to users. A higher-tier shared hosting plan usually provides more memory and a higher CPU percentage for your processes. However, if your site consistently pushes even these expanded limits, switching to a VPS plan will be the safer and more stable solution in the long term.
What is the difference between RAM and the virtual memory limit?
Physical memory is the server’s actual RAM, which your code uses directly and at lightning speed whilst it is running. Virtual memory, on the other hand, may also include slower, disk-based swap space to manage processes that run out of memory. On shared hosting plans, there are limits on both, but running out of physical RAM causes the most noticeable errors and a perceptible slowdown of the website.