White screen of death
A blank page with no error message, because error display is off and nobody knows where the logs are.
[ WordPress / WordPress Bug Fixing ]
Broken WordPress, diagnosed properly.
A white screen, a checkout that fails silently, or an update that took the site down. I find the actual cause rather than disabling plugins until the symptom disappears and the problem returns next month.
Same-day response · Fixed price per issue · No fix, no fee
Same dayresponse
Fixedprice per issue
No fixno fee
Root causenot a workaround
[ What I fix ]
The failures that bring people here.
All of these are solvable. Most take hours rather than days once the cause is actually identified.
Fatal errors after an update
A plugin or theme incompatible with a new PHP or WordPress version, taking the whole site with it.
Checkout or forms failing
Orders not completing, payment callbacks not landing, or form submissions vanishing without a trace.
Plugin conflicts
Two plugins fighting over the same hook, so one feature only breaks when the other is active.
Sudden slowdowns
A site that was fine last week now taking eight seconds, usually a query or a cron job nobody is watching.
Broken after a migration
Mixed content warnings, wrong URLs in the database, or images pointing at the old host.
[ How it works ]
Reproduce, diagnose, fix.
01 — Same day
Triage
You describe the symptom, I check the site and logs and come back with what is wrong, what it will cost to fix, and how long it will take.
02 — Fix
Repair
Fixed on a staging copy wherever possible, verified, then applied to production. Anything risky happens in a window you agree.
03 — After
Explain
You get a short written note: what broke, why, what I changed, and what would stop it recurring. No mystery invoices.
[ What actually changes ]
How the diagnosis works.
Deactivating everything and reactivating one at a time is a last resort, not a method. It also means taking your live site down repeatedly.
Finding the cause
- Server and PHP error logs — read first, because the answer is usually already written there.
- Staging reproduction — the fault reproduced on a copy so debugging does not disturb live traffic.
- Query and performance profiling — for slowdowns, finding the specific slow query or blocking request.
- Conflict isolation — done on the staging copy, systematically, not by guessing on production.
- Recent change review — updates, deploys and content changes correlated against when it broke.
Fixing it properly
- Root cause fix — the underlying problem, not a snippet that suppresses the error message.
- Update-safe changes — in a child theme or small plugin so the next update does not undo the work.
- Regression check — the rest of the site verified, because fixes cause their own bugs.
- Version control — changes committed where you have a repository, so there is a record.
- Prevention note — what would stop this class of problem happening again.
[ Example engagement ]
Intermittent checkout failure, traced in an afternoon.
A store losing roughly one order in nine with no error shown to the customer. A payment callback was timing out under a specific plugin combination, invisible in every plugin-by-plugin test.
Illustrative example of a typical engagement. Figures vary with the state of your systems and are not a guarantee of a specific outcome.
4 hrsto root cause
11%of orders were failing
0code rewritten
1line actually changed
[ Same-day · no fix, no fee ]
Describe the symptom.
Send what is happening and when it started. You get a diagnosis and a fixed price the same working day, and you pay nothing if I cannot fix it.
[ Pricing ]
Pricing that fits your budget.
Tell me the number you have to work with. I'll tell you honestly what's achievable within it — and if it isn't enough, I'll say so before we start rather than halfway through.
Fixed project price
Scope agreed in writing, price agreed in writing, before any work starts. No hourly creep and no invoice you haven't already approved.
Monthly retainer
For ongoing work — maintenance, monitoring, updates and small changes. Month to month, cancel whenever, no minimum term.
Hourly for small jobs
For a single bug or a short task where writing a full scope would cost more than simply doing the work.
Budget too tight for the whole thing? I'll often suggest doing the highest-value part first and the rest later, rather than doing all of it badly.
[ Questions ]
Common questions.
How quickly can you look at it?
Same working day for most issues. If the site is completely down or unable to take orders, say so in the first message and it goes to the front of the queue.
What does it cost?
Quoted per issue after triage, so you know the number before I start. Most single problems are a few hours' work. If I cannot fix it, you do not pay.
What access do you need?
WordPress admin and, ideally, hosting or FTP access with the error logs. Diagnosis is much slower without logs, and slower means more expensive for you.
Can you fix a site another developer built?
Yes, that is most of this work. I will not criticize their code to you unless it is directly relevant to why the thing broke.
Will you break something else?
Fixes are made on a staging copy and regression-checked before going live wherever the hosting allows. Where there is no staging, I take a full backup first and agree a window with you.
[ Related services ]
Related WordPress work.
WordPress Speed OptimizationFix Core Web Vitals and slow load times at the cause.WordPress Malware RemovalHacked site cleaned, hardened and delisted, usually within 24 hours.WordPress DevelopmentCustom themes, plugins and integrations built to be maintained.WordPress SecurityHarden a clean site so it stays that way.WordPress MigrationMove hosts or domains without downtime or losing rankings.Laravel DevelopmentAPIs, dashboards and long-term maintenance of Laravel apps.
[ Let's talk ]
Tell me what's broken.
Describe the problem in a few lines and you'll get a real reply from the person who'd do the work — same working day, no discovery call required.