Faith Forge LabsWebsite Speed Optimization

Describe one slow moment

Copy these prompts into your project notes or enquiry. Plain observations are enough; leave the cause open until it has been investigated. If several problems appear unrelated, record a separate example for each.

1. Where were you?

Write the exact public URL. Note whether you were signed in, but omit account details. If the concern is inside an application, describe the screen and task without sharing private records.

2. What did you try to do?

Describe the action and starting state. Examples include opening a portfolio page, choosing a product option, filtering results or submitting an enquiry. “The site is slow” becomes much more useful when it names the moment.

3. What happened while you waited?

Say whether the main content arrived late, a control hesitated, information took time to update or the layout moved. Include the device, browser and approximate time if known. Note whether you can repeat it and whether it happens on a fresh visit, a return visit or both.

4. What result should stay correct?

List the behavior the change must preserve. This could be the selected product and price, account privacy, image detail, a form's delivery or an editor's ability to publish a correction. Performance work should support that purpose.

5. What changed recently?

Record new media, apps, theme changes, hosting changes or releases. “Nothing known” is a useful answer. A change timeline provides context without establishing that the latest item caused the delay.

6. What evidence is available?

Include public report links and their dates or settings if available. Identify who controls the platform and relevant provider accounts. Don’t paste credentials, private logs, session tokens or customer information into the worksheet or an ordinary message.

A fictional example

“On the sample lighting store's product page, selecting a different fitting pauses before the availability text updates. I noticed it on my phone, and it happened after several option changes. The opening page seemed normal. A configuration app was updated last week, but we don’t know whether that’s related. The fitting, price and cart item must remain consistent.”

These observations identify what to reproduce and which outcomes to protect while leaving the cause open.

Turn the note into a next step

For an initial discussion, the URL and observation may be sufficient. A wider engagement can add representative page families, access, acceptance and release responsibilities through the project brief guide.

Send a performance inquiry or read the performance notebook.