How many visits can be made on which package?

This is a question we get asked almost every day. The answer everyone expects is one number. There is no such number, and below you will understand why.

Short answer: the number of visits your hosting account can handle does not depend on the package. It depends on how much work your site requires from the server for each individual visit. The same package can support 50 visits per minute or 5000 visits per minute. The difference is solely in the site.

Think of hosting as a kitchen in a restaurant

You rented the kitchen. The package you took determines how many chefs you have.

Your site is a recipe.

If the recipe is simple, the cook can handle two hundred guests per hour. If you wrote a forty-step recipe, with twelve ingredients that need to be cut by hand, that same chef arrives to serve twenty guests. The kitchen is the same. The cook is the same. The recipe is different.

When you tell us that your site is running slow or that you've got a resource overrun, we look at your recipe. In 90 percent of cases, the problem is there.

What actually happens when someone opens your site

Most people think that a visit means that the visitor downloads images and text from the server. That's just another part of the story, and a less important one at that.

Here's what's really happening, in order:

1. The visitor clicks on the link.
2. The server runs PHP. It is the program that assembles your page.
3. PHP loads WordPress, then the theme, then each of your plugins, one by one.
4. Then he goes to the database and asks it questions. What is the title? What are the categories. What are the products. What are the prices? What's in the basket? On an average WooCommerce site, this can be 300 to 800 questions for a single page.
5. Only when all that is done, the server sends the finished page to the visitor.
6. The visitor only then downloads images, CSS and JavaScript.

Steps 2 through 5 are what consumes the processor. That's your cook. Step 6 is the waiter carrying the plate to the table, and it costs next to nothing.

That's why page size in megabytes is not a measure of load. A static page with large images can be easier on the server than a small WooCommerce page that makes a thousand queries to the database.

Why does the processor throttle?

Each of these steps takes some CPU time. Let's say your site consumes 0.4 seconds of processor time per visit. If you get 100 visitors in the same minute, that's 40 seconds of processor work in 60 seconds. It passes.

Now you install eight more plugins. Each of them is loaded on each page, and each asks its own questions to the database. Your site now consumes 1.8 seconds per visit. The same 100 visitors are now asking for 180 seconds of work in a minute that has 60 seconds.

The server cannot speed up. The server can only create a queue. That's why the site first becomes slow and then starts throwing 508 or 503 error.

The number of visitors has not changed. The site has changed.

Caching is the real answer to the title question

There is a way to skip steps 2 through 5 entirely. It's called caching.

The server compiles your page once, saves it as a finished file, and the next thousand visitors get that finished file. Without PHP. No base. No cook.

In our kitchen, this means that the dishes are already cooked and ready. The waiter just took the plate and took it away.

The difference in numbers is huge. Same package, same site:

• No caching: around 20 to 50 hits per second at best.
• With caching: several thousand visits per second.

Caching already exists and is enabled on our servers. It works at the server level and is called LiteSpeed. But for it to work on your WordPress site, you need to install the free LiteSpeed Cache plugin and configure it. You have instructions in our knowledge base.

This is the one thing on this list that you can do in ten minutes and that makes the biggest difference. If you do nothing else, do this.

Bots are consuming your resources, not your visitors

This surprises almost every client.

There are not only people on your site. There are also automatic programs. Google, Bing, AI crawlers, competitor trackers, price-stealing scrapers, bots looking for security holes.

They don't cash anything and they don't stop. They can open several hundred pages per minute. On a WooCommerce site with filters, bots can make up to 80 percent of the total load.

You don't see them in Google Analytics, because Analytics only counts people. That's why it looks like you have 200 visits a day, and the server is reporting an overage. The statistics that show the truth are in cPanel, not in Analytics.

How to check where you are

You don't need any technical knowledge for this.

1. Resource consumption in cPanel

Log in to cPanel and open Resource Usage. There you can see if and how many times you broke the CPU, memory or number of processes in the last week. If everything is green, the package is enough for you.

2. Server response time

Open PageSpeed Insights and enter your domain. It looks for an item called Server Response Time, or TTFB.

• Below 200ms means caching is working.
• Over 800ms means that PHP is spinning on every visit and the cache is not enabled or not working.

This is the only number from those tools that really tells about server load. Other ratings and points refer to the visitor experience.

What is meant by an optimized site in 2026.

These are the criteria by which Google evaluates your site:

• LCP below 2.5 seconds. How much main content should be seen.
• INP below 200 ms. How quickly the site reacts when you click something.
• CLS below 0.1. How much content jumps while loading.
• TTFB under 200ms. How fast the server responds.
• Images in WebP or AVIF format. Hero image up to 150 KB, regular images up to 60 KB.
• No image wider than 2000 pixels. A 4000 pixel image consumes the phone's memory even when the file is small.
• Number of active plugins below 25. Each plugin is a chef's job.

If you fulfill this and only then get resource overrun, it means that you have really outgrown the package. Then switching to a bigger package makes sense and will solve the problem.

If you don't meet this, a bigger package is just a more expensive way to make the same problem last a little longer.

Who is responsible for what?

We write this part openly, because this is where misunderstandings most often occur.

Imagine you rented an apartment. The owner guarantees that there is electricity, water and correct installations. If you plug fifteen heaters into one outlet in that apartment, the fuse will blow. The installation is not bad. The consumption is too high.

Hosting works the same way.

Our responsibility:

• The server is working, available and fast.
• Caching, PHP, database and network are setup and maintained.
• There is a backup.
• The attack protection works.
• Support responds to you and tells you exactly where the problem is.

Your responsibility:

• What have you installed on your site?.
• How many plugins do you use and what quality are they?.
• In what format and size are you uploading the images.
• Have you turned on and configured the cache plugin.
• Is the theme you bought well written.

When you contact us that the site is running slowly, we will tell you where the cause is. We do it for free and always. But if the cause is in the site, we cannot solve it for you without your consent and without access to your site.

Hosting is not a guarantee that anything you put up will run fast. Hosting is a guarantee that the server under your site is working properly.

Which package should you take?

Start from the basics. That goes for almost everything.

Switching to a larger package is possible at any time, it takes a few minutes and you only pay the difference. There's no reason to buy something bigger in advance just in case you need it.

Take the bigger package immediately only if you know that you are entering with serious advertisements, say over 100 euros per day, or if you are transferring a store that already has traffic.

You also have a free trial period of 7 days. Use it, set up a site, let it run and look at Resource Usage. That's the most accurate answer you can get, because it's a measurement on your site, not an estimate.

If this seems like too much for you

It's totally fine if you don't want to deal with it. Most people who have a website are not developers and they don't need to be.

We have a website optimization service. We go through all of the above, set up caching, tidy up images, remove redundant plugins and send you a before and after report.