How micro-frontends and NextJS can 4x site performance
summary
Rewrites a slow site into three micro-frontends (marketing, booking, dashboard) hosted via AWS Amplify with root-level rewrites so paths route to separate apps, extracts a shared component library as an npm package, and adopts Next.js for built-in image script and font optimizations plus reliable page-level code splitting. Results show unused JS drops and build time shrinks (10 minute monolith to ~5/3/2 minute apps) and lighthouse moves from 27→65 lighthouse score with big gains in TTI LCP and speed index.
AI-written summary · about
chapters (12)
- 0:00site performance Emily Thomas
- 2:30Just kidding
- 4:151 specialist hire...
- 10:31How can I do that?
- 10:48Find natural functional breaks in your application
- 11:23Understand the tradeoffs.
- 12:35Choose one framework across your applications for consistency.
- 13:31Create a hosting game plan for your applications.
- 15:13Create sensible routing between applications.
- 15:55Measure success and time cap your team.
- 16:26Get buy in from stakeholders and leadership.
- 16:58Halfway Results
related talks
24mMicrofrontends
19mHow Hopin is Moving 10x Faster: Microfrontends at Scale
36mMicro Frontends in Action!
25mMicro Frontend: a microservice architecture from your frontend web apps
45mMicro Frontends in Action!
01h 17mChallenges in Building Micro Front Ends
21mMicro-frontends: 3 years ago
46mMicro Frontend: the microservice puzzle extended to frontend