Free tools Windows power users keep installed
One-click scans. No signup required.
The durable fix is to move the site to a supported PHP release, but only after a backup, staging test, and compatibility check. PHP 8.3 is WordPress Core’s minimum recommended version in its spring 2026 clarification; PHP 7.4 is the minimum supported floor from WordPress 7.0, not an ideal long-term target. Upgrade the runtime, theme, plugins, and server configuration as one controlled change, then add OPcache, page caching, and persistent object caching where they fit. If the host cannot provide a supported PHP branch and adequate resources, migrate the site.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Why an old PHP version makes WordPress slow
Every uncached WordPress request runs PHP code. The runtime loads WordPress core, the active theme, plugins, database queries, scheduled tasks, and any custom code before it can send HTML to a visitor or administrator. PHP branches that have reached end of life no longer receive upstream performance and security fixes. WordPress Developer Resources notes that newer PHP versions contain both security and performance improvements.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
That does not mean PHP is the only possible cause. A site can remain slow after an upgrade if its theme performs expensive work, a plugin repeats database queries, the database is overloaded, pages are never cached, or the server has too little CPU or memory. Treat PHP as one layer of the request path rather than a universal explanation.
WordPress.org wrote in 2018 that updating an older site to a supported version could make it “up to 3 or 4x faster.” That is a general statement, not a guarantee. The result depends on the old runtime, PHP configuration, plugins, theme, database workload, cache hit rate, traffic pattern, and hosting capacity.
#1 Best Overall
Which PHP version should WordPress use now?
WordPress Core’s spring 2026 clarification says PHP 8.3 is the minimum recommended version. The same clarification identifies PHP 7.4 as the minimum supported floor since WordPress 7.0. Those two labels matter:
- PHP 8.3: the recommended baseline stated by WordPress Core for 2026.
- PHP 7.4: a compatibility floor for WordPress support, not a forward-looking performance target. The PHP project has ended upstream support for old branches.
- PHP 5.6, 7.0, 7.1, 7.2, and similar releases: obsolete runtimes that should be treated as an upgrade or migration problem, not as a permanent hosting choice.
Use the newest PHP release that your installed WordPress version, theme, plugins, custom code, and host can pass in staging. Do not jump directly on the production site merely because a version number is newer. Newer PHP is not guaranteed to be backward-compatible with old themes and plugins.
Start with a baseline instead of guessing
Measure the current site before changing PHP. A baseline tells you whether the delay is in PHP execution, database work, cache misses, static delivery, or the server itself, and it gives you a rollback comparison.
Record the software and hosting state
- PHP version and important PHP settings shown by your host or WordPress Site Health.
- WordPress core version, active theme, parent theme if applicable, and every active plugin.
- Database engine and version, database size, and any host-imposed CPU, memory, process, or connection limits.
- Whether page caching, object caching, a content delivery layer, or server-level caching is enabled.
- The hosting plan and whether it provides staging, restorable backups, error logs, OPcache controls, and a persistent object-cache service.
In the dashboard, open Tools > Site Health > Info and save the relevant sections. Your hosting control panel may show PHP under labels such as “PHP Manager,” “MultiPHP,” or “Runtime.” Labels differ by provider, so use the host’s documented path rather than changing an unknown setting.
Measure representative requests
Check the home page and several real page types: a post, an archive, search, a form, the login screen, an administrator screen, and any ecommerce or membership flow. Compare an uncached request with a cached repeat request where your setup permits it. Record time to first byte (TTFB), total load time, and whether the response is served from cache.
Also separate HTML generation from static delivery. A slow first byte points toward PHP, database, web-server, or host-resource work. A fast first byte followed by a slow page often points to large images, JavaScript, CSS, or delivery capacity. Do not attribute every delay to PHP: WordPress optimization guidance specifically calls out repeated queries, TTFB, server software, and host resources.
Capture errors and resource pressure
Save the PHP and web-server error logs before the upgrade. Note fatal errors, deprecation warnings, memory exhaustion, database connection errors, and timeouts. If the host exposes graphs, record CPU, memory, disk I/O, PHP workers, and database usage during a busy period. A baseline made only during a quiet visit can hide the problem that visitors experience during traffic spikes.
Back up the site and build a staging copy
A PHP change can make a previously working plugin or custom snippet fail immediately. Create a restorable backup before updating anything, and verify that the backup contains both the database and all files, including uploads and configuration files. A backup that has never been tested is not a rollback plan.
- Export or snapshot the database using the method supplied by your host or backup system.
- Copy the complete WordPress files, including
wp-content, uploads, themes, plugins, and configuration. - Save the current PHP version, relevant ini settings, cache settings, cron configuration, and error logs.
- Clone the site to staging if your host supports it. Protect staging with a password and prevent it from being indexed.
- Record how to switch PHP back or restore the previous server image before you begin.
Test the restore process on staging or another safe location. The goal is not simply to possess an archive; it is to know that you can recover a working site if the production upgrade fails.
Remove compatibility blockers before changing PHP
Inventory every component that executes PHP. Old sites frequently contain deprecated syntax, removed APIs, unsupported extensions, abandoned plugins, or custom code copied into a theme’s functions.php file. WordPress advises checking compatibility because newer PHP releases can expose defects in old plugins and themes.
Update in a controlled order
- On staging, update WordPress core to the latest version that your site can safely use.
- Update the active theme and its parent theme, then update plugins one group at a time.
- Remove inactive, abandoned, or duplicate plugins instead of carrying them into the PHP upgrade.
- Ask the developer of any essential component for its supported PHP range and a current release.
- Replace components that have no maintenance path. Do not keep an end-of-life plugin solely because it is familiar.
Test after each meaningful group of changes. If several plugins are updated and PHP is changed at the same time, a later failure is much harder to attribute.
Watch for common breakage
- Fatal errors caused by removed or renamed PHP functions.
- Warnings that become errors under stricter type handling.
- Database code that relies on old extensions or unsafe query behavior.
- Shortcodes, widgets, blocks, forms, or checkout code that stops rendering.
- Custom integrations that expect an old API response or old PHP serialization behavior.
Do not hide these failures by leaving display errors disabled and moving on. Use the logs to identify the component, update or replace it, and repeat the staging test.
Upgrade PHP safely
Once staging passes, schedule the production change during a period when you can monitor the site and restore it. The exact control-panel labels vary, but the sequence is consistent.
- Put the site in maintenance mode only if the change requires it; avoid an unnecessarily long outage.
- Confirm that the production backup completed and that the restore path is available.
- Select the tested PHP release in the host’s PHP or runtime manager. Use the newest tested release available to your site, with PHP 8.3 as the WordPress Core recommended baseline for 2026.
- Clear opcode, page, object, and application caches so old code is not served after the runtime changes.
- Open the home page, representative content, login, dashboard, forms, uploads, scheduled tasks, and integrations.
- Review PHP and web-server logs immediately and again after normal traffic resumes.
- Keep the old runtime available only as a short rollback measure while you fix identified compatibility issues. Do not treat an exposed end-of-life version as the permanent solution.
If the host offers only PHP 7.4, that may satisfy the WordPress support floor in the cited 2026 clarification, but it leaves the site below the recommended baseline and on a PHP branch without upstream support. Ask when PHP 8.3 will be available and what migration assistance the host provides.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Test the paths visitors and administrators actually use
A home-page check is not enough. Walk through the site as an anonymous visitor, a logged-in user, and an administrator. Include the paths that generate the most business or editorial value.
- Home page, posts, pages, category and tag archives, navigation, and internal search.
- Contact forms, comments, account registration, password reset, and login/logout.
- Media uploads, image processing, scheduled publishing, and any import or export job.
- Administrator screens used for editing, moderation, reports, and settings.
- Ecommerce checkout, payment callbacks, order emails, memberships, bookings, or downloads if present.
- Analytics, advertising, email, API, webhook, and other external integrations.
Watch for both visible defects and silent failures. A page can look correct while a cron job, email, webhook, or background queue is failing. Check logs and server resource graphs while exercising these paths. If one component fails, disable or replace that component in staging, then retest; do not revert the entire site indefinitely to an unsupported PHP branch.
Enable caching that matches the workload
PHP upgrades reduce execution cost, but caching prevents the same work from being repeated. Use each layer for the job it is designed to do.
OPcache for compiled PHP
OPcache stores precompiled PHP bytecode so the server does not parse and compile every script for every request. Confirm that it is enabled for web requests, not merely for command-line PHP. The WordPress Hosting Handbook warns that poor sizing reduces its benefit: OPcache needs enough memory and script capacity for the application, and stale or invalidation settings must not serve old code after deployments.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsYour host may expose OPcache status and limits, or it may manage them centrally. If you control the server, check the PHP-FPM or web-server pool used by WordPress rather than assuming the command-line configuration is the same. After changing PHP or deploying code, restart the relevant service or use the host’s cache reset so the new scripts are loaded.
Page caching for public responses
Page caching stores generated HTML for pages that can be shared among visitors. It can sharply reduce PHP and database work on public posts and archives. Configure cache invalidation for publishing, editing, menus, widgets, and theme changes. Exclude personalized or stateful endpoints such as logged-in dashboards, carts, checkout, account pages, and pages whose output depends on a visitor’s session.
Verify behavior instead of assuming a cache is active: make a request, inspect the response headers or host dashboard, publish a small change in staging, purge the relevant cache, and confirm that the new content appears. An incorrectly cached form or account page is a correctness and privacy problem, not merely a speed issue.
Persistent object caching
A persistent object cache keeps frequently reused database results between requests. It is useful when the host provides a compatible cache service and the WordPress integration is configured correctly. Check hit behavior, memory usage, and invalidation. A persistent cache cannot repair an inefficient query or an undersized database server; it reduces repeated work when the underlying data and cache policy are appropriate.
Find database and TTFB bottlenecks after PHP is current
If the site is still slow on a supported PHP release with sensible caching, investigate the request path rather than continuing to change PHP versions. Repeated database queries add trips to the database and can overwhelm it during traffic spikes.
Look for query-heavy pages
- Identify templates that load many related posts, products, users, or metadata rows.
- Check search and filter endpoints, which often perform uncached or broad queries.
- Inspect scheduled imports, analytics collectors, and background tasks that compete with visitor requests.
- Review plugins that run work on every page, even when the feature is not visible.
Use the host’s slow-query or application profiling tools if available. Compare a cold request with a warm cached request and note whether TTFB falls when the database is quiet. Optimize or replace the component responsible rather than adding layers of cache that conceal an unbounded query.
Check server capacity
High CPU, exhausted memory, too few PHP workers, saturated disk I/O, or a constrained database connection pool can all raise TTFB while PHP itself is current. Ask the host for resource graphs and limits during the slow period. If the site shares a busy server, the practical fix may be more capacity or a different hosting tier.
When hosting migration is the correct fix
Move the site when the current provider cannot supply a supported PHP branch, reliable backups, staging, OPcache controls, a compatible persistent object-cache service, or enough CPU, memory, and database capacity. Hosting is part of the performance stack; a PHP upgrade alone cannot correct an undersized or poorly configured server.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11| Option | Primary benefit | Main risk | Evidence to check |
|---|---|---|---|
| PHP upgrade | Newer runtime performance, security, and support | Theme, plugin, or custom-code incompatibility | Staging tests, error logs, and developer compatibility statements |
| Page or object caching | Less repeated PHP and database work | Stale content or cache incompatibility | Cache-hit behavior, invalidation, and dynamic-endpoint exclusions |
| Theme or plugin replacement | Removes legacy bottlenecks and unsupported code | Feature and data migration work | Maintenance status, PHP support, and staging regression tests |
| Hosting migration | Supported runtime plus better server and cache resources | DNS, migration, and operational effort | PHP versions, backups, staging, OPcache, object-cache availability, and resource limits |
Before signing up with another provider, confirm the exact PHP versions available in your region and plan, whether staging is included, how restores work, who manages OPcache, and whether object caching is a real service rather than a marketing label. Plan DNS and email changes separately from the PHP change so a failed application test is not confused with a migration problem.
Troubleshooting branches
The site shows a blank page or fatal error after the switch
Use the host’s error log to identify the file and plugin or theme named in the fatal error. If staging is available, reproduce the problem there, update or replace the named component, and retest. If production is unavailable, restore the verified backup or temporarily return to the previous runtime only long enough to repair compatibility. Keep the end-of-life runtime out of the final configuration.
The site works, but the dashboard is still slow
Administrator pages are often uncached and may load reports, revisions, external requests, or large option sets. Check plugin screens, scheduled tasks, and database queries separately from public-page performance. Public page caching will not make an uncached report screen fast.
Public pages are fast for one visitor but slow under traffic
Compare cache hits and misses, then inspect PHP worker limits, CPU, memory, and database connections during the spike. A warm page cache can hide an undersized server until a purge, content update, or uncached endpoint creates concurrent work.
PHP is current but TTFB has not improved
Return to the baseline. Examine repeated queries, slow database statements, uncached dynamic endpoints, web-server configuration, and host capacity. If static files are the slow part after TTFB is acceptable, optimize delivery and assets rather than changing PHP again.
Updating a plugin fixes one error but creates another
Restore staging, update one component at a time, and test the affected workflow after each change. Look for interactions between the plugin, the theme, and custom code. If the component is abandoned or cannot support the target PHP release, replace the feature rather than freezing the entire site on an obsolete runtime.
A maintenance routine that prevents the problem returning
- Keep WordPress core, the active theme, and plugins on maintained releases.
- Review the PHP version after host changes and before renewing a hosting plan.
- Maintain automated backups and periodically perform a test restore.
- Use staging for PHP, core, theme, and plugin changes that can affect production.
- Monitor error logs, TTFB, cache-hit behavior, and server resource graphs.
- Remove abandoned plugins, unused themes, and obsolete custom code.
- Document the tested PHP version, cache purge procedure, rollback method, and critical site paths.
The practical order is straightforward: measure, back up, stage, update components, move to the newest tested supported PHP release, test real workflows, enable correctly sized caches, and investigate database or server limits that remain. If the host cannot support that sequence, changing hosts is part of the fix.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
