Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Speed & performance · Explainer

Does the PHP Version Affect WordPress Speed?

Short answer

Yes, the PHP version affects WordPress speed. WordPress runs on PHP, so every page request runs PHP code, and WordPress's own Site Health docs say newer PHP versions are created with increased performance in mind. Updating from an old, unsupported version to PHP 8.3 or newer can cut server response time, but the size of the gain depends on your theme, plugins, and hosting.

Key takeaways

  • WordPress recommends PHP 8.3 or newer, and still runs on PHP 7.4 or newer, though those old versions no longer get security fixes.
  • Each PHP branch gets 2 years of active support and 2 more years of security fixes, then reaches end of life.
  • PHP 8.2 stops getting security fixes on 31 December 2026, so sites still on it should plan an update.
  • A good time to first byte is 0.8 seconds or less, and a poor one is over 1.8 seconds, according to web.dev.
  • Lighthouse flags server response times over 600 milliseconds on the main document request.
  • PHP is only one speed factor; caching, your theme, plugins, and hosting matter too.

Does the PHP version affect WordPress speed?

Yes, the PHP version affects WordPress speed.

WordPress is written in PHP, so the server runs PHP code for every page that is not served from cache. When that code runs faster, the page reaches the visitor sooner.

WordPress.org states in its Site Health screen docs that newer PHP versions are created with increased performance in mind, so you may see a positive effect on your site's performance. That makes PHP one of the few speed settings you can change without touching your theme or content.

It will not fix a slow host or a heavy page, but it removes one drag on every uncached request. The rest of this guide explains how PHP shapes speed, which version to use, and how to measure the change.

What does PHP do when someone visits your WordPress site?

PHP builds the page on the server by running WordPress core, your theme, and your active plugins, then sends the finished HTML to the visitor's browser.

Each visit that misses the cache starts this build step. PHP reads the database, runs your theme templates, and runs each active plugin's code for that page. The result is one HTML document that the browser can show.

If the same page is served from a full-page cache, PHP may not run at all for that visit. That is why caching can matter more than the PHP version on sites with many repeat visitors.

PHP workers handle these build jobs. A worker is one PHP process that can build one page at a time, so a busy site needs enough workers to keep up. Learn how PHP workers handle simultaneous requests before you judge a slow build step.

Why do newer PHP versions run faster?

Newer PHP versions run faster because each release refines the engine that runs your code, fixes slow paths, and drops support for old, slow ways of writing code.

The PHP team supports each branch for 2 years of active fixes, then 2 more years of security-only fixes, so old branches stop getting improvements. That is one reason WordPress.org warns that sites on old PHP may miss out on both speed gains and security fixes.

Chrome's Lighthouse docs list PHP OPcache among the server tools that cut response time. OPcache stores compiled PHP code in memory, so the server skips the compile step on repeat requests.

A newer PHP version also pairs with newer WordPress releases, which expect recent PHP. WordPress.org recommends PHP 8.3 or greater as of November 2026, and that advice moves forward as new PHP branches arrive.

Which PHP version should you use for WordPress?

Use PHP 8.3 or newer for WordPress, since WordPress.org recommends PHP 8.3 or greater as of November 2026.

The table below uses the support dates on the PHP supported versions page, checked in November 2026.

PHP versionActive support untilSecurity support untilStatus in November 2026
8.231 December 202431 December 2026Security fixes only
8.331 December 202531 December 2027Security fixes only
8.431 December 202631 December 2028Actively supported
8.531 December 202731 December 2029Actively supported

WordPress still runs on PHP 7.4 or newer, but WordPress.org warns that those versions have reached end of life and may expose your site to security risks. The WordPress requirements page lists PHP 8.3 or greater, MariaDB 10.11 or greater, or MySQL 8.4 or greater.

PHP 8.5 is the newest branch, released on 20 November 2025, but your host and plugins must support it first. Our guide to which PHP version to use for WordPress walks through that choice in more detail.

PHP 8.2 stops getting security fixes on 31 December 2026, only weeks after this guide was checked. If your site still runs PHP 8.2, plan the move now rather than waiting for the deadline.

How much faster will your site get after a PHP update?

There is no fixed speed gain from a PHP update, because the gain depends on your theme, plugins, hosting, and how much of your traffic is cached.

A simple site on a fast host may gain only a small amount, while a site with heavy plugin code may gain more. No official WordPress or PHP page gives a single percentage for WordPress sites, so treat any exact percentage you see elsewhere with care.

WordPress.org only promises that you may see a positive effect on performance, not a set amount. That is still worth doing, because the update also brings security fixes and keeps your site on a supported branch.

What you can measure is your own server response time before and after the change. The next sections show how to check your version and measure the result.

How do you check which PHP version your site uses?

Open Tools, then Site Health, then Info in your WordPress dashboard and expand the Server section to see your PHP version.

  1. Log in to your WordPress dashboard.
  2. Go to Tools, then Site Health.
  3. Open the Info tab and expand Server.
  4. Read the PHP version line and note the number.

Site Health also warns you when your PHP version is out of date. Its Status tab shows the message "Your site is running an outdated version of PHP, which requires an update" when a newer version is due.

