My website was fine last month. What changed?

A website depends on more than the files you last edited. Third-party tools, platform updates, content changes and expiring accounts can alter the experience over time.

Build a useful change timeline

Start with when the symptom first appeared and what changed around that time. A new widget, revised image, theme update or expired licence may be relevant. Correlation is a clue, not proof, so test the likely cause before reverting unrelated work.

Monitor what you can act on

A monthly health check can highlight changed measurements, while scheduled uptime requests can reveal repeated availability failures. Neither replaces testing the customer’s main task. A useful alert tells you what changed and what to inspect next, rather than creating a stream of unexplained red numbers.

A practical checklist

• Record significant changes.
• Keep a baseline for important pages.
• Check expiry and renewal dates.
• Investigate repeatable changes before reacting.

What to do next

Start with one important page and one clearly defined problem. Keep a record of the original behaviour, make a controlled change and check the result. If you are not comfortable changing the site, the record gives a developer a useful starting point and makes the scope easier to agree.

A CHD website check can add public-page evidence to that conversation. The free result includes a score and up to three findings. The full $29 teardown includes the measured findings, practical guides, a private report and a PDF. Any repair work is reviewed and quoted before payment.