# Event page unused JavaScript investigation and release record

Event/site: __________  Technical owner: __________  Date: __________

## Baseline conditions
URL and locale: __________  Device and network profile: __________
Run / observation time: __________  Lighthouse opportunity or resource URL: __________

| State recorded with Coverage | Interaction performed | Resource and unused/used observation | Visitor task passed? |
|---|---|---|---|
| First event view | | | |
| Ticket tier selection | | | |
| Registration and validation | | | |
| Menu/language/modal | | | |

## Decision
Resource/bundle: __________  Importing route/component: __________
Purpose and owner: __________
Evidence it is dead, route-specific or only needed later: __________
Action (remove / split / defer / keep): __________
Expected change and loading-state design: __________
Rollback commit/owner: __________

## After change
Same URL, device, network and states repeated: __________
Bytes/execution observation before and after: __________
Event details, ticket price, selection, form and confirmation still work: __________
Regression and decision to keep/revert: __________

Coverage only describes the states observed. A low first-load usage percentage does not prove a feature can be removed.