Skip to content
Igor Kucurski
Menu
WordPress & PHPSecurityServersEmailFor agenciesCase studiesAboutRequest a free check

WordPress & PHP

Your site has no maintenance. I can fix that without breaking it.

Most WordPress sites I see aren't broken. They're just old: an outdated PHP branch, plugins nobody updates, wp-cron running on every page view. I update them safely, one site at a time, with a backup and a way back.

Request a free check →How to check your version

Services

What I do

PHP upgrades

Assess compatibility, back up, switch the PHP version per site, then check the site and logs afterwards. If something breaks, we roll back.

Fixes after updates

Pages not rendering, white screens, plugin conflicts and errors after a WordPress or PHP update, in WordPress and other PHP apps like FreeScout.

Performance

Bot and scraper traffic, an oversized database, caching, and moving wp-cron to a real system cron job.

Migrations

Moving sites to a new server or panel such as CloudPanel, including DNS, IPv6 and MySQL 8.4 upgrades.

Worth knowing

PHP 8.2 security support ends on 31 December 2026

After that date the PHP project stops publishing security releases for 8.2, as it already has for 7.4, 8.0 and 8.1. Some distributions and hosting panels backport fixes for a while, so check with your host what applies to you. If you're on 8.2 or older, now is a good time to plan a move to 8.3 or 8.4. Source: php.net/supported-versions.

Check it yourself

See your versions in two minutes

If you got an email from me about your site, here's how to verify it without trusting me.

Your WordPress version

  • Log in to WordPress and open Dashboard → Updates. It shows your version and whether a newer one exists.
  • Or open Tools → Site Health → Info → WordPress.
  • Compare it with the latest release on wordpress.org/download/releases.

Your PHP version

  • In WordPress: Tools → Site Health → Info → Server shows the PHP version.
  • In your hosting panel (cPanel, Plesk, CloudPanel, DirectAdmin) look for PHP version or PHP selector.
  • Supported branches are listed at php.net/supported-versions.

An old version number doesn't automatically mean you're vulnerable

Linux distributions and hosting panels often backport security fixes into older versions without changing the version number. WordPress also ships security releases for older branches. So a version check from outside tells you what to look at, not whether the fix is missing. I confirm that on the server before calling anything unpatched.

How it works

Backup first, always

  1. 01

    Check

    I look at the versions, plugins and server, and tell you what needs to change and what the risk is.

  2. 02

    Update

    Full backup, then the change, one site at a time. You know in advance what will happen.

  3. 03

    Verify

    I test the important pages and the error log afterwards. If needed, we roll back to the backup.

Real work

Recent WordPress & PHP jobs

UK online store, WooCommerce on a VPS

WooCommerce store overloaded by scrapers

17.8→~2server load

Problem
CPU and memory kept spiking and the store slowed down for real customers.
Cause
A site-copying scraper spread across roughly 4,400 IP addresses, plus aggressive crawlers, and WP-Cron running on every page view.
What I did
  • Identified and blocked the scraper network from the access logs
  • Rewrote robots.txt to rein in crawlers that respect it
  • Moved wp-cron to a real system cron job
Result
Server load dropped from 17.8 to about 2.

Tools and stack

  • WordPress
  • WooCommerce
  • PHP 7.4 → 8.4
  • MySQL / MariaDB
  • Redis
  • FreeScout

Not sure what's wrong? Start with a free check.

Send me your domain and a sentence about the problem. I'll tell you what I checked, what I found, and what can't be confirmed from outside. No passwords needed.

Request a free check →