The Performance Aspect of Building and Deploying Static Sites
summary
Claim: a static site can provide dynamic realtime features but naive full rebuilds create user-visible latency. CloudyPatch generates conference badges using Gridsome + Storyblok + Cloudinary and surfaces the real problem: rebuilds on every attendee cause delays (Gridsome is reported handling ~1,000 entries in ~13s in a cited comparison). Practical fixes are incremental builds that only rebuild changed pages, hybrid SSR for immediate placeholders, and progressive deployment and outsourced media optimization.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:40About me
- 1:49Recap
- 3:58Project Overview
- 5:41Performance
- 6:45Static vs Dynamic
- 8:32Hook
- 10:13Data Source
- 11:50Latency
- 15:35Highbridge
- 17:01Sources
- 17:48Legacy Code
- 19:17Progressive Deployment
- 20:08Hybrid Deployment
- 21:28Summary
related talks
32mStatic Sites go all Hollywood
20mA Saga of Web Rendering Woes
29mJamstack at Scale
22mAdvanced Site Rendering Patterns on the Jamstack
26mIn Defense of Static Sites
43mHow to simplify your life by embracing static site generation
14mStatic Site Generators with JavaScript
20mIncremental Static Regeneration: Static sites on steroids