# Performance investigation worksheet

Blitz Studio · Updated 2026-11-17

Source: https://blitzstudio.xyz/resources/performance-investigation-worksheet

# Performance investigation worksheet

Copy the fields below into a ticket for one page and one symptom. Attach the original trace so someone else can inspect the same evidence.

- **Page and build** —
- **Visitor action and visible symptom** —
- **Browser, viewport, network and cache settings** —
- **Baseline trace or recording** —
- **Observed event and position in the trace** —
- **Possible explanation** —
- **One change to test** —
- **Expected effect on a specific event or metric** —
- **Repeat trace and comparable measurement** —
- **Functional checks and decision** —
- **Owner and follow-up date** —

## Worked example

A fictional ceramics shop sees its hero appear late on a cold mobile load. In the example trace, the image response finishes before the hero is painted. The team would first inspect what happens between the response and paint, including whether application code delays revealing the hero.

The proposed test is to remove the reveal delay in a preview build. Record another trace under the same viewport, network and cache conditions and compare the interval between image completion and paint. Also check that the image still appears correctly when navigating back.

**Status** Pending. This example supplies no measured timing or field result.