If your host panel lists a PHP version selector, check that number too. The panel shows what your host will use after a change, while Site Health shows what your site uses now.

How do you measure the speed change after updating PHP?

Measure time to first byte (TTFB) before and after the update, then compare the two numbers on the same page.

TTFB is the time from the start of navigation until the first byte of the response arrives. Web.dev says most sites should aim for a TTFB of 0.8 seconds or less, and values over 1.8 seconds count as poor.

TTFB covers redirect time, DNS lookup, connection and TLS setup, and the request itself, so it captures the server work PHP does.

Lighthouse adds a stricter check. Its audit fails when the browser waits more than 600 milliseconds for the server to answer the main document request. You can measure TTFB in Chrome DevTools on the Network tab, or with WebPageTest, which web.dev lists as a lab tool for this metric.

Test the same page 3 times before the change and 3 times after it, then compare the middle value from each set. Test at a quiet time of day and avoid changing plugins or themes between the two sets, or you will not know what caused the change.

Faster server response also supports search visibility, as our guide to whether page speed affects SEO explains. Speed is one of several signals search engines weigh, so a faster server helps without being a magic fix.

What else affects WordPress speed besides PHP?

Caching, hosting, your theme, and your plugins often matter more than the PHP version, because they decide how much work PHP has to do at all.

  • Full-page caching serves saved pages without running PHP, so it can cut server work to near zero for repeat visits.
  • Hosting sets the CPU, memory, and PHP worker limits your site runs under.
  • A heavy theme or a slow plugin adds code to every page build, which no PHP version can remove.
  • Large images and extra scripts slow the browser after the server has answered, so they do not show up in TTFB.

Chrome's Lighthouse docs give WordPress-specific advice here: pick a lightweight theme, use full-page caching, and switch off plugins you do not need. That advice sits next to its note on server response times.

Our guide to speeding up WordPress walks through these fixes in order.

If your host is the limit, our guide to testing hosting speed before you buy shows how to compare hosts.

Is it safe to update PHP on a live WordPress site?

Updating PHP is usually safe when your WordPress core, theme, and plugins are up to date, but you should still test it on a staging copy first.

Old plugins or themes may use code that a new PHP version no longer accepts, and that can break a page with an error. Update WordPress, your theme, and all plugins first, then switch PHP on a staging site and click through key pages.

If your host has no staging tool, switch PHP at a quiet time and keep a backup you can restore. If a page breaks, switch back to the old PHP version and ask the plugin or theme author about support for the new version.

A PHP update is also a good time to clear old plugins you no longer use. Fewer plugins mean fewer chances of a clash with the new version.

What mistakes should you avoid?

Do not jump to the newest PHP release on a live site without checking that your theme and plugins support it.

  • Updating PHP without a backup, so a broken page leaves you with no quick way back.
  • Staying on PHP 8.2 past 31 December 2026, when its security fixes end.
  • Judging the change from one test, since a single TTFB reading can swing with network noise.
  • Updating PHP and changing plugins at the same time, so you cannot tell which change helped or hurt.
  • Ignoring the Site Health warning about old PHP until a security issue forces a rushed move.

Frequently asked questions

Will updating PHP break my WordPress site?

It can break a site if a theme or plugin uses code the new PHP version no longer accepts. Update WordPress, your theme, and all plugins first, then test the new PHP version on a staging copy. If a page breaks, switch back to the old version and ask the theme or plugin author about support before you try again.

Does PHP 8.5 work with WordPress?

PHP 8.5 was released on 20 November 2025 and is actively supported until 31 December 2027. WordPress recommends PHP 8.3 or newer, so 8.5 meets that bar, but your host must offer it and your theme and plugins must support it. Test it on a staging copy before you switch a live site to it.

How often should I update PHP?

Check your PHP version at least once a year. Each PHP branch gets 2 years of active support and 2 more years of security fixes, then reaches end of life. Move to a supported branch before the security fixes end, and watch the Site Health screen, which warns you when your version is out of date.

Can I change the PHP version myself, or do I need my host?

Many hosts let you pick a PHP version in the hosting panel, under a PHP settings or PHP version section. Some hosts need a support request to change it, and a few managed hosts update it for you. Check Tools, then Site Health, then Info in WordPress to see the version your site uses now.

Does the PHP version affect SEO?

Only indirectly, through speed. A newer PHP version can cut server response time, and faster pages give visitors a better experience, which search engines weigh among other signals. The PHP version itself is not a ranking factor, so treat it as one speed fix among several, not as an SEO fix on its own.

What PHP version is too old for WordPress?

Anything below PHP 7.4 is too old for current WordPress, and PHP 7.4 itself has reached end of life. PHP 8.2 is the next cutoff, since its security fixes end on 31 December 2026. WordPress recommends PHP 8.3 or newer, so anything below 8.3 should be on your update list.

Sources

  1. Requirements WordPress.org
  2. PHP: Supported Versions PHP.net
  3. Site Health screen WordPress.org
  4. Time to First Byte (TTFB) web.dev
  5. Reduce server response times (TTFB) Chrome for Developers

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test