Upgrading WordPress to PHP 8: Performance Gains, Compatibility Checks, and What to Do First

If you’re running WordPress on PHP 7.4 or an earlier version, you’re leaving measurable performance on the table. PHP 8.x introduced significant engine improvements that reduce server-side processing time for WordPress — without any changes to your theme, plugins, or content.

This guide covers what actually changed in PHP 8, how to verify your site is ready, and how to upgrade without breaking anything.

What Changed in PHP 8 That Affects WordPress

PHP 8.0, released in November 2020, brought several improvements directly relevant to WordPress performance:

JIT Compilation (Just-In-Time) is the most discussed change. PHP 7 and earlier interpreted code at runtime through an opcode cache (OPcache). PHP 8 adds a JIT compiler that can compile frequently-executed code paths directly to native machine code. For CPU-intensive operations — like processing large loops, complex calculations, or heavy template rendering — JIT can substantially reduce execution time.

It’s worth being accurate about the JIT benefit for WordPress specifically: JIT provides the largest gains for compute-heavy workloads. WordPress is largely I/O-bound (database queries, file reads, HTTP requests), so the improvement you’ll see varies. Benchmarks from hosting providers consistently show PHP 8.x outperforming PHP 7.x in typical WordPress workloads, but the magnitude depends on your specific plugins and page complexity.

Named arguments, match expressions, and nullsafe operators are developer-facing features, but they allow PHP code to be written more efficiently, which plugin and theme developers have adopted in their PHP 8-targeted codebases.

Type system improvements (union types, attributes, constructor property promotion) enable PHP code to be structured more cleanly, and the PHP engine can make better optimization decisions when types are declared.

PHP 8.1 added fibers (lightweight concurrency), enums, and further internal optimizations. PHP 8.2 improved readonly properties and continued engine-level refinements. PHP 8.3, released in late 2023, added further performance work including typed class constants and randomization improvements.

Why PHP Version Matters More Than Many Site Owners Realize

Every WordPress page load executes PHP code. The core WordPress bootstrap, your active theme’s functions, every active plugin — all of that runs synchronously on each request (unless object caching serves the result from memory). A faster PHP engine means each of those executions completes in less time.

On shared or under-resourced hosting, this matters especially because your server has limited CPU available per request. A faster PHP version means the same hardware can serve more requests per second, which reduces queue time and improves response under load.

On managed WordPress hosting with proper server architecture, PHP 8.x works alongside OPcache, object caching (Redis/Memcached), and full-page caching to compound the benefits further.

Checking PHP Compatibility Before You Upgrade

Upgrading PHP without verifying compatibility first is the most common cause of post-upgrade breakage. The risks are real: a plugin written for PHP 7 may use functions that were removed or changed behavior in PHP 8.

Step 1: Check your PHP error logs. Before upgrading, review your current error logs for any PHP notices or deprecation warnings. Deprecations logged in PHP 7.4 often become fatal errors in PHP 8.

Step 2: Run a compatibility scan. The PHP Compatibility Checker plugin (formerly WP Engine’s plugin, now in the WordPress.org repository) scans your active plugins and theme against a target PHP version and flags incompatible code. Run this against PHP 8.1 or 8.2 and review the results before touching anything on the server.

Step 3: Check each plugin’s changelog and tested version. Go to Plugins → Add New → and click on each active plugin to see its “Tested up to” and any PHP requirements listed. Actively maintained plugins typically declare PHP 8.x compatibility. Plugins that haven’t been updated in several years are the ones to watch.

Step 4: Test on a staging environment first. This is non-negotiable for production sites. Make a full backup, spin up a staging copy, change the PHP version there, and test all critical paths: checkout flows if WooCommerce is active, form submissions, custom post type pages, admin functions. Fix any issues before touching production.

How to Change Your PHP Version

The process depends entirely on your host.

cPanel hosts: Most cPanel-based hosts include a “MultiPHP Manager” or “PHP Selector” in the dashboard. You can switch PHP versions per-domain without touching the server directly. Look under the Software section in cPanel.

Managed WordPress hosts: Most managed WordPress hosts let you switch PHP versions per site through their dashboard. Some automatically upgrade to new PHP versions on a schedule, while others let you choose.

