# Regional event website latency comparison worksheet

Use one row per URL, region and observation window. Compare like with like. Do not store attendee identities or IP addresses here.

| Event edition / URL | Journey step: page, registration, checkout | Audience region / test location | Timestamp and time zone | Device / browser / connection | Cold or warm cache | Field sample or controlled probe | DNS | Connect/TLS | TTFB | Download / page rendering | Edge/cache signal if available | Third-party dependency | Observation / hypothesis | Owner / next change / retest |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Example / official event page | Public event facts | Main audience / nearby probe | Date + zone | Mobile / browser / network | Cold | Controlled | Record | Record | Record | Record | Check | Ticket embed | Establish baseline | Assigned owner / date |
| | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | |

## Decision record

- Affected regions and real audience relevance:
- Same URL, device class, connection and cache state in each comparison?
- Field data sample and limits; lab probe limitations:
- Slow stage supported by the request waterfall or provider logs:
- Public cacheable asset, dynamic registration or external checkout?
- Hypothesis and alternative explanations:
- Smallest reversible change, owner and expected signal:
- Before/after retest window and result for affected and baseline regions:
- Attendee path still works after change?

A ping or a single TTFB reading cannot establish full page experience or identify the responsible provider.