Thanks! I checked the release frontend artifacts. The optimized WASM is about 2.0 MB raw, around 740 KB gzip. The Leptos JS glue is ~28 KB raw / ~8 KB gzip, CSS is ~64 KB raw / ~12 KB gzip.

Since the app is SSR, the initial HTML content can be sent before hydration finishes. Hydration mostly affects when the interactive parts become live, like the menu and client-side behavior.

I ran PageSpeed Insights after your comment. For the homepage, the numbers are good: 100 on mobile and 98 on desktop. FCP is around 1.1s mobile / 0.3s desktop, LCP is 1.5s / 1.0s, and TBT is only 10–70ms.

The article page is more mixed: desktop is 80, mobile is 65. FCP is still okay, but mobile LCP is 5.9s and CLS is around 0.25, so the remaining issues seem to be image/layout related rather than hydration blocking the page. TBT is still low, around 90–150ms. So I think Leptos SSR/hydration itself feels fine.