How to choose WordPress hosting: 10 measurable criteria to check before you buy

Choosing WordPress hosting is a decision whose effects you see every day: in how fast the first page opens, in whether your store holds up at the busiest hour, and in the SEO you build up, or lose, month after month. The trouble is that every host advertises the same way — "fast", "unlimited", "reliable" — and none of those adjectives can be measured. This guide takes the opposite route and shows how to choose WordPress hosting on things you can measure. First we explain exactly what WordPress asks of a server, then we give you 10 measurable criteria for comparing hosts, list the red flags in hosting ads, and finish with a table that shows the right starting point for each kind of site, from a blog to a WooCommerce store.

WordPress hosting vs regular hosting: from label to technical reality

"WordPress hosting" means two very different things in the hosting market. Sometimes it is just a marketing label on the same old shared hosting, at a slightly higher price; sometimes it means infrastructure that has genuinely been tuned for the way WordPress works. To tell the two apart, you need to know what WordPress does every time a page opens, because every criterion in this guide follows from that.

WordPress is a PHP application that builds each page on the fly: the visitor's request reaches a PHP process, WordPress core, the theme and the plugins run, dozens of queries go to the MySQL database, and finally the finished HTML is sent back. The capacity a host gives you for this work is measured in "PHP workers": the number of requests that can be processed at the same time. If your plan has two workers and each page takes half a second to build, the real capacity of your site is about four dynamic pages per second; anything beyond that waits in a queue or comes back as an error. The big "disk space" figure that ads put front and center tells you nothing about this capacity.

Two kinds of cache change this picture, and the difference between them matters. A page cache keeps a ready-made copy of the HTML so that later visits are answered without running PHP and without touching the database. It works wonders for a blog or a company website, but it is almost useless for logged-in users and shopping carts, because those pages are different for every person. An object cache, such as Redis or Memcached, keeps the results of repeated database queries in memory and comes to the rescue exactly where a page cache falls short: WooCommerce stores and membership sites. A host that offers neither pushes the entire load back onto your handful of workers.

There is also a lesser-known behavior that is specific to WordPress: its built-in scheduler, wp-cron. WordPress runs its scheduled jobs (publishing a post at a set time, checking for updates, plugins' periodic tasks) not with the operating system's real scheduler but on the back of visitors' page loads. On a low-traffic site, jobs fall hours behind; on a busy site, the same mechanism adds overhead to page loads. The standard fix is to disable wp-cron and hand the work to a real cron job, and a host that does not let you define cron jobs has effectively taken that fix away from you:

# wp-config.php
define('DISABLE_WP_CRON', true);

# crontab entry (every 5 minutes)
*/5 * * * * php /home/USER/public_html/wp-cron.php

How to choose WordPress hosting: the 10 measurable criteria

We picked the criteria below deliberately: each one is something you can ask about, measure or verify. Their order is roughly their order of importance for a typical WordPress site.

1 — PHP version and number of workers

The official WordPress documentation always recommends current PHP versions, and the performance difference between PHP generations is real and noticeable. A host that defaults to outdated versions, or does not let you change the version from the control panel, is ruled out at this very first step. After the version, look at capacity: the number of workers, or concurrent PHP processes, should be a specific number in writing, not an adjective such as "powerful".

2 — NVMe storage

Every WordPress page load means reading dozens of PHP files and making repeated round trips to the database, and the speed and latency of the disk play a direct part in all of it. At small, scattered operations, which is exactly the workload of WordPress and MySQL, NVMe drives are several times faster than SATA-based SSDs and dozens of times faster than spinning hard disks. If the disk type is not listed in the plan's specifications, ask; we cover the full technical background in our article on KVM and NVMe.

3 — Database latency

On some platforms the database runs on the web server itself, on others on a separate server; both models can work well. What matters is the latency of each query, because a typical WordPress page runs dozens of queries one after another and small delays add up. Once the service is delivered, use a plugin such as Query Monitor to see the total database time of your pages; if it goes beyond a few dozen milliseconds for a simple page, document it in the first week and follow it up.

4 — Server location relative to your audience

The server's location should be decided by where your visitors are, not by where you happen to be sitting. For a site whose audience is inside Iran, WordPress hosting in Iran has lower network latency and stays reachable from inside the country during disruptions to international connectivity (Iran's links to the global internet are sometimes slowed or cut while domestic traffic keeps flowing). For an audience abroad, the same logic works the other way around. This decision matters so much that we cover it separately in our guide to hosting in Iran vs abroad.

