How Much RAM and CPU Does Your Website Actually Need?

Laptop screen showing two glowing gauge dials representing CPU and memory usage at a moderate healthy level

This page contains affiliate links. If you make a purchase through one, we may earn a commission at no extra cost to you.

Picking a VPS plan mostly comes down to two numbers: how much RAM and how many CPU cores you actually need. Overbuy and you’re wasting money every month; underbuy and you’ll be dealing with the 502/503 errors that come from a server running out of headroom under load. Here’s how to actually estimate it.

RAM Is Usually the First Bottleneck, Not CPU

For most small-to-medium websites — a WordPress site, a small business site, a blog — running out of RAM tends to happen before running out of CPU, since each visiting request and each background process (database queries, caching, PHP execution) claims a chunk of memory for its duration. A site that’s technically getting enough CPU cycles can still slow to a crawl or start throwing errors if RAM is maxed out and the server starts swapping to disk or killing processes to free memory.

Rough Starting Points by Site Type

  • A small brochure site or blog with light, steady traffic generally runs comfortably on a modest amount of RAM and a couple of CPU cores — this is the entry-level tier on most VPS providers, and it’s genuinely enough for a large share of small sites.
  • A WordPress site with regular traffic, several plugins, and some dynamic functionality (forms, a membership area, e-commerce) needs meaningfully more headroom, since each active plugin and each dynamic page request adds real memory overhead on top of the baseline.
  • A site running its own database-heavy application, or multiple sites on one server needs the most resources of the three, since database operations and multiple concurrent codebases compound the RAM and CPU demand well beyond a single simple site.

The Honest Way to Find Out: Watch Your Actual Usage

Guidelines like the above are a reasonable starting point, not a substitute for checking your actual server. Most hosting control panels show live or historical CPU and RAM usage graphs — after your site has been running for a couple of weeks under normal traffic, check whether your usage is sitting comfortably below your plan’s limit, regularly spiking close to it, or consistently maxed out. Regularly brushing up against your limit is the real signal to upgrade, not a guess made before you have any actual data.

Why Starting Smaller Is Usually the Better Mistake to Make

If you’re genuinely unsure, sizing down slightly and upgrading later is the lower-cost mistake compared to overbuying from day one. Most VPS providers, including Contabo, let you scale a plan up without a full server migration, so starting on a smaller tier and moving up once you have real usage data isn’t a wasted step — it’s the more honest way to size this than guessing high and paying for headroom you may never use. See our best cheap VPS under $10/month guide for what a reasonable entry-level tier actually includes.

Does more RAM matter more than more CPU cores for a typical website?

For most small-to-medium sites, yes — running out of RAM tends to cause problems before running out of CPU, since every request and background process claims memory for its duration.

How do I know if my current VPS plan is undersized?

Check your hosting control panel’s CPU and RAM usage graphs after a couple of weeks of normal traffic. Regularly spiking close to your plan’s limit, or sitting consistently maxed out, is the real signal to upgrade.

Is it better to start on a bigger plan than I think I need?

Generally no — starting smaller and upgrading once you have real usage data is the lower-cost mistake compared to overbuying from day one, especially since most providers let you scale up without a full migration.