A website upgrade turns an existing site into a fast, secure and current one without throwing away what already works: the content, the Google rankings and the customers who know it. I upgrade WordPress sites and PHP systems for businesses, from the infrastructure to the design, and I measure before and after.
A site that went live five or seven years ago doesn't break in one day. It wears out: slower loading, plugin warnings, PHP 7 on the server, a design that looks like the year it was built. Below: what an upgrade includes, when a rebuild is better, what it costs, and which mistakes turn an upgrade into an outage.
What a website upgrade is, and what it isn't
Upgrading an existing website (a refresh, a revamp) means working on four layers of a live site: infrastructure (PHP, WordPress, plugins, server), performance (speed and Core Web Vitals), security, and the visible layer (design, UX, mobile). The URLs, the content and the Google rankings stay put. A rebuild starts from zero and puts all of that at risk.
Most sites that reach me run WordPress, where the wear is especially fast. Per WordPress.org, 37% of WordPress sites still run PHP 8.1 or older, with no security updates, and PHP 8.2 joins them on December 31, 2026. A site not upgraded in the last two years almost certainly sits on one of them.
Why sites wear out even when nobody touches them
Because everything around them moves. Plugins get security updates nobody installs (91% of the 2025 vulnerabilities were in plugins), PHP versions reach end of life, Google tightens its speed metrics, and visitors arrive on phones that didn't exist at launch. A site that stands still goes backwards.
And an upgrade isn't clicking "Update all". A blind update on an old site is the classic route to a white screen, and to WordPress repair instead of a planned upgrade. A real upgrade happens on a copy, layer by layer, with tests and a way back.
Website upgrade or rebuild: what's right for your site
The first question on every first call. The answer depends on the state of the site, not its age:
| State of the site | Upgrade | Rebuild |
|---|---|---|
| Good content, dated design | A design refresh, the content stays | You pay twice for the same content |
| Slow site (LCP over 4 seconds) | PHP 8, caching, images, scripts: usually back to green | A new site with 40 plugins is just as slow |
| PHP 7.x and plugins not updated for years | An infrastructure upgrade in stages, on staging | Only if the theme is abandoned and the code cannot run on PHP 8 |
| The site was hacked | Clean-up, hardening and upgrade, content kept | Same password, same vulnerable plugin, hacked again |
| Abandoned theme, old page builder, undocumented custom code | Costs as much as a rebuild, leaves a weak base | A rebuild with content migration and 301 redirects |
| Wix or a closed platform that cannot do what the business needs | Nothing to upgrade inside the platform | A move to WordPress that keeps the URLs |
| The business model changed (from brochure to store) | Patches on a structure not built for it | Planning and a rebuild |
My rule for the decision
If more than 70% of the content and structure stays, and the theme is still updated, it's an upgrade. If the structure, the business model or the platform changes, it's a rebuild. Either way, the decision comes after the diagnosis. Often the site is in better shape than its owner thinks and needs only an infrastructure upgrade and a few hours of speed work.
Not sure whether to upgrade or rebuild? Send me your site address for an honest answer: upgrade, rebuild, or leave it as it is.
A free 30-minute call, no obligation · reply within 24 hours
Book a free callWhat my website upgrade includes: PHP 8, WordPress, Core Web Vitals
The tracks I actually deliver. Take one or combine several, but in order: infrastructure, then performance, then design. A new design on PHP 7 is fresh paint on a damp wall.
- Infrastructure: PHP 8, WordPress, plugins and theme. A PHP upgrade with a compatibility scan of the custom code, WordPress and plugins updated in layers, abandoned plugins replaced, unused ones removed. Sites often arrive with 40+ plugins and leave with 15-20, without losing a feature.
- Performance and Core Web Vitals. Server caching, right-sized WebP and AVIF images, local fonts instead of Google Fonts, third-party scripts loaded only when needed, PageSpeed Insights before and after. Target: mobile LCP under 2.5 seconds, INP under 200 ms, CLS under 0.1.
- Security. A scan, server and wp-admin hardening, two-factor authentication, automatic backups, a check for foreign code. A hacked site is cleaned and closed first. Details in WordPress security.
- Design and user experience. A refresh of the theme or a new child theme: typography, spacing, mobile, forms, contact buttons where they belong. Content and structure stay; the site looks like 2026.
- Technical SEO and keeping rankings. Every URL mapped first, a 301 for every change, titles and meta descriptions, schema (JSON-LD), a sitemap, Search Console after launch. Then organic SEO runs on infrastructure that's finally ready for it.
- Accessibility and privacy. A WCAG 2.2 AA accessibility check, and forms and privacy policy reviewed so visitors know what happens to their data. Not legal advice, but part of the upgrade.
- Platform or server move. From Wix, Squarespace or a ready-made theme to WordPress, or to faster hosting, keeping the URLs, with no downtime.
A custom PHP system instead of WordPress? The PHP 8 upgrade is exactly what I do as a PHP developer: same code, same server, 1.5 to 2 times faster.
How I work: 6 steps from the free call to 30 days of monitoring
You send an address. I check the PHP and WordPress versions, PageSpeed, an external security scan and the URL structure, and tell you what I found and whether an upgrade is worth it at all. Prefer to write? Use the contact page.
With access to site and server: every plugin, the theme, custom code, database, backups. The result is a one- or two-page report - what's risky, slow or redundant, and the price of each track. Yours even if you don't continue with me.
A defined scope, a fixed price and at least one success metric: mobile PageSpeed score, LCP, PHP version or plugin count. No surprises halfway.
A copy of the site on the same server, where PHP 8 goes in, plugins are updated, code is fixed and the design is built. The live site keeps selling.
Every page that brings in leads checked on desktop and mobile, forms actually submitted, payments tested in a sandbox, metrics measured against the starting point. I move on only when the comparison is positive.
The switch in a quiet window, error and Search Console monitoring, free fixes for anything that comes up, and a handover document: what changed, which versions run, how to back up and roll back.
Timelines: infrastructure 3-7 working days, speed one to two weeks, design 3-5 weeks, a platform move 4-8 weeks. You prepare: hosting and domain access, a list of the pages that bring leads, and an hour from someone who knows the site.
Why a developer, and not "someone who knows WordPress"
An upgrade looks simple until something breaks halfway: a payment plugin that isn't PHP 8 compatible, a theme whose author vanished in 2021, a function in functions.php nobody remembers. At that point, a developer who reads and writes PHP turns "we need a rebuild" into a one-hour fix; someone who only knows the dashboard can't.
The closest example is this site. In September 2026 its home page scored 64 on mobile PageSpeed, with LCP at 7.9 seconds. No rebuild, no new server, not one line of content changed - only how fonts, scripts and images load - and the score rose to 100, LCP down to 1.9 seconds. I keep such measurements for every project.
No upgrade touches a live site without three things: a full backup tested by a restore, a staging site where every change happens first, and a way back that takes minutes. And one more: every URL the site had before still answers after, or has a 301 redirect. Seven years of rankings aren't worth trading for a pretty design.
Who I am, and why I do the upgrades myself
I'm a developer with 25+ years in production: Tech Lead at William Hill Online on systems serving millions of users, then development at Mars Media Group and senior full-stack development at BuyMe. There a version upgrade is a planned event with a backup, a test environment and a way back, because every minute of downtime costs money. I bring the same routine to a five-person business.
Independent since 2006, full time since 2019, I build and upgrade WordPress and WooCommerce sites, PHP and Laravel systems and AI systems, and develop verifystring.com, security for AI systems. No subcontractors: the person who diagnoses your site is the one who upgrades it and answers when something breaks. Background on LinkedIn, and more about me here.
Common website upgrade mistakes, and how I avoid them
- Updating everything in one click, on the live site
A white screen, a store that takes no payments, no backup. Every update goes to staging first, to the real site only after testing.
- Moving up the PHP version without a compatibility scan
Functions removed in PHP 8 break custom code and old plugins. I scan and fix before the move, not after a customer sees the first error.
- New design, new URLs, no redirects
Rankings vanish within weeks and the pretty site brings no leads. URLs mapped before, a 301 for every change, Search Console after.
- A speed plugin instead of fixing the cause
A caching plugin hides a slow site until the cache expires. First cut the weight (images, scripts, plugins), then add caching.
- Upgrading a hacked site without cleaning it
The backdoor moves into the upgraded site. Cleaning up and closing the hole are the first step, not the last.
- Forgetting accessibility and privacy
A new form with no privacy notice and too little contrast is legal exposure. Both checks are part of every upgrade.
When not to upgrade: an honest comparison
Part of the service too: sometimes my answer is not to upgrade, at least not now.
| Situation | Upgrade | Not worth it |
|---|---|---|
| The site brings leads, it is just slow and old | Yes: infrastructure and speed, the leads keep coming | A rebuild that puts what works at risk |
| The theme has not been updated since 2022 and the code is undocumented | No: a rebuild on a documented base, with content migration | Upgrading undocumented code: it costs as much as a rebuild and leaves a weak base |
| The site is on Wix and it serves the business | No: keep it, and invest in content | Moving to WordPress only because it is "better" |
| The business changes direction (from brochure to selling online) | No: planning and a rebuild | Patches on a structure not built for it |
| No budget for a full upgrade | Yes: infrastructure only, PHP 8, updates, backups | Waiting until the site breaks |
| The site was hacked for the third time | Yes: clean-up, hardening and upgrade together | Cleaning again and leaving the cause |
If the answer is a rebuild, it becomes a website development project - WordPress development or a freelance web developer build - and the diagnosis goes with it.
How much does a website upgrade cost? Estimated ranges for 2026
Estimates, not a quote: every upgrade starts with a free 30-minute call and ends with a fixed quote, a clear scope and a success metric.
| What is upgraded | What is included | Estimated range |
|---|---|---|
| Full diagnosis and a written report | Infrastructure, speed, security, SEO, plugins, a price per track | $250-420, credited to the upgrade |
| Infrastructure upgrade | PHP 8, WordPress, plugins and theme on staging, backups | $690-1,700 |
| Speed upgrade (Core Web Vitals) | Server caching, images, fonts, scripts, measured before and after | $420-1,700 |
| Security upgrade | Scan, hardening, two-factor authentication, backups | $220-420 (hack recovery $420-970) |
| Design and UX upgrade | A theme refresh or child theme, mobile, forms, no content changes | $1,700-4,200 |
| Move from Wix or a ready-made theme to WordPress | Content migration, URLs kept, 301 redirects, custom design | $2,200-5,600 |
| Full package | All four layers, for a brochure site or a small store | $3,300-8,300 |
| Spot fixes | An error, a plugin conflict, a broken update | from $80, per the repair price list |
| Monthly care after the upgrade | Website maintenance: updates on staging, scans, backups, a monthly report | $100-170/month |
Compare it not with the price of a new site but with the cost of the old one: leads lost to a seven-second load, a working day lost every time it goes down. Per web.dev, a 31% LCP improvement brought Vodafone 8% more sales. In a small business the numbers differ; the direction is the same.
Vadim fixed every problem on my WordPress site in record time. Excellent service, great communication, and a real grasp of the issue from the first moment. Thank you so much for the help - recommended, and definitely the professional you want by your side when something goes wrong with your site.
Website upgrade: frequently asked questions
How long does a website upgrade take?
Infrastructure (PHP 8, WordPress, plugins) takes 3-7 working days, a speed upgrade (Core Web Vitals) one to two weeks, design 3-5 weeks and a platform move 4-8 weeks. The live site keeps working throughout, because the work is done on a copy.
Will the site be down during the upgrade?
No. All changes are made on a staging copy on the same server. Going live takes minutes in a quiet window, with an instant way back if anything comes up.
Will upgrading my website hurt my Google rankings?
A proper upgrade keeps them and usually improves them: every URL is mapped first, every change gets a 301 redirect, and Search Console is checked after launch. What hurts rankings is a new design with new URLs and no redirects.
Do I really have to move to PHP 8?
Yes, and it is more urgent than it seems. PHP 8.1 and older no longer get security updates, and PHP 8.2 reaches its end on December 31, 2026. Moving to PHP 8.3 or 8.4 also makes the site noticeably faster. The move needs a compatibility scan of the plugins and the custom code, so it is done on staging.
How much does it cost to upgrade WordPress?
An infrastructure upgrade usually costs $690-1,700, a speed upgrade $420-1,700, a design upgrade $1,700-4,200 and a full package $3,300-8,300. The exact price is set after a diagnosis, in a fixed quote that does not change halfway through.
Can you upgrade a site someone else built, with no contact with the previous developer?
Yes, that is most projects. I need only access to the hosting and the domain. Undocumented custom code is mapped in the diagnosis, and that is where reading PHP makes the difference between an upgrade and an unnecessary rebuild.
Your site works, but feels old? Let's check what really needs upgrading.
A free 30-minute call, no obligation · reply within 24 hours
Book a free call