5 — Automatic SSL

An SSL certificate stopped being a luxury years ago; issuing and renewing a free certificate automatically should be part of the service itself. A host that charges a separate yearly fee for HTTPS, or leaves certificate renewal as a manual job, comes with a hidden cost and with the risk of a certificate suddenly expiring. If you want to understand the mechanism behind it, our guide to installing a free SSL certificate walks you through it step by step.

6 — Backups and staging

The right question is not "Do you have backups?" It is "How many copies, how often, where are they stored, and can I restore them myself or do I have to open a ticket?" A backup that lives on the same server as your site is lost along with that server. A staging environment, meaning a test copy of your site where you can try theme and plugin updates before applying them to the live site, is rare on shared hosting; not having one is no great flaw, but if a host claims to offer it, try it once before you buy.

7 — Email delivery

WordPress sends critical emails: password resets, new-order notifications, contact-form messages. On shared hosting these messages go out from an IP address shared with dozens of other sites, and if one neighbor sends spam, the bad reputation of that IP becomes your problem too. The bare minimum is being able to set SPF and DKIM records for your domain; the professional solution for business-critical email is a transactional email service separate from the host itself.

8 — A well-known control panel

cPanel and DirectAdmin are both well established and handle the everyday tasks of a WordPress site equally well: creating databases, managing files, subdomains, SSL, switching PHP versions and setting up cron jobs. What should make you wary is an unknown proprietary panel that makes it hard to take a full export of your site. Being able to leave a host easily is part of that host's quality; a service with an open door on the way in and a wall on the way out is not a safe choice.

9 — Quality of support

Test support before you buy, not on the night something breaks. Ask the sales team a real technical question, such as the number of workers or the backup policy, and watch two things: how long the reply takes, and whether the person answering understood your question or sent a canned response. A host that cannot answer precisely before it has your money will not become more precise afterward.

10 — Transparent resource limits

Every shared plan has limits (a share of the CPU, memory, a number of files, concurrent processes), and that is perfectly normal; the issue is transparency. A host that publishes its limits in writing lets you make an informed decision. A host that labels everything "unlimited" has the same limits; it has simply hidden them in the "fair use" clause of the contract, and the first time you learn they exist is the moment your service is suspended.

Shared hosting or VPS? The point where WordPress graduates

Most WordPress sites run perfectly well on properly configured shared hosting, and moving to a server too early only adds cost and maintenance responsibility. Nor is the real dividing line the number of visits; it is the ratio of cacheable to uncacheable pages. A busy blog whose pages look the same to everyone can manage with a page cache even on few workers. A store with an active cart and checkout, or an e-learning site whose users log in, spends PHP and database time on every real visit, and sooner or later it hits the ceiling of a shared plan.

The signs that you have reached that line are clear: noticeable slowdowns that recur at the same times of day, resource-limit errors in the control panel's reports, and a checkout that breaks when the site gets busy. At that point, read the full comparison of the two options in our article on shared hosting vs a VPS, and if you decide to move WordPress from shared hosting to a VPS, our guide to setting up WordPress on a VPS shows what lies ahead, from installing the web server to security and caching. To be honest about it: a VPS brings responsibility. If you have neither the time nor the patience to maintain one, staying on good shared hosting is far better than moving to a neglected server. We have also laid out the exact boundary between the two for different kinds of sites in a table on our WordPress hosting in Iran page.

Red flags in hosting ads

The hosting market, the Iranian one included, is full of claims that either cannot be measured or are contradicted by the contract. Learn to recognize four common patterns:

