qwik

Qwik does not do hydration because it is resumable. Hydration can take several seconds, depending on the complexity of your application and mobile device speed. Qwik applications are instantly interactive even on slow mobile devices leading to a perfect Google PageSpeed score. Qwik apps begin their life as SSR/SSG. Qwik serializes the application's state and framework state into HTML upon rendering the application. Then Qwik can resume execution where the server left off in the browser because all the data Qwik needs is in HTML. No JS needs to be downloaded or executed until it is needed to handle user interaction or rendering. Never think about lazy-loading of your code again. Qwik was built around lazy loading as its core primitive and took it to a whole new level with zero effort for the developer. Event listeners, rendering function, side-effects, creation blocks, it all gets lazy-loaded on an as-needed basis.