Web hosting companies often make bigger resource numbers look automatically better.
One plan has 20 GB of storage. Another has 100 GB. A VPS offers four CPU cores and 8 GB of RAM. A cloud plan promises more PHP workers, higher inode limits, and generous bandwidth.
For a new website owner, those specifications can make it seem safer to buy more than you need.
In reality, a normal WordPress blog may use only a fraction of the storage included with an entry-level plan. At the same time, an ecommerce store can experience performance problems despite having plenty of unused disk space because it is running out of CPU, RAM, or PHP processing capacity.
If you are wondering how much web hosting do I need, there is no single number based solely on monthly visitors. You need to consider what the website does, how much of it can be cached, how many people use it at the same time, how many files it stores, and how resource-intensive its software is.
This guide explains the main hosting resources in practical terms and provides realistic starting points for blogs, business sites, portfolios, WooCommerce stores, and larger content websites.
Web Hosting Resources at a Glance
| Resource | What It Controls | When You Need More |
|---|---|---|
| Storage | How much website data you can store | Large media libraries, multiple sites, downloads |
| Bandwidth/Data Transfer | How much data visitors receive | More traffic or larger pages |
| RAM | Working memory available to processes | Dynamic sites, ecommerce, heavy applications |
| CPU | Processing capacity | More simultaneous or computationally demanding requests |
| Inodes | Number of files and folders | Many images, cache files, emails, backups, multiple sites |
| PHP Workers | Simultaneous uncached PHP requests | WooCommerce, memberships, logged-in users, uncached pages |
| Database Resources | Capacity for queries and connections | Large or highly dynamic WordPress sites |
The important point is that these limits solve different problems.
Buying more storage will not fix a CPU bottleneck, and adding RAM will not solve an inode limit caused by hundreds of thousands of unnecessary cache files.
How Much Storage Does a Website Need?
Storage is the amount of disk space available for your website files.
It can include:
- WordPress core files
- themes
- plugins
- uploaded images
- documents
- database files
- logs
- caches
- locally stored backups
- email, depending on the hosting provider
A simple WordPress site usually does not need huge amounts of storage.
A five-page business website might occupy less than a few gigabytes even after accounting for WordPress, plugins, and images. A blog containing hundreds of well-optimized images can remain comfortably below 20 GB.
Storage becomes more important for photographers, large publishers, download sites, multiple-site accounts, and businesses storing large media libraries.
SSD vs NVMe storage
Most modern hosting now uses solid-state storage rather than traditional mechanical hard drives.
An SSD, or solid-state drive, stores data electronically and provides much faster access than older spinning disks.
NVMe describes a storage protocol designed for modern solid-state storage using PCIe connections. NVMe drives can provide substantially higher throughput and lower latency than older SATA-based SSD technology.
For a normal blog, the difference between SSD and NVMe storage is rarely a reason to abandon an otherwise good hosting plan. Website performance also depends on CPU, RAM, caching, database efficiency, software, and network conditions.
NVMe becomes more valuable for workloads involving frequent disk and database activity.
Think of storage type as part of the performance picture rather than a guarantee of a fast website.
How Much Storage Should You Buy?
As a practical starting point:
| Website Type | Reasonable Starting Storage |
|---|---|
| Small portfolio | 5 to 10 GB |
| New WordPress blog | 10 to 20 GB |
| Small business site | 10 to 20 GB |
| Established content blog | 20 to 50 GB |
| WooCommerce store | 20 to 50+ GB |
| Image-heavy publication | 50 to 100+ GB |
These are planning ranges, not technical requirements.
A photography portfolio containing large original files could require more storage than a 5,000-page text-focused publication.
Before upgrading because disk usage is high, check what is consuming the space. Old backups, staging sites, cache folders, unused themes, and unnecessary image copies can occupy far more storage than the active website itself.
Bandwidth Is Not the Same as Storage
Storage measures what sits on the server.
Bandwidth, as hosting companies commonly use the term, usually refers to the amount of data transferred when visitors use the website. Technically, bandwidth describes network capacity, while hosting plans often use “bandwidth” to mean monthly data transfer. Cloudflare makes the same distinction in its documentation.
Imagine your average page transfers 2 MB of data.
If the site receives 50,000 pageviews:
50,000 × 2 MB = 100,000 MB
That is roughly 100 GB of data transfer before accounting for bots, downloads, admin traffic, and other requests.
If you reduce the average page size to 1 MB, equivalent visitor activity could use roughly half as much transfer.
This is one reason image optimization matters.
A CDN can reduce origin bandwidth
A Content Delivery Network can cache resources such as images, CSS, JavaScript, and sometimes HTML on servers closer to visitors.
When the CDN serves a cached file, the hosting origin does not need to deliver that file every time. This can reduce both latency and the amount of traffic reaching your main server.
A globally distributed content site can therefore serve a surprising amount of visitor traffic without equivalent amounts of data reaching the origin server.
RAM Explained Without the Server Jargon
RAM is the server’s short-term working memory.
Applications use it while they are running.
For WordPress, memory can be consumed by:
- PHP processes
- database services
- caching
- WordPress plugins
- control-panel software
- web-server processes
- background jobs
Insufficient RAM can lead to slower processing, failed processes, swapping, or server errors depending on the hosting environment.
More RAM is particularly useful for dynamic applications where many things happen at once.
A static portfolio site can operate with relatively modest resources. A WooCommerce store handling customers, carts, checkout sessions, inventory queries, payment callbacks, and administrative processes needs more working capacity.
How much RAM do you need?
Shared hosting often does not present RAM in the same straightforward way as a VPS. The provider may simply give the account a resource allowance.
If you are choosing a VPS or cloud server, these are reasonable starting points rather than guarantees:
- 1 to 2 GB: small WordPress site or lightweight application
- 2 to 4 GB: established WordPress site or several small sites
- 4 to 8 GB: moderately busy WooCommerce or dynamic site
- 8 GB and above: larger applications and high-traffic dynamic workloads
Optimization can change these requirements considerably.
A cached blog can handle far more visitors per gigabyte of RAM than an inefficient dynamic application.
What Do CPU Cores Actually Do?
The CPU performs computational work.
For a website, that includes tasks such as:
- executing PHP
- processing database queries
- compressing content
- running WordPress cron jobs
- generating pages
- processing ecommerce activity
- handling backend tasks
A hosting plan with more CPU resources can generally process more work simultaneously or complete computational tasks faster, depending on the underlying processor and architecture.
Reaching a CPU limit can cause requests to queue rather than being handled immediately. Hostinger’s current resource documentation, for example, notes that reaching CPU limits can make websites feel sluggish because visitor requests begin waiting for processing capacity.
How many CPU cores do you need?
Again, shared hosting does not always translate cleanly into dedicated CPU cores.
For VPS and cloud plans, a rough starting framework is:
| Website | Suggested Starting CPU |
|---|---|
| Small blog | 1 vCPU |
| Established blog | 1 to 2 vCPU |
| Business WordPress site | 1 to 2 vCPU |
| Moderate WooCommerce store | 2 to 4 vCPU |
| Large dynamic site | 4+ vCPU |
A highly optimized ecommerce store may outperform a badly configured store with twice the CPU.
Treat CPU requirements as something to monitor rather than a number you can determine perfectly before the site exists.
What Are Inodes?
An inode is essentially a record associated with a file or directory on the hosting account.
For practical hosting purposes, think:
one file or folder = approximately one inode
A website can therefore run into an inode limit even when plenty of gigabytes remain available.
Hostinger’s documentation gives a useful real-world example. Its current web hosting plans have separate limits for disk space and inodes, with published inode allowances ranging from hundreds of thousands upward depending on the plan.
Inodes can accumulate through:
- WordPress files
- plugin files
- themes
- image thumbnails
- cache files
- log files
- staging copies
- locally stored backups
Hostinger notes that reaching an inode limit can prevent new files or folders from being created even if disk storage remains available.
This is particularly relevant when hosting many WordPress installations under one account.
Do not judge a multi-site hosting plan only by its advertised storage.
What Are PHP Workers?
WordPress is built with PHP, and dynamic WordPress requests need PHP processing.
Hosting companies may describe the processes handling those requests as PHP workers or PHP threads.
The simplest explanation is:
One PHP worker handles one active PHP request at a time.
If every available worker is busy, additional dynamic requests wait.
Kinsta’s current documentation uses the term PHP threads, noting that each handles one incoming request at a time. It also points out that cached content can bypass PHP processing, while uncached requests and database-changing actions require PHP.
This is why PHP worker capacity matters much more for some websites than others.
A normal blog
Most article pages can be aggressively cached.
One generated copy can be served repeatedly without asking WordPress to rebuild the page for every visitor.
WooCommerce
Many interactions are unique to individual customers:
- cart
- checkout
- account pages
- personalized sessions
- inventory changes
- payment processes
Those requests cannot always be handled like a cached public article.
The store therefore places much greater demand on PHP processing even with fewer total visitors.
More PHP workers do not automatically mean a faster site. Slow code and slow database queries keep each worker occupied longer, reducing how many requests the same worker pool can process.
Databases Matter More as WordPress Becomes Dynamic
WordPress stores posts, settings, users, orders, product data, comments, and other information in a database.
A small blog’s database may be relatively modest.
An ecommerce site can generate much more activity through:
- orders
- customers
- products
- sessions
- inventory
- analytics records
- plugin tables
Database performance depends on more than its file size.
The number and efficiency of queries, indexes, concurrent connections, database server performance, and plugins can all matter.
This is why a 5 GB WordPress database is not automatically “too big,” while a much smaller badly optimized database can cause performance problems.
Monthly Visitors Are a Poor Resource Calculator
Hosting plans often describe themselves as suitable for a certain number of monthly visits.
Those figures can be useful as broad guidance, but 100,000 monthly visits is not a standardized workload.
Compare two sites.
Site A
- 100,000 monthly pageviews
- mostly cached articles
- optimized images
- CDN
- few logged-in visitors
Site B
- 40,000 monthly visits
- WooCommerce
- customer accounts
- dynamic search
- carts and checkouts
- many plugins
Site B may require substantially more server processing despite receiving less than half the traffic.
Concurrency matters too.
A website receiving 300,000 visits evenly across an entire month can be easier to host than one receiving 100,000 visits with 20,000 arriving during a viral two-hour period.
Traffic Spikes Matter More Than Monthly Averages
Imagine your website normally has 10 people active simultaneously.
Then a popular newsletter links to one article and 500 visitors arrive within a few minutes.
Your monthly traffic figure may still look modest, but the server suddenly has to process a large burst of requests.
Caching and CDNs can absorb much of this load on content sites. Cloudflare notes that cached resources can be served from CDN edge infrastructure instead of repeatedly hitting the origin server.
Dynamic requests are harder.
For an ecommerce store running a major sale, hundreds of customers may simultaneously add products, access carts, check inventory, and complete payments.
That is where CPU, RAM, PHP capacity, database performance, and scalable infrastructure become much more important.
Example Hosting Requirements by Website Type
The ranges below are reasonable starting points for planning, not guarantees. Hosting platforms allocate resources differently, and efficient software can substantially change requirements.
| Website Type | Storage | RAM* | CPU* | Resource Priority |
|---|---|---|---|---|
| New blog | 10 to 20 GB | 1 to 2 GB | 1 vCPU | Caching, backups |
| Established blog | 20 to 50 GB | 2 to 4 GB | 1 to 2 vCPU | CPU, CDN, caching |
| Portfolio | 5 to 20 GB | 1 to 2 GB | 1 vCPU | Image storage, bandwidth |
| Small business site | 10 to 20 GB | 1 to 2 GB | 1 to 2 vCPU | Reliability, backups |
| WooCommerce store | 20 to 50+ GB | 4 to 8 GB | 2 to 4 vCPU | PHP, RAM, database |
| High-traffic content site | 50+ GB | 4 to 8+ GB | 4+ vCPU | CDN, caching, scalability |
*RAM and CPU ranges are most directly applicable when selecting VPS or cloud resources. Shared and managed hosts may allocate these resources differently.
New blog
A new WordPress blog should usually begin on decent shared or managed WordPress hosting.
You probably do not need a 4-core VPS and 8 GB RAM before you have readers.
Prioritize automatic backups, caching, SSL, sufficient storage, and an easy upgrade path.
Established blog
As content and traffic grow, CPU utilization, caching, storage, and CDN usage become more important.
Do not upgrade only because the website reached an arbitrary visitor count. Check whether your current hosting is actually hitting limits.
Portfolio
A photography or design portfolio may use more storage and bandwidth than CPU.
Compress images and consider offloading video rather than buying a much larger server solely to store huge media files.
Small business website
Most brochure-style business sites have modest resource requirements.
Reliability, security, backups, email, and support may matter more than raw CPU specifications.
WooCommerce store
WooCommerce is where resource planning becomes more important.
Dynamic carts, accounts, orders, inventory, payment processing, and database activity mean caching cannot solve every request.
Prioritize CPU, RAM, PHP capacity, database performance, and backups rather than simply looking for enormous storage.
High-traffic content site
Large publishers benefit heavily from effective full-page caching and CDN delivery.
A well-cached site can handle large amounts of traffic efficiently because many requests do not need to reach WordPress at all.
Still, the origin needs enough capacity for cache misses, publishing activity, crawlers, admin users, APIs, and sudden traffic spikes.
How to Know When You Need More Hosting
Do not upgrade simply because your provider sends a marketing email recommending a larger plan.
Look for evidence.
Possible signs include:
- CPU repeatedly reaching its limit
- sustained high RAM usage
- 503 or timeout errors
- PHP requests queuing
- slow uncached pages
- disk nearing capacity
- inode limits approaching maximum
- database connection problems
- traffic spikes causing outages
- consistent performance problems after optimization
Modern hosting panels often expose this information. Hostinger, for example, provides resource-usage reports covering CPU, memory, disk space, inodes, and other account limits.
Check the bottleneck before upgrading.
If your inode usage is at 95% but CPU is at 15%, adding CPU resources does not address the problem.
If storage is almost empty but PHP is saturated during checkout, buying a plan primarily because it includes more disk space misses the real issue.
Buy for Your Workload, Not the Biggest Number
Most website owners need less hosting than advertising pages make them think.
A new blog can often start comfortably with an entry-level shared plan. A normal small business website may remain there for years. Larger blogs need more resources gradually, particularly if caching and CDN usage are good.
Ecommerce is different because more traffic involves dynamic activity. WooCommerce stores should pay closer attention to CPU, RAM, PHP processing, database performance, and concurrency.
The best approach is to start with sensible resources and monitor actual usage.
Storage tells you how much you can keep. Bandwidth tells you how much data you can transfer. RAM provides working memory. CPU performs the processing. Inodes limit file counts. PHP workers determine how many dynamic PHP requests can be handled concurrently.
Once you understand what each resource does, choosing hosting becomes much easier. You stop paying for impressive specifications you may never use and start looking for the limits that actually affect your website.
Leave a Reply