When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
dd and sysbench cpu in the first hour; compare against the provider’s own benchmark page.When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.
Blogs and portfolio sites are the cheapest possible workloads to run on a VPS, and they are also where budget buyers overspend most often. A static portfolio serving 5,000 page views a month can run on a single shared CPU core with 512 MB of RAM. A mid-size WordPress blog with caching and a few thousand daily visitors fits comfortably in 1 GB. The $3–$5 per month tier exists precisely for this use case, so the question is not whether it is enough but which specs inside that tier actually matter.
The answer changes once you look at what is inside real plans at this price, because two providers charging $4 can ship very different hardware. Below is what to check, in the order that it affects your site.
The spec floor for a blog or portfolio in 2026
Treat this as the minimum for a site you actually care about. Anything above it is comfort, not necessity, unless your traffic is unusual.
| Spec | Minimum to accept | Comfortable | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB | PHP-FPM workers + database + OS cache |
| vCPU | 1 shared | 2 shared | Page generation, image resizing, backups |
| Storage | 20 GB NVMe/SSD | 40 GB NVMe | Images, backups, OS, logs |
| Transfer | 1 TB | 2 TB | A text-and-image blog rarely exceeds 300 GB |
| Virtualization | KVM | KVM | Swap control, custom kernels, Docker |
| Backups | Weekly snapshot included | Daily offsite | The most common paid add-on after year one |
A static site built with Hugo, Astro or 11ty can drop to 512 MB and still be fast, because nginx or Caddy only needs to hand files to the kernel. A WordPress site with a page cache in front needs roughly the same, but the uncached requests — admin logins, comment submissions, search — will spike to 1 GB in bursts. Two gigabytes removes that tension entirely and typically costs $2 more.
Why the $3–$5 tier is not the same as a $3–$5 tier
At this price, providers are competing on margins that are measured in pennies. That shows up in three places:
- CPU class. Some plans are Intel Xeon Gold on modern DDR4; others are recycled E5 v2 hardware. The spec sheet says “2 vCPU” in both cases. Single-thread performance can differ by two to three times, which is what you feel on a WordPress page render.
- Storage type. “SSD” in 2026 can mean SATA SSD behind a shared controller. NVMe plans at the same price are usually a generation ahead on random reads, which matters for database queries.
- Transfer honesty. A $4 plan advertising 4 TB is metering you somewhere else — often a 100 Mbit port cap or a fair-use clause. A 1 TB allowance on a full gigabit port is the better deal for a real blog.
You can compare the tiers side by side in our budget hosting comparison table, which lists the specs and renewal prices rather than just the promo price. The renewal column is the one people skip and regret.
Static portfolio vs WordPress blog: different plans
A portfolio built as static HTML usually has a fast build step and then almost no runtime. You are serving read-only files, so nginx’s sendfile path handles hundreds of requests per second on one core. The risk is disk, not CPU: galleries and video builds can balloon a 20 GB plan quickly. Keep the repository and the build output on the server, but push large media to object storage or a CDN.
WordPress is the opposite. Disk usage stays modest if you compress images, but request handling is CPU-heavy and memory-bound. The practical tuning at 1 GB is a page cache (WP Super Cache, Cache Enabler, or FastCGI cache in nginx), PHP-FPM with 3–4 workers, and MySQL’s innodb_buffer_pool_size set to about 256 MB. At 2 GB, raise workers to 6–8 and let the buffer pool use 512 MB; you will notice the difference on uncached admin pages and bulk edits.
Ghost, being Node.js, sits between the two: around 200–300 MB resident with a couple of hundred concurrent readers, but it needs swap configured if you run it on 512 MB. If you plan to grow into a newsletter, start at 1 GB.
What actually breaks first at this price
In practice, four things fail before you need more CPU:
- Memory during traffic spikes. A Hacker News or Reddit link pushes uncached requests past your worker limit and the OOM killer takes out MySQL. Swap of 1–2 GB prevents the hard failure.
- Disk filling from backups. Local snapshots stored on the same volume are not backups; they double your disk usage. Schedule pruning and keep one offsite copy.
- Image processing on upload. Resizing ten 4 MB photos in a row will pin a shared vCPU and slow the site for everyone. Resize before upload or offload to a CDN’s image service.
- Bot traffic. Unfiltered scrapers can consume your entire transfer allowance. A free CDN tier and a robots rule will not stop all of them, but they cut the bill.
The $3-to-$5 plan checklist
Before you pay for a year, run these six checks. Each takes minutes and each rules out a class of disappointment.
- Confirm the price is the renewal price, not a first-term promo.
- Confirm KVM and a real root shell with console access.
- Run
ddandsysbench cpuin the first hour; compare against the provider’s own benchmark page. - Check whether snapshots or daily backups are included or cost extra.
- Verify the port speed with an iperf3 test against a nearby host.
- Read the refund window and whether it applies to annual prepay.
When to move up rather than tune
Stay at $3–$5 as long as cached page load stays under 400 ms and TTFB under 200 ms at your 95th percentile. Move to the $8–$12 tier when any of these happen for two consecutive weeks: memory usage above 85% with swap actively used, CPU steal above 5%, or disk above 80% after pruning logs and backups.
Do not jump to a $20 plan because a graph looked spiky once. A single 2 GB upgrade usually covers a 5–10x traffic increase for this workload, and you can see which sizes fit your traffic in our hosting tiers and what they include overview first.
Bottom line
A blog or portfolio needs 1 GB and a modern core, not a big plan. Spend the extra dollar on NVMe and a modern CPU class instead of on more RAM you will not use, and keep $2–$3 of monthly headroom for a backup copy. That combination keeps a low-traffic site fast for years without a renewal surprise.



