Jason Grigsby

There is one type of project that we seem to excel at, but that we don’t know what to call it. What would you call it?

We’re nearing the time of year when many retailers enter a website code freeze for the holiday season. Here are five low-risk improvements you might be able to squeeze in before your code freeze arrives

I get a bad feeling in the pit of my stomach when I have to tell someone that there is something deeply wrong with their website—especially when I know that it is too late to fix it. I hate that feeling. And I felt it twice recently.

I see a recurring performance problem on many ecommerce sites—the most important images on the page are being lazy loaded when they shouldn't be. You’re better off not implementing lazy loading at all than implementing it incorrectly.

If you buy a burgundy dress and what arrives is tango red? Do you return it? Probably. Product images matter. Returns cost businesses billions and have a big environmental impact. Read our New Recommendations for Ecommerce Images.

Hey there, web enthusiasts! We’ve had the pleasure of partnering with some big brands to revolutionize their websites and create extraordinary user experiences. But hey, we’re not too proud to admit that we’ve hit a bit of a downturn lately. That’s where you, our awesome community, come in.

It’s counterintuitive and misleading, but if you use YouTube’s no cookies domain, YouTube will still set cookies when someone starts playing a video.

With the news that CSS Container Queries have shipped in nearly all stable, modern browsers, it’s time to revisit responsive images and ask how they fit in a container query world. Are we on the right path?

After seventeen years, An Event Apart (AEA) is no more. I know all things must end, but this one hit me hard. It’s been a couple of weeks, and I’m still thinking about what AEA has meant to me, and how much I will miss it.

Components are everywhere, but they are rarely reusable across systems. A design system component is written differently than a CMS editor component. But does it have to be this way? Could we take one set of components and port them to multiple JavaScript frameworks, import them into design tools, and use them for the editing interfaces in content management systems?