Caching, components, and the render-blocking path
Hugh Haworth argues that Cache-Control is an unusually potent tool for web performance. The angle that gets overlooked is HTML caching: because HTML changes most often and sits as the parent of most other cached assets, most people skip caching it entirely. It can be done carefully — a forum with rapidly changing page content is a poor candidate — but it tends to be a deliberate omission. The practical route is letting Cloudflare handle it.
Web components and the framework question
The idea of web components carrying a framework along, possibly a mix of unrelated ones, is an uncomfortable one on first read. Nolan Lawson works through the nuance: a couple of kilobytes that can be lazy loaded or code-split out isn't a major cost, and the framework in question may be optimized for runtime performance.
Measuring vitals in a component
Stefan Judis published web-vitals-element on npm, a package that boots a <web-vitals> component reporting CLS, FID, LCP, and BVD. A demo is available; the package notably won't build on Skypack.
Pitfalls, blocking, and other reading
- Jake and Surma's top 10 performance pitfalls list is full of surprises. The guess is that today's low-hanging performance fruit either disappears through technological improvement or gets handled by site owners and hosts, leaving a new set of problems as the top offenders.
- Sia Karamalegos' deep dive on render-blocking resources defines them as files that "press pause" on the critical rendering path, interrupting one or more of its steps. Anything render-blocking should be intentional — critical CSS, for example — rather than accidental.
- Colin Armstrong's account of cutting a Next.js page size by 3.5x and reaching a 98 Lighthouse score leans on dynamically loading assets, shrinking assets, and responsive images, with much of the diagnostic and fixing tooling already built into Next.js. The PurgeCSS and Tailwind portion stands out: shipping 350KB of CSS where 10KB would do means Tailwind is being used wrong — unused selectors should be purged, or the JIT compiler used to generate only what's needed.
- Nolan Lawson on text input responsiveness: keep expensive main-thread work from blocking the
inputevent, and batch UI updates withrequestIdleCallback. - Zach Leatherman's vector/raster split gets the smallest file by dividing a graphic in two — SVG for what vectors do well, a heavily optimized raster (ideally AVIF) for the rest — and layering them.



