The weirdly obscure art of Streamed HTML - DEV Community
dev.to · 4,691 words · saved by 1 readers
Literally “one weird trick” to massively improve Time To First Byte
My goal from last time: reuse our existing APIs in a demo of the fastest possible version of our ecommerce website… and keep it under 20 kilobytes. I decided this called for an MPA. (aka a traditional web app. Site. Thang. Not-SPA. Whatever.) And with that decision, I doomed the site to feel slow and clunky In theory, there’s no reason MPA interactions need be as slow as commonly encountered. But in practice, there are many reasons. Here’s an example. At Kroger, product searches take two steps: Send user’s query to an API to get matching product codes Send those product codes to an API to get
related reading
- Streaming HTML – Master.dev Blogfrontendmasters.com
- How's Linear so fast? A technical breakdownperformance.dev
- The new wave of Javascript web frameworksfrontendmastery.com
- The Web Animation Performance Tier List | Motion Magazinemotion.dev
- App Router: Streaming | Next.jsnextjs.org
- The Design of This Websiteturntrout.com
- The unreasonable effectiveness of HTML — examplesthariqs.github.io
- RSC From Scratch. Part 1: Server Components · reactwg server-components · Discussion #5github.com
- The Descent — What Happened to the Frontend While You Weren't Watchingdavidpoblador.com
- The Web Animation Performance Tier List | Motion Magazinemotion.dev
- APIs All the Way Down - Not Boring by Packy McCormicknotboring.co
- 7 Principles of Rich Web Applicationsrauchg.com