Qwik: Making sure that easy is same as performant

Is your framework's 'easy' path killing your app's performance? Discover how Qwik's resumability delivers instant interactivity with a near-zero JavaScript payload.

#1about 3 minutes

The performance problem with modern web applications

Most modern websites fail Core Web Vitals because the amount of JavaScript shipped to the client is constantly increasing, which directly harms startup performance.

#2about 3 minutes

Understanding the limitations of hydration in frameworks

Hydration attempts to solve slow initial loads but introduces an 'uncanny valley' and performance overhead by re-executing the entire application on the client.

#3about 5 minutes

Introducing resumability as an alternative to hydration

Qwik's resumability achieves constant-time startup performance by serializing listener information into the HTML, eliminating the need to re-execute components on the client.

#4about 4 minutes

Demonstrating lazy loading and execution with Qwik

A live demo shows how Qwik only downloads the minimal JavaScript code required for a user interaction at the moment it's needed, with a service worker prefetching chunks for a fast experience.

#5about 3 minutes

Moving closures and tree-shaking data with Qwik

Qwik can move function closures between the client and server using `server$` and automatically tree-shakes data, serializing only what's necessary for client-side interactions.

#6about 2 minutes

Solving common performance issues like CLS by default

The framework provides built-in components, like an image optimizer, that automatically prevent common issues like Cumulative Layout Shift (CLS) and generate responsive source sets.

#7about 4 minutes

Q&A on security, tooling, and framework adoption

The speaker answers audience questions about handling server-side secrets, Qwik's use of Vite, the future of resumability in other frameworks, and fallbacks for service workers.