Personalization, Performance, and Probably Dynamic Content
summary
Claim: deliver CMS-driven personalized pages with Angular without request-time slowdown by pre-rendering and caching all product pages (served from cache saves ~4ms per visit), using platform-server SSR for build-time rendering, measuring that batch renders are ~100ms while per-user personalized renders cost ~400ms, classifying personalized UI as constant vs conditional and implementing ghost placeholders plus end-of-page vertical expansion so personalization injects without layout shift; a demo app exists though initial deploys needed fixes.
AI-written summary · about
chapters (7)
- 0:00Intro
- 1:00Phone Shopping App - Business Requirements
- 3:41Our Pre-Rendering Strategy
- 5:56Thinking in Page States
- 6:16Rules for Designing Two States
- 8:13Classifying Personalized Components
- 10:55Planning for Personalization
related talks
22mAsynchronous Personalization
23mPre-Rendering Strategies
16mHigh-speed personalization with Next.js
19mA plethora of rendering ideas
32mBuilding a dynamic SPA website with Angular
17mPerformance Engineering in Dynamic Web
22mAngular Pre Rendering for SEO, Speed, and Happy Users
33mPerceived faster Angular applications