Race-weekend traffic spikes, served from cache. Editors ship live.
NASCAR Studios produces race-weekend content across web and OTT. Traffic spikes 40× on race day. Their previous site went down twice in a season under load. Editors needed to publish lap-by-lap updates without a developer present.
NASCAR Studios produces content for race weekends: driver profiles, race previews, lap-by-lap updates, and post-race analysis. Traffic spikes 40× on race day.
The performance constraint The site had to serve race-day traffic from cache, period. No origin requests on race day. This shaped every architecture decision: content had to be fully pre-rendered and the CMS had to publish without triggering a full rebuild.
Storyblok + Astro on Cloudflare Pages We chose Astro for its island architecture. Storyblok's webhook-driven ISR let editors publish a story update and see it live in under 10 seconds without touching the build pipeline. Cloudflare Pages serves the site from 300+ edge locations.
Lighthouse 97 → 100 Three things pulled it to 100: replacing a third-party font loader with static loading, lazy-loading below-the-fold images with proper dimensions, and moving the analytics snippet to requestIdleCallback.
Editorial workflow Editors use Storyblok's visual editor to compose race previews, schedule them, and publish lap-by-lap updates from pit lane on a tablet. No developer is present on race day.