This is a Q3 2026 snapshot. Hosting stacks change quietly — often without a changelog entry a customer ever sees — so we re-check the underlying components each quarter rather than trust a page written a year ago. Numbers below reflect what we found checking live hosting environments and public documentation this quarter; re-verify before making a migration decision off any single data point.
What “the stack” actually means
When we say “stack” we mean the four layers that determine how a WordPress install actually runs, independent of any theme or plugin choice: the PHP runtime version, the web server (Nginx, LiteSpeed, or Apache with a proxy in front), the database engine (MySQL vs. MariaDB, and which major version), and the object cache layer (Redis, Memcached, or none). None of these show up in a typical “features” comparison page, but all four move independently of a host's marketing site — a host can ship a redesigned dashboard while quietly leaving customers on a PHP version two releases behind.
What changed this quarter
PHP 8.5 reached general availability in November 2025 and has been the actively-maintained stable branch through this year, with PHP 8.4 remaining the more conservative production choice (security and bug-fix support runs through December 2028). WordPress core's own minimum recommendation still sits at PHP 8.3. The practical gap this creates: most managed WordPress hosts we checked — including Kinsta, WP Engine, and Cloudways — still default new sites to PHP 8.2 or 8.3 rather than the newest available branch, and only expose 8.4/8.5 as an opt-in change in the hosting panel. If you provisioned a site more than a year ago, there's a reasonable chance you're running a PHP version your host has since surpassed for new signups.
On the web-server side, the shift toward LiteSpeed and Nginx-plus-FastCGI-cache setups (replacing plain Apache) has continued, mainly because both handle high concurrent connection counts with a smaller memory footprint — relevant if your site gets bursty traffic rather than a flat daily curve.
How to check your own host's current stack
- PHP version: WP Admin → Tools → Site Health → Info tab → Server. This is the authoritative source; don't trust a host's marketing page.
- Web server: Check response headers (`curl -I https://yoursite.com`) for a `Server:` or `X-Powered-By` header — many hosts strip this deliberately, in which case ask support directly.
- Database engine/version: Site Health → Info → Database, or `SELECT VERSION();` via phpMyAdmin/Adminer if your host exposes it.
- Object cache: Site Health → Info → WordPress Constants, look for `WP_CACHE` and check whether a persistent object-cache drop-in (`object-cache.php`) is present in `wp-content/`.
Default stack by host (this quarter's check)
| Host | Default PHP for new sites | Web server | Object cache included |
|---|---|---|---|
| Kinsta | 8.2 (8.3+ selectable in MyKinsta) | Nginx | Redis (add-on, paid tiers) |
| WP Engine | 8.2 (8.3 selectable) | Nginx | Included on Business+ plans |
| Cloudways | 8.2 (up to 8.3 selectable) | Apache/Nginx or Varnish stack, host-dependent | Redis (optional add-on) |
| Hostinger | 8.2 (selectable up to latest available) | LiteSpeed | LiteSpeed Cache built-in |
Treat this table as a starting point, not a guarantee — hosts roll out version bumps in phases, and your specific data center or plan tier may already be ahead of what's listed here.
FAQ
Does upgrading PHP version actually speed up my site? Usually yes, and it's one of the few “free” performance wins available — PHP 8.x releases have consistently improved execution speed over 7.x, and 8.3/8.4 add further JIT and opcache refinements. The catch is plugin compatibility: test on staging first, since older or abandoned plugins can throw fatal errors on newer PHP.
Why doesn't my host just default everyone to the newest PHP version? Support-ticket volume. A host with millions of active WordPress installs cannot afford the fatal-error support load from force-upgrading every site at once, so new sites get the newer default while existing sites are migrated more slowly, often requiring an opt-in click.
Is it worth switching hosts over an outdated PHP default? Not on its own — nearly every host lets you manually bump the PHP version in its control panel. Check that setting before assuming you're stuck.
Verdict
The stack keeps moving even when your invoice doesn't change. The actionable step from this quarter's check isn't “switch hosts” — it's “open Site Health and look,” since a one-click PHP bump sitting unused in your hosting panel is the single most common gap we found.
