Your website feels slow. What should you send me?
Send the page and tell me where you notice the wait. Opening a page, choosing a product, and saving an edit can involve different problems.
Describe what you saw before naming a cause
“The project photograph appears after the rest of the page” is useful. “We need a new server” is a proposed remedy that still needs evidence. Keep both if a provider has already made a recommendation, but separate the observed behavior from the explanation.
Include a public URL where possible and the action that follows it. If the delay occurs only after a menu opens or a filter changes, say so. A general homepage link can send the investigation in the wrong direction.
Record the device, browser and approximate time. You don’t need precise timings from memory. Say whether the issue repeats, whether it affects one person or several, and whether a signed-in state matters. “I have only seen it once” is useful context, not a reason to discard the observation.
Explain why that moment matters
A slow decorative transition and a delay that prevents a customer choosing a product have different consequences. Describe the task's place in the business: an enquiry, a purchase, a search, a document request or an editorial update.
Avoid assigning an unsupported revenue figure to the problem. The immediate goal is to identify its importance and the behavior that must remain intact. If you already have reliable commercial evidence, explain how it was collected rather than treating correlation as proof of cause.
Bring reports with their context
A screenshot can help, but a report link, date and test settings are more useful when available. Identify whether a supplier tested the affected page or a different one. If two reports disagree, bring both; the difference may reveal a variation in conditions or coverage.
Previous work also matters. Mention recent theme, app, media or hosting changes and any optimization tools already enabled. You don’t need to assume the most recent change caused the issue. A simple timeline helps the investigation ask better questions.
Identify the people who can unblock the next step
Know who controls the website platform, code, hosting and relevant apps. A public assessment may not require all those people immediately, but deeper work can depend on their access or approval. If the previous developer is unavailable, say so early.
Don’t send passwords, private logs, customer records or session cookies in an ordinary enquiry. The next step can establish a suitable way to review protected material if it’s necessary.
Agree what to investigate next
A productive conversation should clarify the affected experience, the next evidence to collect and the scope needed to collect it. It may lead to a focused correction, an audit or a provider conversation. It shouldn’t require a confident rebuild estimate before anybody has understood the delay.
Use the short worksheet to collect the essentials. If the project already spans several journeys or teams, the project brief guide helps record the wider decisions. Send your example when you’re ready.
