High time to first byte (TTFB)
The server takes too long to build the page itself: PHP runs, dozens of queries hit the database, and only then does the HTML go out. A CDN barely helps here. The fix is page caching and, eventually, more CPU and RAM.
Most WordPress sites run perfectly well on shared hosting. Some don’t, and hardly anyone tells you so honestly, because they’d rather sell you a pricier plan on the same shared hosting. This page covers both: WordPress hosting in Iran for the sites that fit it, and the right path for the ones that don’t.
“My site is slow” is really four very different problems, each with its own fix. Get the diagnosis wrong and you pay more without getting any faster.
The server takes too long to build the page itself: PHP runs, dozens of queries hit the database, and only then does the HTML go out. A CDN barely helps here. The fix is page caching and, eventually, more CPU and RAM.
Images, CSS and JavaScript are heavy, and they’re all served from one place. This is exactly where a CDN pays off: the same files are served from the edge node closest to each visitor.
Every active plugin runs code on every page load. A site with 40 active plugins is slow even on a powerful server. Trim your plugins before you upgrade the server: it’s the only fix that costs nothing.
Autoloaded options in wp_options, piles of post revisions and plugin logs weigh the database down. A bigger server hides the problem; it doesn’t solve it.
The real dividing line isn’t traffic. It’s how much of your site can be cached.
| Your site | The right choice |
|---|---|
| Company site, blog or portfolio: pages rarely change | Shared hosting. With page caching and a CDN, it beats a server nobody has tuned. |
| High-traffic content site where almost everything can be cached | Shared hosting + CDN. That will carry you a long way. |
| WooCommerce store with an active cart and checkout | A VPS. The cart, checkout and “My account” pages can’t be cached by nature, so every visit really runs PHP and hits the database. |
| Membership site, online courses or anywhere users are logged in | A VPS. Logged-in users bypass the page cache, so the load lands straight on the CPU. |
| Heavy plugins, cron jobs or background queues | A VPS, with root access and full control over resources. |
| You run several client sites | Both, from one account. See agency hosting. |
A VPS starts at 863 Toman an hour and is billed hourly, so you can try one for a week and delete it if it doesn’t work out. Details on the Linux VPS in Iran page.
A CDN solves half the problem, and it solves that half very well. The honest truth is that the other half is your server’s job.
Images, CSS and JavaScript, which make up most of a page’s weight, are served from the edge node closest to each visitor, across 8 nodes today. SSL certificates are issued automatically, and the load from those files never reaches your server.
With the CDN on, the published record points at the edge nodes and your origin server’s IP stays out of public view, so scans and direct traffic aimed at the origin go nowhere.
Pages that are different for every user (cart, checkout, dashboard) aren’t cached and have to be built by your server every time. If that’s where your problem is, a CDN won’t change anything; look at page caching and server resources instead.
You switch the CDN on for any A record from the same DNS management page, and your first 1 TB of traffic is free.
Activated as soon as the invoice is paid, and managed from your Mehran Host panel.
Disk space: 500 MB. Bandwidth: Unlimited. Control panel: DirectAdmin. 1,500,000 Toman / month
Managed WordPress (automatic core and plugin updates, server-level caching, staging and one-click restore) isn’t offered today. If that’s what you’re after, tell us: we’ll build it sooner, and in the meantime we’ll show you how to get as close as possible with our existing hosting or a VPS.