Mastodon Feed: Post

slightlyoff@toot.cafe ("Alex Russell") wrote:

(trying this again because it was pointed out previously toot traced the old site)

Shot:

https://thenewstack.io/new-york-public-library-on-choosing-react-to-rebuild-website/

Chaser:

https://www.webpagetest.org/video/compare.php?tests=241117_AiDcAY_3AK-r%3A1-c%3A0&thumbSize=200&ival=100&end=full

Main thread unresponsive until ~15 seconds in. The new version *paints* faster, but isn't usable any faster. We're celebrating this a progress?

https://www.webpagetest.org/video/compare.php?tests=241117_AiDcAY_3AK%2C241117_BiDcMM_2W7&thumbSize=200&ival=100&end=full

It's malpractice to chose Next.js, or any other CSR-premised stack, for delivering public services.

/cc @ricmac

Attachments:

• WPT waterfall for new Next.js-based NYPL Digital Collections site on a low-end devices and P75 network connection. The main thread doesn't become consistently interactive until the 15 second mark. (remote)