First commits will set your Nuxt app performance for success!
summary
Project first commits set long‑term performance: starter Nuxt demos score 90+ Lighthouse but real storefronts often drop to ~50, so adopt a server‑first, static-first sites mindset. Enable Nuxt 3 experimental server components (.server files), mark plugins as server‑only, use a lazy‑hydrate component (view‑lazy‑hydration inspired) to defer JS, run nuxi analyze after each added module, and move heavy SDKs into API routes so only display code reaches the client.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:14Performance in Nuxt apps
- 3:40Hello World performance is meaningless for real apps
- 5:47Astro/Quick vs Nuxt speed
- 7:31How Astro achieves superior performance
- 9:38Static deploy for performance
- 11:44Controlling Nuxt bundle JS
- 14:13Static server components in Nuxt
- 16:42Lazy hydration in Nuxt
- 18:31Component interactivity guide
- 20:19Server-only plugins in Nuxt
- 21:43Avoid heavy frontend data
- 22:47Q&A
- 23:50Q&A
- 24:10Q&A
related talks
33mHow Nuxt 3 is allowing us to build faster applications?
30mPerformance-Minded Development with Nuxt 3
26mBe Lazy, Be Smart, Be Nuxt.
25mHow we are optimizing Nuxt without removing features in VueStorefront
34mFast Nuxt.js Applications with PRPL Pattern
33mNuxt.js 2.0
21mNuxt Performances
38mLarge Scale Nuxt Architecture