I was recently made maintainer of the json gem, and aside from fixing some old bugs, I focused quite a bit on its performance, so that it is now the fastest JSON parser and generator for Ruby on most benchmarks.
Performance | 2024 | The Web Almanac by HTTP Archive
Performance chapter of the 2024 Web Almanac covering Core Web Vitals, with deep dives into the Largest Contentful Paint, Cumulative Layout Shift, and Interaction to Next Paint metrics and their diagnostics.
We'll walk through key configurations like Tiered Cache, Cache Reserve, and crafting specific cache rules, highlighting how these optimizations benefit Pillser's users.
Page Speed Insights and Lighthouse can't evaluate performance across your entire stack of services and apps. You need something more powerful: tracing.
Speeding up the JavaScript ecosystem - npm scripts
'npm scripts' are executed by JavaScript developers and CI systems all around the world all the time. Despite their high usage they are not particularly well optimized and add about 400ms of overhead. In this article we were able to bring that down to ~22ms.
How analyzing your codebase can save you time and money | nicolae.tech
A comprehensive guide about hotspots in your codebase, cognitive complexity and avoiding disasters by being proactive. An article inspired by the book "Your Code as a Crime Scene" by Adam Tornhill with practical examples.
How many bytes is "normal" for a web font: a study using Google fonts
TL;DR: If your font file is significantly larger than 20K you may ask yourself "How did I get here?".For images I think we (web developers) have a sense of how many bytes we can expect an image we see on a page to be. A JPEG photo? 100-ish K is ok for a decent quality. Less is nice. How about 200K?