In rare moments, you might want to execute script tags injected with React's dangerouslySetInnerHTML prop. Here's how to make it possible.

For the best performance, there’s no good reason content-focused sites should ever serve an uncached page to a visitor. With modern caching directives and other approaches on the table, it’s easier than ever to preventing visitors from knowing your origin exists at all.

Image performance on too many websites these days suck pretty bad, making it difficult to build strong user experiences and SEO. I’m building this service that reformats, optimizes, and aggressively caches images just by prefixing the URLs. Hoping to serve people with established sites, but who don’t have a lot of time or resources to stay on top of image performance themselves. Let me know your thoughts, and how something like this might be improved down the road.

I wrote a blog post breaking down some of the reasons Maps (and WeakMaps) are especially useful tools when working with a large number of DOM nodes.

With so much going on on the browser's main thread, keeping a canvas animation buttery smooth can sometimes be a challenge. I wrote about how Web workers can help ease that hassle by handling the painting process elsewhere.

Reviewing some of the most common approaches available to remove event listeners in JavaScript.

Much appreciated feedback!