3 ms·
Looking the home page (which looks to be built with seed-rs), a ~500k wasm file is loaded. The static part loads fairly fast, but none of the links work until
by turtlebits 5y ago
Looking the home page (which looks to be built with seed-rs), a ~500k wasm file is loaded.
The static part loads fairly fast, but none of the links work until after the wasm loads (you can tell because the header changes)
Looks like the entire site is in the wasm file as no additional network requests are made. Doesn't seem great for general purpose web sites (like your home page).
- sfvisser 5y agoNot that I disagree — it's rather steep — but not super unlike many react/vue based sites. Frameworks like Next.js can help by adding seamless server side rendering so at least your links will work before your js/wasm is loaded. Maybe seed-rs can move into that direction as well.
- brundolf 5y agoIs that 500k with or without gzip? With gzip, that would be huge. Either way there are certain techniques like bundle-splitting and hydration that will probably have to be reinvented for these WASM frameworks, unfortunately. For the moment they're probably better suited to high-complexity browser-based tooling that needs the extra performance, vs simple crud sites. Edit: on second thought, for an entire multi-page site in one bundle this wouldn't be super huge. I'm used to smaller numbers but I'm also used to split-bundles.
- turtlebits 5y agoFor the site (including wasm) - (over the network) 597 kB transferred (uncompressed) 2.3 MB resources
- azakai 5y agoThe wasm file is dc7bb6f6208af7f13f16.module.wasm which is 2MB uncompressed.
- zhiel 5y agoNow imagine if the WASM folks had all the bundler/dead code elimination/link time optimization..., its coming, sorta...