• "Everything unlimited". Unlimited disk space, bandwidth and email on a server with finite resources cannot be defined. The claim always comes paired with a "fair use" clause, which means there is a limit; they just don't tell you the number. It is also the classic sign of oversold hosting: a server on which the host has sold more accounts than the hardware can serve at once, betting that they will never all be busy at the same time.
• Uptime promises with several decimal places. A figure with no stated measuring tool, no calculation period and no penalty for missing it is not a figure; it is decoration. Ask which tool measures it, from which location, and under what written commitment. Silence in reply to that question is an answer in itself.
• "Optimized for WordPress" with no details at all. Real optimization has parts you can name: the PHP version, caching, the disk type, the workers. If the seller cannot tell you exactly what has been optimized, probably only the label on the page has changed.
• A tempting first-year price. Some services lure customers in with a low price and then multiply it at renewal. Before you buy, ask for next year's renewal price in writing and compare the real cost on that basis.

Decision table: which hosting for which site?

If you are in a hurry, the table below sums up the whole guide. The last column shows which of the 10 criteria above matter most for that kind of site:

Whichever option you choose, do not guess once the service is delivered: measure your site's real speed with our free website speed test and keep the result as a baseline for later comparisons.

Buying WordPress hosting and paying in Toman: the Mehran Host approach

Mehran Host has no separate, higher-priced plan labeled "WordPress", and that is a deliberate choice: the shared hosting infrastructure on cPanel and DirectAdmin is the same for WordPress as for any other PHP application, and a label adds no speed. The service is activated automatically once its invoice is paid in Toman (the everyday unit of Iran's currency; 1 Toman = 10 rials), and the current list of plans is on our Iran web hosting page. If you are unsure whether your site should stay on shared hosting or whether it is time to move to a server, our WordPress and WooCommerce hosting page was written for exactly that question. It also explains which part of speed a CDN (with 1 TB of free traffic) solves and which part remains your server's job.

One last piece of advice that will save you money: if your WordPress site is slow today, work through our guide to speeding up WordPress before you buy or migrate anything. Much of the slowness comes from too many plugins, missing caching and heavy images, and it can be fixed on the hosting you already have without spending a single rial. Better hosting does not rescue a badly configured site; it only makes its slowness more expensive.

Frequently asked questions

What is the difference between WordPress hosting and regular hosting?

In many cases there is no real technical difference: "WordPress hosting" is just a label on the same shared hosting. When a real difference exists, it lies in the configuration: a current PHP version, enough PHP workers, a page cache or object cache, and NVMe storage. Instead of trusting the label, ask for exactly these specifications in writing; a host that gives you written answers is more trustworthy than one that only has a label.

How many PHP workers does a WordPress site need?

It depends on how much of your site can be cached. A site with a page cache that serves most visits from that cache can manage with two to four workers; a store or membership site where users log in genuinely uses a worker for every request and needs more. Your concurrent traffic sets the exact number; what matters is that the plan's figure is written down and that you can ask about it.

Should I choose WordPress hosting in Iran or abroad?

Choose by where your visitors are, not where you are. If your main audience is inside Iran, hosting in Iran has lower network latency and stays reachable from inside the country when international connectivity is disrupted; for an audience mostly outside Iran, a server close to those visitors makes more sense. If both groups matter, hosting near your main audience combined with a CDN for static files is a practical middle ground.

When should I move WordPress from shared hosting to a VPS?

Move when uncacheable pages have become your site's main load: a store with an active shopping cart, a membership site with logged-in users, or heavy plugins that run on every request. The practical signs are recurring slowdowns at peak hours and resource-limit errors in your control panel. Until you see those signs, good shared hosting with a page cache is usually enough, and moving early only adds maintenance work.

How can I tell whether the WordPress hosting I bought is actually good?

Put it through a one-week trial: measure your home page's time to first byte (TTFB), check the total time of your database queries with the Query Monitor plugin, do a test restore from a backup, and open a real technical ticket to judge the quality of the reply. If the results do not match the promised specifications, document it that same week; migrating in the first week is cheap, and in the second year it is expensive.