Website Support for Artists & Charities: A Simple “What’s Broken?” Triage Guide

If your website suddenly feels unreliable, you do not need to solve everything at once. Start by sorting the problem into the right bucket. A broken form, a slow page, and a strange mobile layout all need different next steps — and the right first check can save a lot of time.

Checklist for website triage: forms, images, mobile, speed.
A simple triage checklist helps you spot the most urgent website issues before they spread.

When Something Goes Wrong: 5 Checks You Can Do in 10 Minutes

Before you call for help, do a calm 10-minute pass. You are not looking for perfection. You are looking for clues.

  • Check the homepage. Does the homepage load, or do you see an error, a blank screen, or a layout that looks broken?
  • Test one form. Try a contact or enquiry form and note whether it submits cleanly.
  • Look at images. Are photos missing, stretched, cropped oddly, or taking far too long to appear?
  • Open the site on mobile. Check the same page on a phone or narrow browser window.
  • Give it a quick speed check. If a page is unusually slow, note which page and what feels slow: loading, scrolling, or clicking.

If you want a neutral external benchmark for mobile usability or performance, the guidance from web.dev on responsive design basics and PageSpeed Insights can help you describe what you are seeing without guessing at the cause.

Triage Decision Tree: What Kind of Problem Is It?

Use the simplest category that fits. That keeps the next step focused.

  • A. Broken links or forms — a button goes nowhere, a link throws an error, or a form does not send.
  • B. Display or layout issues — text overlaps, menus hide, images break the layout, or spacing looks wrong.
  • C. Performance or slow pages — pages load, but they take too long and people may give up.
  • D. Security or odd behavior — pop-ups you did not expect, unknown text, login trouble, or content changing on its own.
  • E. Content updates — the site works, but text, hours, staff details, images, or announcements need a tidy update.

If the issue affects trust, access, or submissions, treat it as urgent. If it is cosmetic but visible, it can usually be scheduled. If it is just content, it may be a quick update rather than a repair.

Forms and Contact Problems: Confirm the Real Break Point

Forms can fail in more than one place. The visible page may look fine while messages get lost after submission. Start by checking three things:

  • Does the form submit on the page? If not, the problem is likely on the front end or within the form setup.
  • Do messages reach the right inbox? If submission works but no one receives mail, the issue may be routing, filtering, or a mailbox problem.
  • Are replies landing in spam? Ask the recipient to check spam, junk, promotions, and any message rules before assuming the form is broken.

For a broader look at form behavior and message flow, the official help from Google Workspace spam and delivery guidance and the practical notes in MDN’s forms guide are useful reference points. You do not need to become a developer; you only need enough detail to describe what is happening.

Image and Gallery Issues: Broken, Cropped, or Just Slow?

Image problems usually fall into one of three groups:

  • Broken media — the image does not appear at all, or you see a missing-file symbol.
  • Wrong sizing — the image loads, but it is stretched, too small, or cut off.
  • Slow-loading photos — the image eventually appears, but the page feels heavy or jerky while it does.

When you report it, note whether the problem appears on one page or everywhere. That small detail helps separate a single bad file from a wider layout issue.

Checklist for website triage: forms, images, mobile, speed.
Document what you see. A screenshot is often more helpful than a long explanation.

Mobile Display Problems: What to Capture Before You Reach Out

Mobile issues can hide on desktop. A menu may wrap badly, a button may be too close to another element, or a section may push sideways off the screen. If that happens, capture:

  • the device model if you know it,
  • the browser name,
  • the page URL,
  • a screenshot,
  • and what you expected to see instead.

If you want a simple, widely used reference for accessible mobile-friendly layout behavior, WCAG’s reflow guidance is a good benchmark to mention in a support note.

SEO-Impact Triage: Fix the Things That Can Hurt Visibility Fast

Some issues are not just annoying — they can make pages harder to find. Check these first:

  • Does the page still have a sensible title?
  • Is the page being indexed normally?
  • Was a key page accidentally hidden from search?
  • Did an important page disappear or move?

If you use search tools, Google’s SEO Starter Guide is a steady reference for the basics. It will not fix a broken site for you, but it will help you spot which problems deserve immediate attention.

What to Collect Before You Contact Support

Good support starts with good context. Before you send a message, gather:

  • the exact URL,
  • screenshots,
  • the time you saw the issue,
  • your browser and device,
  • what you expected to happen,
  • and what actually happened.

A short note written like this works well: “On the contact page, the form submitted but no confirmation appeared. I tested it on an iPhone in Safari at 10:15 a.m.” That is far more useful than “the site is broken.”

A Simple Next Actions Plan

TimeframeWhat to do
TodayCheck the homepage, one form, one image-heavy page, and one mobile view. Save screenshots.
This weekSend a tidy support request with the URL, device details, and expected vs. actual outcome.
MonthlyReview key pages, test forms, replace outdated content, and check for new broken links or slow pages.

If a task is small, you can often handle it yourself. If it affects design, performance, or form delivery, it is usually better to ask for help rather than make a guess and hope the site forgives you. Sites are rarely that generous.

FAQs

How do I know if it is urgent?

If visitors cannot contact you, donate, book, buy, or find a key page, treat it as urgent. If it only affects appearance, it may be important but not emergency-level.

Can I keep the site live while we fix it?

Usually, yes. Many fixes can happen while the site stays online. The safest approach is to document the problem first so changes are targeted and temporary workarounds do not create new confusion.

What should never be changed without advice?

Avoid changing anything you do not fully understand on a live site, especially anything related to forms, search visibility, navigation, or theme settings. If in doubt, capture the problem and ask for help before making a risky guess.

If you are unsure where your issue fits, start with support, or visit contact with your screenshots and notes. If you want more practical website guidance, browse the blog or see the available services that can help.

Scroll to Top