How much RAM, CPU and storage does your site need?

A brochure site needs 5–10 GB of storage and the resources of a shared hosting plan, a growing blog 10–30 GB, and a small to mid-sized online store at least 20–40 GB plus guaranteed RAM and CPU. Below we explain how much resource you need for a site by type and traffic, so you don't pay for what you don't use or get stuck at the first traffic spike.

What RAM, CPU and storage actually mean

Before the numbers, here are the three terms in brief:

• CPU (processor): builds the pages, runs the code (PHP) and processes orders. It matters most when many visitors arrive at once.
• RAM (memory): the temporary workspace. The more you have, the more requests and processes the server can handle at once without stalling.
• Storage (disk): where the site's files live, meaning images, the database, email and backups. On an NVMe drive, data is read much faster than on classic storage.

The simple rule: storage depends on how much content you have, while RAM and CPU depend on how much traffic you serve at the same time. A small site with heavy traffic needs power, not necessarily space.

How much resource you need for a site, by type

Here are three typical cases, from lightest to most demanding. The figures are a guide: a poorly optimized store can use more than a bigger one that's well maintained.

Brochure site (company, freelancer, portfolio)

A few pages, a contact form, maybe a small blog. The needs are modest: 5–10 GB of storage is plenty, and the memory and CPU of a shared hosting plan cover a project like this easily. With WordPress, a clean theme and a few plugins, you're fine. Most brochure sites will never need more.

Blog or content site with growing traffic

An active blog, a local news site or a platform with new articles every week collects images, comments and a bigger database over time. Here we recommend 10–30 GB of storage and, more importantly, a plan with somewhat more memory and CPU, so pages stay fast when an article takes off. LiteSpeed's cache helps a lot: it serves pre-built pages without starting PHP on every visit.

Online store

This is where things change. A store (WooCommerce, PrestaShop and so on) needs more power, because every cart, customer login and order is a dynamic process that can't be served from cache. You also have a large catalog, images and a database that keeps growing. For a small or mid-sized store, start from at least 20–40 GB of storage and a plan with clearly allocated resources (guaranteed RAM and CPU, not "unlimited" on paper). As sales grow, you'll need an isolated environment, which is what a VPS gives you.

How to estimate traffic and peaks

You size resources for peaks, not for the daily average. A site might have 100 visitors a day, but if 80 of them arrive in the same hour (after a newsletter or an ad), the server has to cope with that hour.

A few practical pointers:

• Simultaneous visitors, not monthly ones. The useful question isn't how many visitors you get a month, but how many can be on the site at once at peak time.
• Static or dynamic content. Pages served from cache (articles, info pages) use little. Carts, accounts, searches and product filters use real CPU and RAM.
• Campaigns and seasons. Black Friday, a press mention or a successful ad can multiply your traffic within hours. Leave headroom for those moments.

If you're starting from scratch with no data, that's normal. Begin with an NVMe web hosting plan that fits your type of site and watch usage over the first months. It's easier to scale up when needed than to pay for unused resources from day one.

Signs you need more resources

Your site tells you fairly clearly when the plan has become too small:

• Pages load more and more slowly, especially at peak hours or during campaigns.
• "Resource limit reached" or 503 errors: you've hit the plan's memory or process limit.
• The admin panel (WordPress, for example) is slow even though the public side looks fine, which is typical of large databases or stores.
• Storage is nearly full, usually because of backups, email or unoptimized images.
• You've passed a few hundred products or run several sites on one account, and they start taking resources from each other.

Before you buy more power, check whether the real problem is missing optimization: oversized images, unnecessary plugins, no caching. A good clean-up often delays an upgrade by months. If you've already added resources and the problem persists, you do need a stronger environment.

When to move from shared hosting to a VPS

Shared hosting is enough for most sites: it's simple, managed by the provider and cheap. At some point, though, you want guaranteed resources and more control, and that's where a VPS (virtual private server) comes in.

Consider a VPS when:

• Your store has steady traffic and you can't afford slowdowns at peak hours.
• You want dedicated RAM and CPU without sharing the server with other customers.
• You need special setups (specific software versions, your own services, several sites under full control).
• You want to add resources on demand as the business grows.

The advantage of a VPS is scalability: you start with a configuration that fits today and enlarge it when you need to, without complicated moves. See the options on our scalable VPS cloud servers page, where you pick how much power you need and adjust it as you go.

Choose by real need

Start from your type of site and realistic traffic, not from the most expensive plan "just to be safe". A brochure site runs well on shared hosting, a growing blog needs a somewhat bigger plan, and a serious store will reach a VPS sooner or later. If you're not sure what fits, our support team answers in Romanian and will help you choose. See the web hosting plans: migration is free and you can move to a bigger plan at any time.