You bought hosting, set up WordPress, and now your site loads like a slideshow on a bad connection. You’re not alone.
Most beginners pick a plan based on price or a flashy ad. They don’t actually check if the hosting delivers what it promises. The result? A slow site that hurts your traffic, frustrates visitors, and wastes your money.
This checklist gives you five concrete tests to run right now. You’ll know exactly where your hosting fails and what to fix.
Step 1: Run a speed test on a real page (not the homepage)
Don’t test your homepage. It’s often cached and loads fast. Test a blog post or product page with images and text.
Use a free tool like GTmetrix or Pingdom. Enter the full URL of a typical page.
What to look for:
– Load time: under 3 seconds is acceptable. Under 2 seconds is good. Over 4 seconds is a problem.
– First Contentful Paint (FCP): under 1.5 seconds.
– Largest Contentful Paint (LCP): under 2.5 seconds.
If your page scores poorly, your hosting is likely the bottleneck. A cheap VPS often fixes this faster than upgrading a shared plan.
Step 2: Check if your server uses NVMe or just SSD
Shared hosting often advertises “SSD storage,” but not all SSDs are equal. NVMe drives are 5x faster than SATA SSDs.
How to check:
1. Install a plugin like WP Server Stats or Server Information.
2. Look for “Drive type” or “Storage type” in the server info.
3. If you see “sda” or “SATA,” you’re on older hardware. If you see “nvme0n1,” you’re good.
NVMe is standard on most modern VPS hosting. If your host still uses SATA SSDs, consider switching. It’s one of the easiest upgrades for speed.
Step 3: Verify your PHP version and memory limit
Old PHP versions kill performance. WordPress recommends PHP 8.0 or newer. Many cheap hosts still default to PHP 7.4 or even 7.2.
Check your PHP version:
– Go to Tools > Site Health in your WordPress admin.
– Click the Info tab.
– Look under Server for “PHP version.”
Also check the memory limit. It should be at least 128MB, preferably 256MB or higher. If it’s lower, your site will crash when you install plugins or add media.
If your host limits you to PHP 7.4 or 64MB memory, that’s a red flag. A fast VPS server typically lets you customize these settings.
Step 4: Find the visitor cap or resource limit
Many shared hosts don’t tell you about visitor caps until your site slows down or goes offline. This is called a “resource limit.”
How to find it:
– Check your hosting dashboard for “CPU cores,” “RAM,” or “inode limits.”
– Look at your plan’s fine print for “visitors per month” or “concurrent connections.”
– If you can’t find anything, contact support and ask: “What happens if my site gets 500 visitors in one hour?”
If the answer is “your site will be suspended” or “you need to upgrade,” your current plan isn’t scalable. For growing sites, WordPress hosting with clear resource limits is safer.
Step 5: Test support with a technical question
Don’t wait until your site is down. Ask a technical question now.
Open a chat or ticket and ask: “Can you show me my server’s current CPU load and RAM usage?”
A good host will answer within 5 minutes and give you real numbers. A bad host will say “we don’t provide that information” or redirect you to a knowledge base article.
If support can’t answer a basic performance question, they won’t help you when your site crashes.
Common mistakes beginners make when checking hosting
- Only testing the homepage. Cache plugins make the homepage look fast. Test a real post.
- Ignoring the PHP version. Old PHP is slow and insecure.
- Assuming all SSDs are the same. NVMe is significantly faster.
- Not checking the resource limit. Shared plans often cap you at 10-20 concurrent visitors.
- Forgetting to test support. Fast support is crucial during a crisis.
Mini scenario: How a portfolio site cut load time from 6 seconds to 1.2 seconds
Anna runs a photography portfolio. Her shared hosting plan cost $3/month. Her gallery pages loaded in 6 seconds.
She ran the checklist:
– Speed test showed 6.2 seconds on a portfolio page.
– Server type was SATA SSD.
– PHP version was 7.4.
– Memory limit was 64MB.
– Support couldn’t tell her the CPU limit.
She switched to a cheap VPS with NVMe storage and PHP 8.1. She set the memory limit to 256MB. Her load time dropped to 1.2 seconds.
Her bounce rate went from 65% to 25%. That single change paid for years of hosting.
For this use case, a recommended VPS provider with NVMe storage and PHP 8 support is ideal. Our pick for cheap VPS hosting balances speed and cost for beginners.
FAQ
Q: Can I check my hosting performance without installing a plugin?
A: Yes. Use GTmetrix or Pingdom for speed. Check PHP version via Tools > Site Health. For storage type, you may need a plugin or server panel access.
Q: What’s the most common cause of slow WordPress sites on shared hosting?
A: Low PHP memory limit (often 64MB) and old PHP versions. Both are easy to fix if your host allows customization.
Q: Does cheap VPS hosting require technical skills to manage?
A: Not always. Many cheap VPS plans offer a control panel like cPanel or CyberPanel. You can manage WordPress without SSH if you choose a managed VPS.
Q: How do I know if my hosting is good for SEO?
A: Check page load time (under 2.5 seconds), server response time (under 300ms), and uptime (99.9% or higher). Hosting for SEO means fast servers and low latency.
Q: What should I do if my host refuses to tell me the CPU limit?
A: That’s a red flag. Start looking for a more transparent provider. Good hosts publish their resource limits clearly.
