Skip to main content

Website Troubleshooting

Something on your website is broken and nobody knows why

We investigate methodically using logs, recent change history and controlled testing to find the actual cause of website faults, fix it safely and explain what happened.

Updates appliedOnline · 200 OK

Business impact

Small faults often have quiet but real costs

Not every problem takes a website offline. Many faults keep the site running while silently losing enquiries, orders or data.

Silent lead loss

Contact forms that appear to submit but never deliver email can go unnoticed for weeks while enquiries disappear.

Revenue leaks

Coupon errors, shipping calculation bugs or a payment step failing on one browser reduce sales without triggering an outage.

Recurring disruption

Intermittent issues that are patched rather than diagnosed come back, often at the worst possible moment.

Common issues

Problems we regularly solve

White screens and 500 errors

PHP fatal errors after an update, memory limits exhausted or a corrupted .htaccess file leaving the site blank or showing a generic error.

Forms not delivering

Emails sent from the web server rejected or marked as spam because SPF, DKIM or SMTP configuration is missing or wrong.

Plugin and theme conflicts

Two components loading incompatible libraries or hooking the same feature, causing broken layouts or JavaScript errors.

Failed or partial updates

Updates interrupted mid-way, leaving the site in maintenance mode or with mismatched core and plugin versions.

Intermittent slowness and timeouts

Problems that only appear at certain times, linked to scheduled tasks, backups, bots or resource limits on the hosting.

Redirect loops and mixed content

Misconfigured HTTPS, CDN or proxy settings causing endless redirects or insecure content warnings in the browser.

What's covered

What's included in website troubleshooting

Troubleshooting covers diagnosis and repair on the platforms we support. Where the fault lies with a third-party service, we gather the evidence and work with the vendor on your behalf.

Error and log analysis

Reviewing PHP error logs, web server logs, application logs and browser console output to pinpoint where failures occur.

Change history review

Correlating the start of a problem with recent updates, deployments, configuration changes or hosting events.

Conflict isolation

Reproducing the fault on a staging copy and disabling components in a controlled way to identify the cause without disrupting the live site.

Email delivery problems

Diagnosing website email delivery, configuring authenticated SMTP and checking SPF, DKIM and DMARC records.

Hosting and DNS faults

Identifying resource limits, DNS misconfiguration, expired certificates and proxy issues that affect the site.

Fix and prevention

Implementing the fix, testing affected journeys and recommending changes to stop the issue returning.

Maintenance activities

What we do, and how often

Exact frequencies depend on your plan and platform. This is a typical schedule.

On demand

  • Fault reproduction and impact assessment
  • Log, error and change history analysis
  • Staging-based conflict testing
  • Fix implementation and regression checks
  • Root cause summary on the ticket

On onboarding

  • Access to hosting, CMS and logs
  • Staging environment set up where the platform allows

Monthly

  • Review of recurring faults in the monthly report
  • Preventive recommendations for repeat issues

Our methodology

How we work

  1. 1

    Define the symptom

    We confirm exactly what is happening, for whom, on which devices and since when, because precise symptoms narrow the search quickly.

  2. 2

    Gather evidence

    Logs, error messages, recent changes and monitoring data are collected before anything is altered.

  3. 3

    Isolate the cause

    We form a hypothesis and test it, ideally on staging, eliminating possibilities until the cause is confirmed.

  4. 4

    Fix and verify

    The fix is applied with a backup in place and the affected journey is tested end to end, along with related features.

  5. 5

    Explain and prevent

    You receive a plain-language explanation of what went wrong and what, if anything, should change to prevent it happening again.

Business benefits

What you gain

Root causes, not workarounds

Diagnosing the underlying problem helps reduce repeat incidents and the cost of fixing the same thing twice.

Minimal disruption

Testing on staging means fewer experiments on the live site while visitors are using it.

Plain-language explanations

You understand what failed and why, which helps when deciding on follow-up work.

One team across layers

Because we work across code, hosting, DNS and email, issues are not passed between suppliers.

Technologies supported

  • PHP error logs
  • Nginx and Apache logs
  • Browser developer tools
  • Query Monitor
  • WP-CLI
  • Git
  • SMTP and email authentication (SPF, DKIM, DMARC)
  • Cloudflare
  • cPanel and Plesk
  • Staging environments

Running something not listed? Ask us – we'll tell you honestly if it's a fit.

Who it's for

Who needs website troubleshooting?

Businesses with an unexplained fault

Owners and managers facing an error that their hosting company says is a website problem and their developer says is a hosting problem.

Teams after a failed update

Organisations whose site broke after an update and need it working again safely.

Agencies with legacy client sites

Agencies inheriting sites they did not build and need diagnosed quickly.

Industry guidance: Professional Services · E-commerce · Digital Agencies

FAQs

Website Troubleshooting: common questions

Can you fix a website problem as a one-off job?
Yes, troubleshooting can be arranged as a one-off engagement. Many clients then move to a maintenance plan so the same issues are prevented in future.
What information should we send when reporting a problem?
The page or feature affected, what you expected to happen, what actually happened, any error message or screenshot, the browser and device used and roughly when it started. This speeds up diagnosis considerably.
Our form says the message was sent but we never receive it. Why?
This is usually an email delivery issue rather than a form fault. Messages sent directly from the web server are often rejected or filtered as spam unless authenticated SMTP and correct SPF and DKIM records are in place.
Will you need to take the site offline to troubleshoot?
Rarely. We reproduce and test on a staging copy wherever possible, and only make changes on the live site once we know what the fix is.
What if the problem is caused by a third-party plugin or service?
We document the evidence, apply a safe workaround if one exists and report the issue to the vendor. If the component is unreliable, we recommend alternatives.

Get a persistent website problem diagnosed

Contact us with the details of the fault and an engineer will review it and recommend next steps.