WebPlatform
Core Web Vitals and Web Performance at Traveloka
Performance work on high-traffic, conversion-critical pages, driven by real-user measurement and performance budgets.
- Role
- Software Engineer (Web)
- Period
- 2018–2025
- Stack
- Core Web Vitals · Next.js · Real-user monitoring · Code splitting
The problem
These were high-traffic, conversion-critical web experiences, so performance had to be measured from what users actually experienced, not from a developer laptop.
The approach
- Measure real users first. Real-user measurement decided what to fix, and performance budgets kept regressions from creeping back in.
- Cut the JavaScript the browser has to run: code splitting, lazy loading and dependency optimization.
- Fix the rest of the path: JavaScript execution, rendering, networking, images and third-party scripts.
Talking about it
I turned the lessons into talks: "Performance: Core Web Vitals Top Recommendations + INP" at DevFest Jakarta 2023, and "Bridging the Gap: Making It Easier to Build for the Web" at Google I/O Extended Jakarta 2022.
I also write about it: the event loop is not what you think explains the long tasks behind poor INP and how to break them up.