Performance & Technical Debt

I help teams fix slow apps, clean up risky codebases, and remove the technical friction that keeps delivery slower than it should be.

What I help with

Some teams need a new feature. Others need someone to make the existing system feel sane again. This work is for the second group.

LCP, INP, CLS, bundle size, render blocking assets, hydration issues. The work that makes real pages feel fast again.

Untangling risky areas of the codebase in stages. Safer than a big rewrite and easier to explain to the rest of the team.

CI friction, flaky tests, unclear boundaries, repeated manual work. I remove the technical drag that slows teams down every week.

Not a 70-page report no one reads. A ranked list of the issues worth fixing first, with enough detail to act on immediately.

Useful when slow delivery is partly caused by deployment, hosting, or CI/CD issues.

Useful when cleanup work turns into a larger build or modernization project.

No. I can audit first, but I usually stay to implement the fixes so the work actually lands.

Yes. This is often most useful for in-house teams that need extra senior capacity to clear a backlog of hard technical work.

Only if the current system is genuinely costing more to preserve than replace. Most of the time, staged cleanup is the better call.

If performance is sliding or technical debt is slowing the team down, I can help you work out where to start and what to fix first.