# Event website font-loading decision worksheet

Event/site: __________  Owner: __________  Date: __________

| Text role and route | Font family/file/weight | Locales and glyph coverage | Fallback | font-display choice and reason | Initial-view priority | License/update owner |
|---|---|---|---|---|---|---|
| Brand event name | | | | | | |
| Date, venue and price | | | | | | |
| Ticket CTA and controls | | | | | | |
| Registration and messages | | | | | | |

## Discovery and delivery
- [ ] Network observation shows when critical CSS and font files are requested.
- [ ] Unused weights and styles are excluded from this route.
- [ ] External font connection and self-hosting were compared under the same conditions.
- [ ] Any preload is justified by first-view use and does not delay poster or key content.
- [ ] Subsets cover all six locales; licensing allows any alteration and hosting.

## Rendering and attendee checks
- [ ] Date, venue, price and CTA remain readable while fonts load.
- [ ] Fallback and web font do not move the ticket action unexpectedly.
- [ ] Long German/French text and Japanese glyphs render correctly.
- [ ] First visit, slower phone connection and repeat visit were compared.
- [ ] Registration and ticket handoff remain usable.

Decision, evidence and next review: __________