Website fixes & rescue
The site is slow, something broke, or the developer stopped replying. I'll tell you what's actually wrong before anyone talks about rebuilding.
Most rescue work starts the same way: something used to work, someone left, and now nobody wants to touch it. The first step is an assessment — what's there, what's dangerous, what can be saved. Sometimes the answer is a few days of fixes rather than a rebuild, and you should hear that even though a rebuild would pay me more.
What's included
An honest assessment first
I read the code and the infrastructure and tell you what's wrong, what it takes to fix, and whether rebuilding is genuinely the better option.
Speed and Core Web Vitals
Find what's actually slow — images, blocking scripts, server response — and fix the causes rather than chasing a score.
Broken and abandoned projects
Finish what someone else left half-built, or stabilise a codebase whose author is unreachable.
SEO and indexing problems
Pages missing from Google, broken redirects and canonicals, a sitemap nobody maintained — the technical reasons traffic disappeared.
Security and dependency updates
Outdated packages with known vulnerabilities, exposed configuration, missing security headers — brought up to date deliberately.
A safe path forward
Tests and logging around the fragile parts, so the next change doesn't reintroduce the same failure.
How we'd work
- 01
Scope, in writing
We agree exactly what gets built and what it costs before any code — no creeping invoice, no surprises.
- 02
Ship in slices
Working software every week, not a big-bang reveal at the end. You see progress and can change course early.
- 03
Pay after launch
You pay once the project is live and you're happy with it. No upfront deposit.
Related work
Questions clients ask
Can you fix a site you didn't build?
Yes — that's most of this work. I read what's there first; the assessment is how we both find out whether fixing or rebuilding makes more sense.
What if the previous developer disappeared?
Common, and workable as long as you control the domain, hosting and repository. If access is missing, recovering it is the first thing we sort out.
How fast can something urgent be fixed?
A site that's down or badly broken gets looked at first. Small fixes often land the same day; how fast depends on what the assessment finds.
Will you tell me if it's not worth fixing?
Yes. If patching costs more than replacing, I'll say so and explain why — including when that means less work for me.
Do you take over ongoing maintenance?
Yes, if you want it — updates, monitoring and changes on an ongoing basis. No lock-in, and no contract you have to escape from.
Have a project in mind?
Tell me what you're building and where it's stuck. I usually reply within a few hours.