VPS and self-managed servers: If you manage your own server (Apache or Nginx with PHP-FPM), you’ll install the target PHP version alongside the existing one, update your PHP-FPM pool configuration, and restart the service. This is out of scope for most site owners but well-documented in server administration guides.

After changing the PHP version, immediately check your site’s front end and admin panel for white screens, fatal errors, or broken functionality.

PHP 8 and Common WordPress Plugins

Most actively maintained plugins have supported PHP 8 for several years. The WordPress ecosystem moved quickly to adopt compatibility after PHP 8’s release in 2020. You’re most likely to encounter issues with:

• Very old plugins that haven’t been updated since 2019 or earlier
• Premium plugins from smaller vendors that may lag behind the free WordPress.org ecosystem
• Custom plugins written by developers who targeted specific PHP versions

If a plugin breaks on PHP 8, your options are: update to the latest version of the plugin (often the fix is already there), find an actively maintained alternative, or file a support request with the plugin author.

What PHP Version Should You Target?

As of 2026, WordPress officially recommends PHP 8.0 or higher and requires PHP 7.4 minimum. The current stable releases are PHP 8.2 and 8.3.

• PHP 8.1 has broad compatibility across the plugin ecosystem and was the dominant recommended version through 2024.
• PHP 8.2 is well-supported by major plugins and offers additional improvements. A reasonable target for most sites.
• PHP 8.3 is the latest stable branch and has good compatibility with actively maintained plugins, but some less-updated plugins may flag warnings.

Starting with PHP 8.1 or 8.2 is a sensible choice for most WordPress sites in 2026 — broad compatibility, meaningful performance gains over PHP 7.x, and active security support from the PHP project.

OPcache: The Companion Configuration That Amplifies PHP 8 Gains

Regardless of PHP version, OPcache should be enabled and properly configured. OPcache stores compiled PHP bytecode in memory so that the interpreter doesn’t have to re-parse and re-compile your PHP files on every request.

Key OPcache settings to verify with your host or server admin:

• opcache.enable=1 — enabled
• opcache.memory_consumption — 128MB or higher for WordPress sites with many plugins
• opcache.max_accelerated_files — set high enough to cache all your PHP files (WordPress core alone has thousands)
• opcache.validate_timestamps=0 — in production, disable file-change checking for maximum performance (not appropriate for active development environments)

PHP 8’s JIT builds on top of OPcache, so if OPcache isn’t properly configured, you won’t get the full benefit of JIT.

How Your Host Determines How Much You Gain

Upgrading PHP on a slow or over-provisioned host improves the PHP execution layer, but doesn’t fix other bottlenecks: slow storage I/O, inadequate RAM, poor server configuration, or network latency to your database.

On a properly architected managed WordPress host, PHP 8.x operates alongside:

• NVMe storage for fast disk I/O
• Redis or Memcached for persistent object caching
• Dedicated PHP-FPM pools per site so one site’s traffic doesn’t affect another
• Full-page caching that bypasses PHP entirely for cached requests

This is why two sites running the same PHP version can have dramatically different real-world performance depending on the underlying hosting infrastructure.

Verifying the Improvement

After upgrading PHP, use these tools to measure the actual impact:

Query Monitor (free WordPress plugin): Shows PHP execution time, database query count and time, and per-plugin timing. Compare a few pages before and after the upgrade to see concrete differences.

New Relic or Kinsta APM (if available through your host): Application performance monitoring that breaks down server-side execution in detail.

WebPageTest or GTmetrix: Run a few test runs before and after — focus on TTFB (Time to First Byte) and server response time, since that’s where PHP version improvements show up.

Don’t expect PHP 8 alone to transform a slow site into a fast one — the gains are real but incremental. Combined with proper caching, optimized database queries, a CDN, and image optimization, PHP 8 is one layer of a complete performance stack.

---

Ready to Actually Run PHP 8 Well?

The PHP version running on your server is only part of the equation. How that PHP environment is configured, what it sits alongside (Redis, OPcache, full-page caching), and what hardware it runs on all determine what your visitors actually experience.

Rocket.net runs WordPress on PHP 8.x by default with OPcache and Redis object caching pre-configured — the infrastructure is already set up to get the most out of modern PHP without requiring manual server tuning. If you’re currently on a host that requires manual configuration to enable basic optimizations like OPcache, it may be worth reconsidering whether you’re spending time on things that should be handled at the infrastructure level.