I have a vague worry that, as we put more and more computation into CSS, web devs are going to end up with performance issues that are difficult to trace to their source compared to JS solutions. The answer is to surface this in DevTools I guess.
Jun 15, 2026 at 1:33 PM
schalkneethling/css-benchpress
css-benchpress aims to help developers and tooling authors discover where CSS patterns become performance problems by growing realistic web-platform test cases until measurable regressions appear.
Solving Performance for 2D & 3D Web Apps: Finally!
The many, many, many JavaScript runtimes of the last decade
This last decade has seen an inundation of new JavaScript runtimes (and engines in equal measure), enabling us to run JavaScript in all manner of contexts...
Reading a Performance Profile: Field Guide
An interactive field guide to the Chrome DevTools Performance panel: waterfall, flame chart, LCP, CLS, INP, and the Insights panel.
2026 CSS wishlist – Nathan Knowler
What I’d like to see prioritized for CSS in 2026, how those features will allow us to create better web-based design systems, and how they renew separation of concerns.
The CSS Selection - 2026 Edition - Project Wallace
The CSS Selection shows real-world CSS usage from over 100,000 websites and looks at the most important metrics.
Web Engines Hackfest 2025
Bring the Console API to CSS with css-console
Web Components Are Not the Future
A few years ago I wrote an article suggesting that Web Components might not be the most beneficial...
Frontend Minimalism in Action: Do More With Less JavaScript | Peter Kröner | webinale Berlin 2026
Next.js — The Perpetual Beta Framework
Exploring 6 years of Next.js, from early days to App Router & RSC, with migrations, performance tweaks, and framework insights
There's no reason for software to be slow anymore
The other day, I saw a viral tweet saying that people talking about how LLMs are causing slow, bloated, code are going to eat crow once they re-write everything in super-optimized assembly. We're not quite at the point where we want to write everything in assembly, but some variant of what Nolan Lawson said about testing, you can choose how many bugs you want now, which I less eloquently noted here, is becoming more true for performance.
Do we still need build tools?
Do we still need Rspack, SWC, PostCSS, Vite, Parcel, Webpack, Turbopack, esbuild, Rollup, Rolldown, Babel, Autoprefixer, esbuild and Lightning CSS in 2026?
You should know this before choosing Next.js
Picking the technology stack for a project is an important and consequential decision. In the enterprise space in particular, it often involves a multi-year commitment with long-lasting implication...
