Logs before guesses

Find what broke. Wire the site back up right.

When your site errors, slows down, or stops sending leads, we reproduce the problem, read server logs, and fix the real cause. Some issues need your hosting company or a plugin vendor; we say so early and leave a written summary your team can follow.

Report a site problem Ongoing WordPress care
Start the quick brief

Priority reply

What broke on your site?

1 / 4

Logs before guesses — tell us what you are seeing.

What is the main issue?
How urgent is this?
You
Anything else we should know?

When your site shows a white screen, loops on redirects, stops sending form leads, or crawls on phones, you need someone who finds the real cause instead of guessing. We troubleshoot WordPress and common PHP hosting setups with logs, a safe copy to test in, and a written summary when we are done. Some problems need your hosting company or a plugin vendor; we say that early and stay on the thread until the site is wired back up correctly.

What we handle on repair calls

One calm process: reproduce what broke, read server and application logs, narrow plugin or theme conflicts, fix or roll back safely, then verify forms, phones, and public pages before we call it done.

What we do not do

We do not promise same-day fixes on every setup, guaranteed uptime, or a magic button after years of neglected updates. We do not hide behind jargon or bill for guesses. When the honest answer is a rebuild, host migration, or vendor ticket, we say so in writing.

We can help with

Evidence first, then a fix you can explain to your team.

  • Site down or error pages: white screens, 500 errors, PHP version mismatches after a host upgrade.
  • Forms and lead routing: submissions that never arrive, spam floods, or notifications going to a former employee.
  • Redirects and HTTPS: loops, mixed content warnings, certificates pointed at the wrong server, www vs non-www fights.
  • Performance and admin pain: slow saves, locked database tables, bloated plugins slowing the dashboard.
  • After a bad update: plugin or theme conflicts, broken layouts, missing images until caches clear.
  • Handoff notes: what broke, what we changed, and optional maintenance so it does not repeat.

We will not

Stated plainly, including in writing when asked.

  • Guarantee a timeline before we see logs, access, and whether a safe test copy exists.
  • Band-aid forever: temporary holds are labeled; permanent fixes get a proper release window when possible.
  • Blame without proof: we show what the logs and tests pointed to, even when the answer is a vendor bug.
  • Leave you locked out: you keep hosting, domain, and admin access unless you ask us to hold keys for care.
  • Vanish after the fire: we document changes and can connect follow-up care or a rebuild plan when repair is not enough.

Symptoms we investigate first

Most owners call when something public broke: the homepage, a form, or checkout. These are the patterns we look for before we change production. Open any card below for a plain-English read on cause, fix, and what to expect.

Common situations we repair

Every site history is different. These are repair calls we see often on WordPress and shared hosting. Timelines depend on access, backups, and whether your host can help on their side.

White screen or site completely down

The public site errors after an update, a host PHP change, or a plugin auto-update overnight.

The problem: Customers see a blank page or a generic error. Your office may still reach wp-admin, or nothing loads at all. Someone updated plugins on production without a backup.

What we do: We read error logs, enable safe debugging if needed, and test on a staging copy when your hosting allows it. We narrow plugin vs theme conflicts, patch or roll back, and bring the public site back before we chase nice-to-haves.

What to expect: A working homepage and critical forms first. Deeper cleanup may continue under maintenance if the site was neglected.

Forms look fine but leads never arrive

Thank-you pages show success while dispatch hears crickets.

The problem: SMTP credentials expired, a plugin update changed the recipient, spam filters swallowed notifications, or a CDN cached an old form handler.

What we do: We send test submissions, trace delivery paths, fix routing to the inbox your office actually monitors, and add basic spam controls without blocking real customers.

What to expect: Verified test leads and written notes on what was miswired. We do not guarantee lead volume; we fix the pipe.

Redirect loops and HTTPS warnings

Browsers complain about security or bounce between http, https, and www.

The problem: DNS still points at an old host, SSL renewed on the wrong server, or multilingual and HTTPS rules fight each other.

What we do: We map where the domain resolves, which certificate is served, and which redirect rules run in WordPress vs the server. We align one canonical URL your team can share with customers.

What to expect: Propagation can take hours after DNS changes. We tell you what to watch and when to re-test.

Slow site or admin that will not save

Pages load forever on phones; updating copy times out in the dashboard.

The problem: Oversized images, too many plugins, database bloat, or a host plan that cannot handle traffic spikes during storm season.

What we do: We measure what actually slows real mobile loads, trim obvious waste, fix database locks where safe, and tell you honestly if the host tier is the bottleneck.

What to expect: Faster critical pages when the cause is fixable in software. Some wins need hosting changes, not another plugin.

Hacked, defaced, or suspicious admin users

Strange redirects, pharma spam pages, or logins you did not create.

The problem: Outdated plugins, weak passwords, or a former vendor left wide-open access. Google may warn visitors before your office notices.

What we do: We contain the damage, remove known malicious code where we can verify it, reset credentials, patch entry points, and document what was found. We do not sell “unhackable”; we remove lazy weak spots.

What to expect: Clean public pages and sane admin access first. Severe cases may need a clean rebuild from backups.

How a repair call usually runs

Order shifts when the site is fully down. The spine stays the same: understand what changed, prove the cause, fix without making new surprises, and leave a summary your next vendor can follow.

  1. Triage: failing URLs, last known good time, recent publishes, DNS or SSL changes, and access your team can share today.
  2. Reproduce: read server and application logs; note whether only logged-in users see the failure.
  3. Isolate: safe staging copy when available; disable suspects one at a time instead of guessing in production.
  4. Fix or contain: patch, rollback, or a labeled temporary hold until a proper maintenance window.
  5. Verify and document: test forms, phones, and key pages on mobile; write what broke, what we changed, and what still needs your host or a vendor.

After the site is back up

One repair call can stop the bleeding. Recurring issues usually mean nobody owns updates, backups, or plugin testing. We can connect ongoing WordPress maintenance, hosting review, or a planned rebuild when patch-on-patch is no longer sane.

  • Written summary: timeline, root cause when known, files or plugins touched, and open items for your host.
  • Lead path check: forms and call links tested the way a customer would use them on a phone.
  • Honest next step: maintenance, hosting upgrade, or rebuild scoped separately, not buried in the repair invoice.

Contact Archi FX with failing URLs, the last time the site looked healthy, and access your team can share. For non-urgent work, say whether ads or booking tools depend on the site this week.

Ready to talk through your project?

We read every inquiry personally. Tell us what you need and we will respond with a clear recommendation.

Start a conversation View all services