Shared hosting accounts per server is 40 to 50 websites per 1 GB of RAM, as long as no more than 10% of the hosted websites get persistent traffic, according to Plesk. Check your current server's total memory and compare it against the number of active sites using a Resource Isolation Test.
Review Hosting Bureau directs readers to evaluate the impact of neighbors on shared hosting by checking the server's physical hardware limits. Shared hosting accounts per server can suffer from resource contention, which is when multiple sites compete for the same CPU power at the exact same time.
- What it is
- Shared hosting accounts per server represent the total number of websites running on a single physical machine
- Who it suits
- Websites with low traffic volume that require cost-effective hosting without dedicated hardware
- What you need first
- A full site backup file containing all database tables and media assets for migration
- What it costs to change later
- Data remains on the original server unless a manual migration of the database and files occurs
- First thing to check
- The server load average metric shows how many concurrent processes are currently active on the hardware
Capacity limits for shared hosting
A single server can host hundreds or even thousands of shared hosting accounts depending on the hardware. According to Plesk documentation, Plesk recommends 1 GB of RAM for every 40 to 50 websites, as long as no more than 10% of the hosted websites get persistent traffic. This limit depends on how a provider chooses to oversell the physical resources.
A VPS provides more dedicated resources than shared hosting
A VPS is a Virtual Private Server that carves out a private slice of a physical machine. It works by using software to ensure your site has its own dedicated portion of memory and processing power. This matters because you should switch to a VPS when your site needs more stability than a shared environment can provide.
CPU and RAM determine the ceiling
The available cpu and ram determine the ceiling for every shared hosting account. A host might snapshot a server to create a baseline, but high traffic on a neighboring site can still impact your speed. You can compare shared hosting with cloud hosting to confirm your specific limits or check your hosting plan for a stated number of concurrent connections.
Maximum number of websites per server
The maximum number of websites per server is determined by the host’s ability to allocate enough memory and processing power to each account. A provider might host 500 websites on one machine if the traffic is low, but this number drops if the sites require heavy scripts to resolve requests. You should verify the specific capacity of your host to ensure your site maintains the performance standards defined in the Core Web Vitals thresholds published by Google.
How do neighboring websites on a shared server affect my site speed?
Neighboring websites on a shared server affect your site speed by competing for limited hardware resources. If a neighbor experiences a sudden spike in traffic, your site might experience increased latency, lower available bandwidth, or higher CPU usage. This occurs because the physical hardware must process every request from every account on that specific machine.
Neighbor impact on shared hosting accounts
- CPU usage spikes occur when a neighboring site runs heavy scripts or processes large amounts of data simultaneously.
- Bandwidth limits apply to the total data the server can move, meaning a high-traffic neighbor can saturate the connection.
- Latency increases as the server takes longer to queue and execute requests during periods of high demand.
- Plesk recommends 1 GB of RAM for every 40 to 50 websites, as long as no more than 10% of the hosted websites get persistent traffic. Plesk is a web hosting control panel designed to manage websites and servers.
- A shared hosting account remains subject to these resource constraints regardless of the specific website content.
Persistent traffic determines how many sites a server can hold
Persistent traffic is the steady flow of visitors to a website over a long period. It is calculated by measuring how many websites on a server are constantly receiving hits rather than just occasional visits. This matters because a server can host more accounts if only a small portion of those sites are busy at all times.
Availability of free shared hosting for testing
Many providers offer a free shared hosting account for a limited period to let users test performance. These trials allow users to check how a site behaves or how to install git on shared hosting before committing to a paid plan.
Impact of traffic spikes on shared resources
A neighbor with a massive traffic spike can slow down your site because they share the same physical hardware. When one site consumes a large portion of the server’s processing power or memory, other sites experience delays. This happens because the server must queue requests and distribute limited resources among all active users.
Host balances CPU and RAM demands
High server load occurs when the demand for CPU or RAM exceeds the available capacity. A shared web hosting account relies on the host to balance these demands fairly. If a neighbor’s site is not properly optimized, it might consume more than its fair share of the available bandwidth.
Impact of neighbor traffic spikes on shared resources
Resource contention happens when multiple websites compete for the same hardware components simultaneously. This competition can cause your site to lag or fail to load during peak periods for other users. To maintain stability, many providers use a shared web hosting account structure that limits the maximum resources any single user can grab.
What are the differences between cPanel and Plesk for managing shared hosting accounts?
The differences between cPanel and Plesk involve their underlying operating systems and interface designs. cPanel operates on Linux and uses a traditional graphical interface for web management. Plesk supports both Windows and Linux environments and utilizes a more modern, modular layout for managing shared hosting accounts.
Memory limits for 50 websites
Suppose a host manages 50 websites on a Linux server. If the host allocates 1 GB of RAM to the server, each site has a 20 MB limit. If 10 websites receive persistent traffic, they consume 200 MB of the total memory.
Server control panel comparison
| cPanel Management | Plesk Management | Shared Hosting Accounts |
|---|---|---|
| Supports Linux systems | Supports Windows and Linux | cPanel shared hosting accounts |
| Uses traditional layout | Uses modern modular layout | Plesk shared hosting accounts |
| Replicates standard workflows | Provides flexible configurations | Shared web hosting accounts |
| Audits Linux permissions | Audits cross-platform permissions | Shared hosting email account |
Differences between standard and merchant accounts
Standard shared hosting accounts limit the number of websites a user can host on one plan. Merchant accounts provision higher limits and allow a user to resell the hosting space to multiple clients. Before choosing, compare shared hosting with WordPress hosting to see how merchant accounts often replicate extra security layers to audit several sub-users on a single server.
Standard limits for a shared hosting package
Standard shared hosting packages typically limit disk space, bandwidth, and inbound traffic. These limits vary by provider, but most plans partition resources to ensure stability for all users. No universal rule defines the exact capacity for every merchant account, as limits depend on the specific hosting tier selected.
Shared hosting package limits
- Disk space limits determine the total amount of data a user can store on the server.
- Bandwidth limits restrict the amount of data transferred from the server to visitors.
- Inbound traffic limits control the volume of data sent to the server for uploads or updates.
- Plesk recommends 1 GB of RAM for every 40 to 50 websites, as long as no more than 10% of the hosted websites get persistent traffic.
- Shared web hosting accounts packages often throttle performance if a single site consumes disproportionate resources.
Typical limits for shared hosting plans
Hosting providers use these limits to sandbox individual sites and prevent a single account from exhausting server resources. While small sites stay well under these caps, high-traffic sites may hit limits and require a move to a dedicated environment.
Choose a shared hosting provider that guarantees your site speed
Selecting a shared hosting plan requires balancing your traffic needs against the server capacity and performance limits of the hosting environment.
Steps to evaluate shared hosting performance
- Calculate your expected persistent traffic percentage. Identify the percentage of your websites that receive constant traffic. Ensure this figure remains below 10% of the total hosted sites.
- Determine your required RAM based on site volume. Check the Plesk documentation to see that 1 GB of RAM is recommended for every 40 to 50 websites.
- Request the server's total RAM and site limit from your provider. Ask your hosting provider for the total RAM and the maximum number of accounts per server. Compare these to the Plesk documentation recommendations.
- Verify the Largest Contentful Paint requirement. Largest Contentful Paint is a metric that measures the time it takes for the largest piece of content to appear on a screen. Check your site speed using Google Core Web Vitals. The Largest Contentful Paint should occur within 2.5 seconds of the page starting to load.
- Confirm the Interaction to Next Paint threshold. Interaction to Next Paint is a metric that measures the time from a user action to the next visual update on the screen. Test your site's responsiveness. A page should have an Interaction to Next Paint of 200 milliseconds or less at the 75th percentile.
Frequently asked questions
- What are the requirements for a Windows shared hosting account compared to Linux?
- Plesk supports both Windows and Linux environments for shared hosting accounts. The system uses a modern, modular layout to manage these accounts across different operating systems.
- When should I move from a shared hosting account to a VPS?
- Move your site to a dedicated environment if a high-traffic site consumes disproportionate resources. This happens when a shared web hosting account hits limits like bandwidth or CPU capacity.
- What happens if a neighbor experiences a sudden traffic spike?
- Neighbor traffic spikes cause your site to experience increased latency or lower available bandwidth. This occurs because the physical hardware must process every request from every account on that specific machine.
- Can I test a shared hosting account before I buy it?
- Many providers offer a free shared hosting account for a limited period to test performance. These trials let you check how a site behaves before you commit to a paid plan.