Website technical rescue
Send me the website and describe what is happening. I work across the boundaries between the page, code, host, domain, DNS, email, database, authentication, and deployment.
01 / Symptoms
| What you see | What may be involved | What I can do |
|---|---|---|
| The site loads slowly. | Images, scripts, fonts, rendering, caching, application work, or data queries. | Measure the delay, isolate the cost, repair what is responsible, and retest. |
| Forms submit but no email arrives. | Form code, provider API, DNS records, SPF, DKIM, routing, or notification handling. | Follow the submission from browser to storage and delivery instead of guessing at one provider. |
| The domain or email broke after a change. | Registrar, nameservers, DNS records, proxy state, mail routing, certificates, or origin configuration. | Reconstruct the record path, correct the conflict, and verify web and mail behavior separately. |
| Hosting costs too much or feels impossible to leave. | Legacy plans, unnecessary resources, bundled services, undocumented dependencies, or migration risk. | Inventory what the site actually needs, identify a viable target, and scope a protected migration. |
| A login stopped working. | Account ownership, password recovery, application auth, environment variables, callbacks, or database state. | Diagnose the part you control and assist with documented recovery paths. I do not promise access where ownership cannot be proven. |
| The database or dynamic feature is failing. | Schema, query behavior, credentials, migrations, runtime limits, or application logic. | Inspect the data path, reproduce the failure, and repair or clearly bound the next action. |
| The layout is broken on phones or after an update. | CSS, image dimensions, content overflow, component changes, or browser behavior. | Repair the actual layout failure without turning a contained problem into an unwanted redesign. |
| The developer is gone and nobody knows how it works. | Accounts, repository, hosting, deployment, domains, third-party services, and undocumented code. | Create a system inventory, stabilize what can be controlled, and produce a practical ownership map. |
02 / Who uses this
Direct client work
You know what is hurting the business or organization, but you should not need to determine whether DNS, code, hosting, or email owns it before asking for help.
Technical overflow
Use me for the infrastructure, migration, deployment, database, or cross-provider issue that is blocking your actual project.
03 / How work is priced
If the failure and boundary are clear, I quote a fixed price before production work.
If access, logs, or deeper investigation are required, I quote a paid diagnosis. The result is evidence, the most likely root cause, repair options, risk, and a separate repair price.
I inventory the current system, define what must survive, establish rollback, and provide a written scope.
Work can be hourly or fixed-scope depending on how well the failure is bounded. Your client relationship stays yours.
I do not publish a fake flat price for problems that can range from one DNS record to two days of account recovery and infrastructure tracing.
04 / Production process
You send the URL and symptom. I inspect what is externally visible and tell you whether the problem fits my work.
I identify the minimum accounts, repository, logs, or records needed. You retain ownership of your accounts and domain.
I state what I am changing, what I am not changing, how rollback works, and the price. I confirm the price before I touch production.
I reproduce the issue, make the narrowest responsible change, and keep adjacent working behavior in scope.
I test the behavior that failed, relevant nearby behavior, mobile layout when applicable, and production routing after deployment.
You receive a plain record of the cause, the change, the services involved, and the credentials or configuration that must remain under your control.
05 / Evidence
For Highlands Nordic Sno-Park, I replaced obsolete infrastructure with a Git-managed static system on Cloudflare, added D1-backed workflows, Resend notifications, preserved PayPal payments, created a high-resolution interactive trail map, and reduced annual website operating cost by about $225 per year.
06 / Send the problem