Decoupled WordPress: Enterprise Performance
summary
Covers concrete decoupled patterns: WordPress as CMS with Gatsby static builds, Angular single‑page apps, and Next.js/SSR tradeoffs; tools used include ACF, WP GraphQL, Netlify, Pantheon, AWS Amplify, Firebase and Amazon API Gateway and a plugin called Fireboost iio that caches WP API responses. Claims: enterprise performance needs backend shielding and caching; static builds give huge FCP gains but cause 1–2 minute rebuild delays; a GoodHire migration finishes in ~4 months; heavy dashboards hit JSON size limits and need serverless endpoints to avoid TTI/TBT issues.
AI-written summary · about
chapters (18)
- 0:00Introduction and speaker background
- 1:04Agenda and audience check
- 1:48Traditional vs headless CMS explained
- 3:14Enterprise performance priorities
- 4:19Performance planning fundamentals
- 5:01Browser performance metrics
- 10:19Frontend architecture selection
- 13:07Single page applications vs JAMstack
- 17:49JAMstack with Gatsby and WordPress
- 20:38Backend performance and shielding
- 22:03FireBoost IO caching solution
- 23:06Case study: GoodHire website
- 26:45Case study: Book widget app
- 29:37Case study: Wealth manager dashboard
- 31:46Q&A: Project scope and team size
- 34:26Q&A: FireBoost IO functionality
- 35:51Q&A: Containers and AWS
- 36:56Q&A: FireBoost IO with multisite
