Web Development
Event sites that hold traffic when a fight week actually hits
Matchroom needed digital experiences that look like the brand and survive a traffic spike. We rebuilt event pages, schedules, and media modules for performance and editorial speed.
The operational problem
Campaign pages were beautiful in staging and fragile on sale day. Editors waited on developers for copy that should have been a field.
A slow fight-week page is not a Lighthouse score. It is tickets and sponsors watching a spinner.
What was breaking down
- Hero video blocking first paint
- Editorial changes stuck in a ticket queue
- Schedule modules that did not cache
How Striders Tech approached it
We treated performance as part of the design: static shells, cached schedules, and an editor layout that does not require a deploy.
What we built
- Event templates with locked performance budgets
- Editor-controlled fight cards and media
- Edge caching for schedule fragments
- Media that does not steal LCP from the poster
Results the team can measure
- Fight week pages held under load that used to queue
- Editors ship copy without an engineering ticket
- Sponsor units render without shifting the card
Who this case study is for
Sports and entertainment brands whose biggest nights are also their most expensive traffic events.
Matchroom operates in sports / media. The work is a custom system designed around their process, not a generic template with extra fields bolted on.
What changed after the system went live
pages held under load that used to queue
ship copy without an engineering ticket
render without shifting the card