Pre-Rendering Strategies
summary
Angular server-side rendering uses Angular/platform-server and renderModuleFactory to output HTML ahead of bootstrap, improving time to first meaningful paint while avoiding large hits to time to interactive. Options are app-shell, critical content, or full session rendering; timing choices are build-time, request-time, lazy/cron with caching. Example: 100,000 products × 10 locales would be ~10 billion pages at build time, reducible to a million by skipping user-specific widgets. Event-replay libraries (Jeff Whelply et al.) record and replay interactions during bootstrap.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:31Jeffs background
- 1:43What is prerendering
- 7:12Prerendering process
- 9:34Replaying user events
- 11:40Prerendering strategies
- 13:36Content strategy
- 17:37User strategy
- 18:31Use cases
related talks
21mStrategies for Server Side Rendering Angular Applications
22mAngular Pre Rendering for SEO, Speed, and Happy Users
19mA plethora of rendering ideas
28mServer-side rendering with Angular 2
41mServer-side rendering with Angular—be faster and more SEO, CDN and user-friendly!
24mAngular 2 Server Side Rendering
15mPersonalization, Performance, and Probably Dynamic Content
26mServer Side Rendering with Angular Universal
