Update PHP in 4 Easy Steps (Your Site Is Probably Years Out of Date)
Most small business sites are running an outdated PHP version that quietly costs them speed and security. Here's how to check it, back up, test, and switch.
By Patrick Moore
To update PHP in 4 steps: (1) check your current version in your hosting dashboard or a plugin like Display PHP Version, (2) back up your full site — files and database, (3) test compatibility on a staging site or with a checker plugin, then (4) switch to a current supported version in your control panel and re-test every key page and form. For most hosts it's a 10-minute job, and a current PHP version makes your site faster and closes security holes for free.
Here's a bet I'd make about your website: it's running a version of PHP that stopped getting security updates years ago. You don't know it. Your host didn't tell you. And it's quietly costing you.
PHP is the code that runs WordPress and most of the web. Old versions are slower, no longer get security patches, and eventually get dropped by the plugins and themes you depend on. Updating it isn't "developer stuff" you can ignore — it's a free speed and security win sitting in your hosting panel.
Running outdated PHP is a silent tax on speed and security — and most owners are paying it without knowing.
01Why an Old PHP Version Actually Costs You
This isn't theoretical. I've inherited sites stuck on PHP 7.0 — a version that's been dead for years — and just bumping them to a current release shaved load time without touching a single line of design.
The danger isn't only speed. When a version stops getting security patches, every newly discovered hole stays open forever. And at some point WordPress core or a plugin you rely on drops support for it, and something breaks with no warning.
Outdated PHP vs a Current Version
- Noticeably faster page loads
- Active security patches
- Full plugin and theme compatibility
- Ready for the next WordPress update
- Slower under the same traffic
- No security fixes for new exploits
- Plugins start failing without warning
- Eventually blocks WordPress core updates
02Step 1: Find Out What You're Actually Running
Before you change anything, know your starting point. Most hosts show your PHP version right in the dashboard — in cPanel it's under "MultiPHP Manager," and managed hosts usually have it under a PHP or tools section.
Not sure where to look? Install a free plugin like "Display PHP Version." It shows your number on the WordPress dashboard in two clicks. Write down what you're on so you can compare and roll back if needed.
What you're checking for
- The exact PHP version number your site runs today
- Whether it's still officially supported (anything below 8.x is a red flag)
- Which control panel your host uses to change it
- How far behind the current release you are
03Step 2: Back Up Before You Touch Anything
Never change PHP on a live site without a full backup. I mean the whole thing — files and database, not just one or the other.
If something breaks after the switch, a complete backup means you roll back in minutes instead of scrambling. Better yet, do the work on a staging copy first so your live site never feels the experiment. Most decent hosts give you one-click staging now.
A backup turns a broken update from an emergency into a five-minute reset.
04Step 3: Test Compatibility Before You Flip the Switch
The thing most likely to break is an old plugin or theme that isn't ready for the new PHP version. So test before you commit, not after.
Use a staging site, or run a PHP compatibility checker plugin against your install. It flags the themes and plugins that aren't ready. Update or replace anything outdated first — that's almost always the real fix.
Before switching, confirm
- Every active plugin is updated to its latest version
- Your theme supports the target PHP release
- Any compatibility-checker warnings have been resolved
- Abandoned plugins with no updates in years are replaced
05Step 4: Switch the Version and Re-Test
Make the change cleanly
- 1
Select the new version
In your hosting control panel, pick a current supported PHP release. Aim for the latest stable version your host offers.
- 2
Save and apply
Save the change. On most hosts it takes effect instantly — no restart drama.
- 3
Re-test every key page
Open your homepage, key landing pages, checkout, and contact form. Click through like a real visitor.
- 4
Test the things that make you money
Submit a form. Run a test order. Confirm email notifications fire. If it earns leads or revenue, verify it works.
06What If Something Breaks?
Here's the common gotcha: you flip the version and a plugin or theme throws an error. Don't panic, and absolutely don't give up and stay on ancient PHP.
The fix is simple. Roll back to your old version, update the plugin that broke, then try the switch again. Nine times out of ten the culprit is one outdated plugin — fix it and the upgrade goes through clean.
Check your version, back up your site, test for compatibility, then switch — and you've turned a silent speed and security tax into a free upgrade in about ten minutes.
FAQ
Frequently asked questions
- What is PHP and why does my website need it?
- PHP is the programming language that runs WordPress and most of the web. It's the code that builds your pages when someone visits. Your site needs a current, supported PHP version because old ones are slower, no longer receive security patches, and eventually stop being supported by WordPress core, plugins, and themes.
- How do I check what PHP version my site is running?
- Log into your hosting dashboard — in cPanel it's under "MultiPHP Manager," and managed hosts list it under PHP or tools settings. If you can't find it, install the free "Display PHP Version" plugin, which shows your version right on the WordPress dashboard. Note the number before you change anything so you can compare or roll back.
- Should I update PHP myself or hire a developer?
- If you can back up your site and your host has one-click staging, most owners can update PHP themselves in about ten minutes. Hire help if you run a complex site with many plugins, no backup system, or revenue-critical functions like checkout. The risk isn't the switch itself — it's not having a backup or staging copy to fall back on.
- Will updating PHP break my WordPress site?
- It can if an outdated plugin or theme isn't compatible with the new version, which is why you back up and test first. Run a compatibility checker or use a staging site, and update your plugins and theme before switching. If something breaks, roll back, update the offending plugin, and try again.
- What PHP version should I update to?
- Aim for the latest stable PHP release your host offers — generally PHP 8.x or higher. Anything in the 7.x range or older is no longer receiving security updates and should be upgraded. Pick the newest version your plugins and theme support after testing for compatibility.
- How often should I update my PHP version?
- Check your PHP version at least once a year, since each major release is supported for roughly two to three years before security updates stop. When your version approaches end-of-life or your host offers a newer stable release, plan an upgrade. Staying current keeps your site fast, secure, and compatible with future WordPress updates.
Your website shouldn't just look good. It should generate business.
Whether you need a better website, stronger SEO, or smarter marketing, I'll help you turn more visitors into leads, calls, and customers.