React to the Need for Speed
summary
SumUp faces slow pages from bloated JavaScript so the team adds bundle-size tools and automated checks, applies code splitting + multiple webpack entries to avoid loading React on simple pages, and implements SSR + hydration (Next.js) to improve first paint but TTI still sits around ~9s. Measurements use Google Analytics + User Timing from real devices; concrete network math: 4 Mbps ≈ 500 KB/s so a 5 MB page takes ~10s; JS parse 1 MB ≈ 2s on iPhone 8, ~13–15s on mid Android.
AI-written summary · about
chapters (15)
- 0:00Start
- 4:35SIDE QUESTS
- 4:50RISE AND FALL OF EMPIRES
- 5:00MONSTERS
- 6:59THE STORY
- 9:22AVERAGE CONNECTION SPEED IN BRAZIL
- 10:17THE PERFORMANCE PERCEPTION
- 12:01THE COST OF PROCESSING TIME IN SECONDS FOR IMB OF JAVASCRIPT
- 13:17RAIL MODEL
- 16:06REACT SINGLE PAGE APPLICATIONS
- 17:48BUNDLE SIZE BUDGETS
- 18:18CODE SPLITTING
- 20:27MULTIPLE ENTRY POINTS
- 22:18META-FRAMEWORKS
- 24:50LESSONS LEARNED
related talks
08mLightning fast SSR React apps with top perceived performance and no (client side) JavaScript
24mHoussein Djirdeh - Progressive React
25mDesigning High Performance React Applications
16mNeed for Speed: How Modern JavaScript Frameworks Are Solving Web Performance
26mProgressive React
34mOptimizing Performance in Large-Scale React & Node.js Applications
32mPractical Performance Tips Building Progressive Web Apps
26mLightning Fast React Apps
