Hosting · Explainer
How Many Visitors Can Shared Hosting Handle?
Short answer
Shared hosting can handle about 10,000 to 400,000 visits a month, depending on the plan, caching and how heavy each page is. Entry plans suit small blogs and brochure sites, while top shared plans suit busier sites with good caching. The real limit is rarely the visit number alone; CPU time, RAM, PHP workers and file counts decide when a site slows down.
Key takeaways
- Shared hosting has no single visitor limit; each plan pairs a monthly visit estimate with CPU, RAM and file limits.
- Entry shared plans are sized for about 10,000 to 40,000 visits a month, while top shared plans reach about 400,000.
- Caching matters more than the monthly total, because cached pages use little CPU and uncached pages use far more.
- SiteGround caps StartUp at 1,000 CPU seconds an hour, while Hostinger caps Premium at 40 PHP workers.
- WooCommerce stores, logged-in users and heavy plugins use more server time per visit than a plain blog.
- Check CPU, memory and worker use in your host panel before you upgrade, so you fix the real limit.
How many visitors can shared hosting handle?
Shared hosting can handle about 10,000 to 400,000 visits a month, depending on the plan, caching and page weight.
That range comes from the visit estimates hosts publish on their own plan pages, as of November 2026. SiteGround lists about 10,000 visits a month for StartUp, about 100,000 for GrowBig and about 400,000 for GoGeek.
Bluehost lists about 40,000 visits a month for Starter, about 200,000 for Business and about 400,000 for eCommerce Essentials.
Those numbers are estimates, not hard caps. A light blog with caching can pass its estimate without trouble, while a heavy store can struggle below it. If you are still choosing a plan, read our guide on how to choose WordPress hosting before you compare visit figures alone.
What does “monthly visits” mean on a hosting plan?
A monthly visit estimate is the host's rough guide to the traffic a plan is sized for, not a meter that stops your site at an exact number.
Hosts count visits in different ways, and most do not publish the exact method. SiteGround says its figure is an approximate estimate of the maximum visits a plan can handle when sites use its out-of-the-box caching. That condition matters, because caching changes how much work each visit creates.
Do not treat the estimate as a guarantee. It helps you compare plans from the same host, but it does not tell you how many visitors arrive at once, how many pages each visitor reads, or how much work each page needs.
How many visitors can shared hosting handle at the same time?
Shared hosting handles far fewer visitors at the same time than it handles in a month, because the monthly total spreads across days and hours.
A site with 30,000 visits a month averages about 1,000 visits a day, or about 40 visits an hour if traffic were even. Real traffic is not even.
A post shared in the morning can bring 200 visitors in one hour, and that hour is the one that tests your plan.
The limit that bites at peak time is concurrency, not the monthly total. Only uncached requests need a PHP worker, CPU time and RAM at that moment.
Cached pages can serve many readers at once with little server work, which is why two sites with the same monthly total can behave very differently.
What limits shared hosting first: CPU, RAM, or PHP workers?
CPU time usually limits shared hosting first, followed by PHP workers and RAM, because every uncached WordPress page must run PHP and query the database.
SiteGround measures CPU in CPU seconds, which is the processor time your scripts use. Its fair-use page sets red-flag values of 1,000 CPU seconds an hour on StartUp, 2,000 on GrowBig and 4,000 on GoGeek.
Daily values are 10,000, 20,000 and 40,000. That page was last updated on 12 October 2021, so ask support to confirm the current values for your plan.
Hostinger measures the same problem in different units. Its plan parameters page lists Premium at 1 CPU core, 2 GB of RAM and 40 PHP workers.
Unlimited lists 2 cores, 3 GB of RAM and 60 PHP workers. A PHP worker runs one uncached request at a time, so slow pages hold workers longer and queue the next visitors.
RAM and file counts matter too. SiteGround allows up to 768 MB of RAM per process on all three shared plans, and sets inode limits of 200,000 files on StartUp, 400,000 on GrowBig and 600,000 on GoGeek.
An inode is one file or folder, so backups, cache files and email can push a site toward that limit even when disk space remains.
How many visitors can each shared plan handle?
Entry shared plans suit about 10,000 to 40,000 visits a month, mid plans suit about 100,000 to 200,000, and top shared plans suit about 400,000.
The table below uses each host's own plan page, as of November 2026. Prices are intro prices for the longest prepaid term, with renewal prices after the first term.
| Host and plan | Visits a month (estimate) | Storage | Key limit | Intro / renewal, as of November 2026 |
|---|---|---|---|---|
| SiteGround StartUp | About 10,000 | 10 GB | 1,000 CPU seconds an hour | $1.99 / $17.99 a month |
| SiteGround GrowBig | About 100,000 | 50 GB | 2,000 CPU seconds an hour | $3.99 / $29.99 a month |
| SiteGround GoGeek | About 400,000 | 100 GB | 4,000 CPU seconds an hour | $5.99 / $44.99 a month |
| Bluehost Starter | About 40,000 | 10 GB NVMe | 10 websites | $3.99 / $9.99 a month |
| Bluehost Business | About 200,000 | 50 GB NVMe | 50 websites | $6.99 / $13.99 a month |
| Bluehost eCommerce Essentials | About 400,000 | 100 GB NVMe | 100 websites | $14.99 / $21.99 a month |
| Hostinger Premium | About 25,000 | 20 GB SSD | 40 PHP workers, 1 core, 2 GB RAM | About $2.49-$2.99 / about $10.99-$11.99 a month |
| Hostinger Unlimited | About 100,000 | 50 GB NVMe | 60 PHP workers, 2 cores, 3 GB RAM | About $3.49-$3.99 / about $16.99 a month |
SiteGround's prices come from its own hosting prices page, which lists StartUp at $1.99 a month for the first prepaid 12 months and $17.99 on renewal.
Bluehost's prices come from its own shared hosting prices page, which lists Starter at $3.99 a month on a 36-month term and $9.99 on renewal.
Hostinger prices vary by country store and sale, so the table shows a range for a 48-month term, as of November 2026. Check the checkout page for the price that applies to your store before you decide.
How does caching change how many visitors you can handle?
Caching raises the number of visitors shared hosting can handle, because a cached page is served without running PHP or querying the database for every visit.
WordPress Developer Resources explains the three main cache layers in plain terms. A page cache serves complete rendered pages, an object cache stores database and query results, and an opcode cache stores compiled PHP code. Each layer removes work from a later visit.
The same source warns that without a caching solution, performance will slow to a halt as page requests stack up, and can crash the web or database server.
That is why a cached blog can handle far more readers than an uncached one on the same plan. For step-by-step speed work, see how to speed up WordPress.
A CDN adds a second layer of caching. Cloudflare explains that a CDN is a group of servers that caches content close to end users, and that caching reduces the amount of data an origin server must provide.
That reduces both bandwidth use and origin load. If you want cost figures for that layer, read how much a CDN costs for WordPress.
How do WooCommerce stores and logged-in users change the number?
WooCommerce stores and logged-in users handle fewer visitors on the same shared plan, because their pages cannot be cached in the same way as public blog pages.
Cart, checkout and account pages must run fresh for each shopper, so each visit uses PHP, memory and database time.
WooCommerce's server requirements list PHP 8.3 or greater, tested up to PHP 8.4, MySQL 8.0 or greater or MariaDB 10.6 or greater, and a WordPress memory limit of 256 MB or greater.
Logged-in readers have the same effect on a smaller scale. Member areas, course lessons and forum pages run PHP for each view, while public posts can sit in the page cache. A site with 5,000 logged-in visits a month can use more CPU than a blog with 30,000 cached visits.
How can you check how many visitors your site can handle?
Check your host's resource charts and your analytics together, because traffic alone does not show which limit you are close to.
Start with your host panel. SiteGround shows CPU seconds under Services, then Settings, then Statistics, then CPU Seconds in the Client Area.
Hostinger shows CPU, memory, I/O, PHP workers, disk and inodes under Websites, then Dashboard, then Hosting plan, then Resources Usage. Look for peaks, not monthly averages, and note which chart hits its red line first.
Then check your server baseline in WordPress. WordPress.org recommends PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.0 or greater, and HTTPS support.
You can check your PHP version in WordPress under Tools, then Site Health, then the Info tab, then the Server section. If your PHP version is below 8.3, ask your host to move you to a supported version before you judge traffic capacity.
Also count the visits that never reach a human reader. Bots, crawlers and uptime checks can use CPU and workers just like visitors. Our guide on how AI crawlers affect WordPress bandwidth explains how crawler traffic adds to that load.
When should you move off shared hosting?
Move off shared hosting when you hit CPU, worker or memory limits often, even after caching, image sizing and plugin cleanup.
Signs include slow pages at peak hours, 503 or 508 errors, and warnings from your host about resource use.
A 508 error means the account hit a resource limit, while a 503 error often means the service is briefly unavailable because workers or memory ran out. Occasional spikes are normal, but repeated limits in the same week point to a plan that is too small.
Do not move only because your monthly visits passed an estimate. If your resource charts stay well below their limits, your plan still has room. If charts hit their limits while visits are modest, fix the heavy pages first, then move if the limits keep returning.
What mistakes should you avoid?
The most common mistake is treating “unlimited” bandwidth or visits as unlimited server power, when CPU, RAM and workers still have fixed caps.
Avoid these errors:
- Comparing only monthly visit numbers, and ignoring CPU seconds, PHP workers and inodes.
- Running a store or member site on an entry plan with no caching, then blaming traffic for the slowdown.
- Keeping unused plugins, old backups and large media libraries, which raise CPU, memory and file counts.
- Ignoring bot and crawler traffic, which can use a large share of a small plan.
- Choosing a plan by intro price alone, without noting the renewal price that applies after the first term.
Cloudflare's free and paid plans can help with caching and bot pressure, so compare Cloudflare Free vs Pro for WordPress before you add a CDN.
Keep a backup you can restore before you change caching or hosting settings, as explained in how to back up WordPress.
Frequently asked questions
Can shared hosting handle 100,000 visitors a month?
Yes, on the right plan. Mid and top shared plans are sized for about 100,000 to 400,000 visits a month, with SiteGround GrowBig at about 100,000 and Bluehost Business at about 200,000. A cached blog reaches that range more easily than a store or member site, because uncached pages use more CPU and workers per visit.
What happens when shared hosting hits its limit?
Your site slows down first, then visitors may see 503 or 508 errors when workers, memory or CPU run out. Some hosts send a warning and limit the account for a time, while others ask you to upgrade. Check your host panel for the exact chart that hit its limit, then fix caching and heavy pages before you pay for a bigger plan.
Does unlimited bandwidth mean unlimited visitors?
No. Unlimited bandwidth means the host does not meter data transfer on that plan, but CPU, RAM, PHP workers and file counts still have fixed caps. A site can stay within its bandwidth allowance and still hit a CPU or worker limit during a traffic spike. Read the plan limits, not only the word unlimited, before you judge capacity.
How many visitors can shared hosting handle at once?
There is no single number, because it depends on caching and page weight. Cached pages can serve many readers at once with little server work, while uncached pages each need a PHP worker and CPU time. Hostinger Premium allows 40 PHP workers, so about 40 slow uncached requests can run at once before new requests must wait in line.
Is shared hosting enough for a WooCommerce store?
It can be enough for a small store with light traffic and good caching, but cart and checkout pages cannot be cached like blog posts. WooCommerce lists PHP 8.3 or greater and a WordPress memory limit of 256 MB or greater in its server requirements. If checkout slows at peak times or you hit CPU limits often, move to a plan with more workers and memory.
Sources
- Requirements WordPress.org
- What is a Fair Use of SiteGround Web Hosting Services? SiteGround
- Compare Shared Web Hosting Plans and Cost Bluehost
- Parameters and limits of hosting plans in Hostinger Hostinger
- WooCommerce Server Recommendations WooCommerce
- What is a CDN? Cloudflare
- Optimization WordPress Developer Resources
- SiteGround hosting plans and prices SiteGround
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
