✳flâneur — a map of the web's best reading

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

Explore this link on the map →

related reading