Developer Buying Guide
PHP hosting plans — Modern PHP is fast. Most hosting is what slows it down
The runtime stopped being the bottleneck years ago. The configuration in front of it usually still is.
The short answer
Start from a current PHP release with OPcache active, Composer installed and per-site version switching available — the language is genuinely fast now, and the platform's job is to stop getting in the way of that. Two settings and one version number account for most of the difference between hosts.
This page names the settings, tells you how to read each one from your own account, explains which of them flatter a benchmark without helping a visitor, and finishes with the tier we would buy.
By the HostingFast team · Reviewed 24 August 2026
99.9%
Uptime target, monitored
24/7
Engineers on duty
Free
SSL on every plan
NVMe
Drives, every tier
For developers who already know how far PHP has moved and are tired of hosting that has not moved with it. If you can run phpinfo and read a status array, everything below is checkable in ten minutes.
Years of engine optimisation and the JIT compiler introduced in PHP 8 made it one of the fastest interpreted runtimes in general use. The reputation for sluggishness dates from an era of hosting that ended a long time ago, and the remaining slowness is nearly always configuration.
Read these four values from your own account
opcache.enable and the hit rate. Call opcache_get_status and look at two fields: the hit ratio, which should sit comfortably above 95% on a warm site, and oom_restarts, which should be zero. A full opcode cache silently reverts you to recompiling every file on every request, and it is the most expensive misconfiguration available on a PHP host.
The version number, per site. PHP 8.x against 7.4 is a measurable gain on real workloads such as WordPress, and it arrives without touching a line of code — the rare optimisation that amounts to choosing an entry from a dropdown.
memory_limit and max_execution_time, checked against what your framework actually needs rather than against the default. Bulk admin operations are where an undersized limit shows up, and it shows up as a blank page rather than an error.
The extension list. mysqli and PDO, gd and imagick, curl, intl, mbstring, zip and redis are the practical working set; a missing one turns into a deployment failure at the worst possible moment.
Which of those actually reaches a visitor
OPcache reaches every visitor on every uncached request, which is why it comes first. The version bump reaches every visitor too, and both are free.
The JIT, by contrast, is where the cargo cult lives. It is a genuine gain on numeric and CPU-bound code and close to irrelevant for a typical database-backed web request, where the time goes to I/O rather than opcode dispatch. Enabling it and expecting a faster blog is a benchmark result with no visitor attached.
The same applies to micro-benchmarks generally. A synthetic loop that gets 20% faster tells you about the interpreter. What tells you about your site is time to first byte on a real, uncached URL — measure that before and after any change, or you are collecting trivia.
What to rule out, and why it stays common
Providers still defaulting to PHP 7.x. An end-of-life interpreter is unpatched attack surface wearing a version number, and no amount of application code compensates for it.
Providers who set the version account-wide rather than per site, which turns one legacy application into a ceiling for everything else you host.
The pattern persists because its bill arrives late: at renewal, mid-migration, or exactly when growth arrives. The cure is arithmetic — total the cost over two or three years with every add-on you would genuinely need included.
Our pick, and the measurement that confirms it
Turbo is where this page lands: 25 sites on one account, 20 GB of NVMe, per-site PHP switching from the panel, LiteSpeed caching at server level, and SSL, migration and mailboxes already inside the rate.
Confirm it in three commands. Check the version, read the OPcache hit ratio after a warm-up, and time an uncached URL from the connection your audience uses. Those three readings say more than any comparison table.
Then run the commercial checks too: the renewal rate against the order rate, a hard question to support at an awkward hour, the refund terms read for carve-outs, and the company registration looked up on the public record.
Our commercial interest, stated in the body copy
We sell hosting, which is exactly why this page is built out of values you can read from your own account rather than adjectives you would have to take on trust.
Mailboxes on your own domain are part of the plan rather than a checkout line item, so the mail configuration never becomes a separate negotiation.
- Every claim reducible to a value you can read
- PHP version set per site, not per account
- The renewal figure published in full
- Free migration makes the trial cheap
Why HostingFast
Standard on every plan
Per-site version switching
A legacy application and a current one run side by side on one account, each on the interpreter it needs.
OPcache you can inspect
Hit ratio and restart counts are readable from your own code, which is the only way to know the cache is doing its job.
LiteSpeed at server level
A cache hit skips PHP and the database entirely — the largest available saving is the work you never do.
Turbo, in numbers
25 sites, 20 GB of NVMe and per-site PHP control at one published monthly rate that does not change at renewal.
An upgrade that is not a migration
Shared, VPS and dedicated on one platform, so growing out of a tier is an account change rather than a weekend.
Extensions without a ticket
The practical working set is toggled from the panel, and anything more obscure is a conversation rather than a refusal.
Prices Side by Side
Our numbers next to the big names
Typical intro and renewal pricing across the market, lined up against ours — including the renewal figure most comparison charts skip.
| Feature | HostingFastMost popular | Typical household-name host | Typical bargain host | Typical loss-leader deal |
|---|---|---|---|---|
| Starting price / mo* | $2.42/mo | $4–$6 | $2–$4 | $1–$3 |
| Renewal price / mo | $2.42/mo | $10–$15 | $8–$12 | $4–$6 |
| Cheapest plan renews at its sign-up price | ||||
| SSL as standard | ||||
| Migration done for you | ||||
| NVMe drives on the cheapest tier | ||||
| Daily backups from the first tier | ||||
| Real humans on support, 24/7 |
*Our number is the lowest-priced plan we sell on an annual term, pulled live from the same catalogue that powers our pricing page — it physically cannot fall out of date. The other three columns show the ranges shared hosts in each bracket typically advertise: introductory offers that mostly demand a one-to-four-year commitment, then jump once it expires. We no longer name rivals or print their prices, because a figure we cannot verify on the day you read it has no business on this page. Line us up against whichever host you are really weighing — and give the renewal row the hardest look.
Quick Start
From order to online
- 1
Read the three values first
Version, OPcache hit ratio, and uncached time to first byte. Ten minutes of reading beats an afternoon of feature grids and settles most of this decision.
- 2
Separate the free wins from the fashionable ones
A version bump and a warm opcode cache reach every visitor. The JIT reaches numeric workloads. Spend your attention in that order.
- 3
Rank the shortlist on year two
Renewal rate times the term, plus every extra you would genuinely enable. Introductory pricing never survives that multiplication.
- 4
Prove it on a real URL
Time an uncached page before and after, from the same connection, cold and warm. A synthetic loop is trivia; a real template is evidence.
Built In
Loaded onto every plan
- PHP 8.x available shortly after release, selectable per site
- OPcache enabled and sized so restarts stay at zero
- The practical extension set toggled from the panel
- Composer and SSH on the developer-focused tiers
- LiteSpeed caching built into the server, not patched in by plugin
- Error logs readable the moment something misbehaves
- Staging copies so an update is tested before it is trusted
- NVMe SSD on every tier, including the entry plan
- Renewal charged at the rate you ordered at
- 99.9% uptime as the target, monitored around the clock
Frequently Asked
What people ask us most often
How do I tell whether OPcache is doing anything?
Call opcache_get_status from a script on the account and read two fields. The hit ratio should be well above 95% once the site is warm, and oom_restarts should be zero. A ratio in the seventies with restarts climbing means the cache is too small for the number of files you are running, and every restart throws away the compiled opcode for every site on the account.
Is the PHP 8 JIT worth enabling on a website?
Usually not, and the honest reason is where the time goes. A typical web request spends its milliseconds waiting on the database and the filesystem, which the JIT does not touch. It shines on numeric and CPU-bound work. Enabling it because a benchmark improved is the clearest example of optimising something a visitor will never experience.
What actually breaks when I move a site from 7.4 to 8.x?
Mostly removed functions and stricter type handling in old libraries — each is an immediate fatal error rather than a subtle regression, which is good news. Clone the site to staging, switch the version there, exercise the admin and checkout paths, and read the error log. An afternoon on staging beats a rollback on production.
Does the extension set differ between plans?
The working set is the same across the shared and business tiers and is toggled per site from the panel, so a project that needs intl and one that needs imagick do not have to argue. Anything outside that set is a support conversation; we would rather add it than have you discover the gap during a deploy.
Keep reading
Hosting With SSH Access
Why a shell prompt changes what you can diagnose, and which tiers include one.
Managed vs Unmanaged VPS
Who gets paged at four in the morning, costed both ways.
PHP (Glossary)
The term in plain language, with the practical consequence for a page load.
PHP Hosting
Choose your PHP version per site, on fast NVMe hardware.
cPanel Reseller Hosting
The industry-standard panel scaled for resellers, WHM included.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Give modern PHP somewhere to run.
Current releases, a warm opcode cache and LiteSpeed in front, at a rate that does not move at renewal.
View PHP Hosting plans