The number that separates hosting from everything else is time to first byte (TTFB): under 600 ms and your server is fine — the slowness is in your site; consistently over a second and the host, or its configuration, is the cause. Everything else — images, themes, plugins — is measured after that.
This distinction saves you money: most people who buy a more expensive plan chasing speed could have fixed the problem for free.
Measure first: three minutes
1) Time to first byte. Open any free measurement tool (PageSpeed Insights, WebPageTest, GTmetrix) and read TTFB or "Server Response Time".
| The number | What it means |
|---|---|
| Under 200 ms | Excellent |
| 200 – 600 | Good — the server is not your problem |
| 600 – 1000 | Borderline, worth a look |
| Over 1000 | The server or its configuration is the cause |
2) Measure twice: at peak and at a quiet hour. A large gap means you are hitting a resource ceiling — an explicit symptom for moving off shared hosting.
3) Measure from where your visitors are. A tool testing from Frankfurt tells you nothing about a visitor in Riyadh. Pick the test location nearest your audience.
Prices on this page are read from our table the moment you open it, not typed into the text. Check the comparison page for the latest figures before buying.
Causes, ordered by likelihood
This order comes from what we actually see, not from what gets marketed:
1. Uncompressed images — the number one cause by a wide margin. A 3 MB image displayed in a 400-pixel slot wastes everything a fast server gave you.
2. The theme and plugins — a heavy theme loads dozens of files, and every plugin adds queries.
3. No caching — without it, every visit rebuilds the page from scratch.
4. Distance from your visitors — geography costs milliseconds no faster CPU can recover.
5. Hosting resources — last on the list, not first.
So the practical order: compress the images, add caching, trim the plugins. If TTFB is still high after that — then upgrade.
What in hosting actually matters
If you have established the server is the cause, these are the factors by impact:
Reserved resources. On shared hosting you share a CPU with hundreds of sites; a busy neighbour slows you. A VPS reserves your slice, so performance stops fluctuating.
Disk type. NVMe beats SSD, and SSD massively beats spinning disks. Most modern plans are NVMe.
PHP version. The gap between PHP 7.4 and 8.3 is noticeable. Update it from your control panel — we cover where to find it.
Web server. LiteSpeed outperforms Apache on busy WordPress sites, and many providers use it.
Data centre location. The most neglected factor — a US server for a Gulf audience adds hundreds of milliseconds.
Three free fixes before you pay
1. Compress your images. Convert to WebP and resize to the dimensions actually displayed. Page weight often drops to a third.
2. Install caching. On WordPress, one caching plugin makes a large difference. If your server runs LiteSpeed, use its dedicated plugin.
3. Delete what you do not use. Every deactivated plugin and old theme is weight and a potential hole.
Try these three, then measure again. If the number improved, you just saved the price of an upgrade.
When upgrading is the answer
Upgrade if two of these are true:
- TTFB above a second after fixing images and caching
- A clear gap between peak and quiet hours
- A resource-limit email from your provider
- The site falls over when traffic rises
Then choose by situation:
| Your situation | Where to go | Per month | |
|---|---|---|---|
| Outgrew shared, do not want to run a server | Cloud Startup | EGP 319 | Offer |
| Want reserved resources and control | KVM 2 | EGP 429 | Offer |
| Still on an old, slow plan | Premium | EGP 79 | Offer |
Does speed affect search ranking?
Yes, but do not overstate it. Google uses page experience signals as one factor among dozens, and better content beats higher speed.
The clearer effect is on bounce rate: visitors leave a slow page before reading it. That hurts you twice — in sales and in ranking.
The short answer
Measure before you pay. One number — TTFB — tells you where the problem is.
Fix the free things first: images, caching, plugins. Most sites improve here and stop.
Upgrade when the number stays high after that — not before. Upgrading "just in case" is a bill for nothing.
Compare plans on promo and renewal price together on the comparison page.
Read next: What is web hosting? · The best hosting company · Cheapest web hosting · Hosting contract terms · Compare plans
Disclosure: some links on this page are affiliate links. They cost you nothing extra, and nobody buys a ranking here with them — how we work.