The playbook
Website Speed Optimization: Template and Field Guide
This website speed optimization template turns a broad task into a record another person can use. It captures template, bottleneck, change, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
Put the task in context
Identify the resource or interaction causing delay before applying broad changes. Large hero images, unnecessary scripts, and slow server responses need different fixes. Retest the full user journey after optimization so reduced load time does not conceal broken functionality.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| template | Record the template associated with this page or interaction record. Use a stable reference so later updates can be matched. |
| bottleneck | Record the bottleneck associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| change | Record the change associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| measurement | Record the measurement associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with template. Use the same reference throughout the record so notes are not attached to the wrong item. Then measure important templates under representative conditions. This establishes the information required before the worksheet becomes a request for action.
Next, identify large assets blocking resources and slow responses. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as optimizing a score while breaking images forms or useful content, rather than a broad instruction to “improve performance.”
Finally, test one bottleneck at a time and verify functions still work. Put pair performance measurements with complete journey tests in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Optimizing a score while breaking images forms or useful content |
| Action | Pair performance measurements with complete journey tests |
| First check | Measure important templates under representative conditions |
| Follow-up check | Test one bottleneck at a time and verify functions still work |
| Outcome to define | load and interaction delays |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If bottleneck changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep load and interaction delays connected to the item so the team can later assess whether the action was useful.
Verify the actual visitor journey on a narrow screen and with a keyboard. A design can look complete while hiding an unreachable control or a missing confirmation. Record the task attempted and what happened at the end.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now