This site was down for a couple weeks and it really brought home just how often I visit. I was reduced to looking up archived versions on the Wayback Machine, a circumstance which I’d chalk up to its being a very thorough guide to :nth-child and my brain refusing to memorize how to write negative ranges no matter how often I use them.
I’m surprised I’ve never linked to it before but it’s back now and I promise never to take it for granted again.
Found 99 vulnerabilities (84 moderately irrelevant, 15 highly irrelevant)...
Bookmarking this article for the next time dependabot alerts come up at work. It’s a really fun read on a pretty dry topic and full of an appropriate amount of incredulity at some of the high severity vulnerabilities that get flagged.
Space Time has a regular version with the full design and lightly touching letters and a stackable, overlapping version with separate layers for the base, outline, shadow, and stars (plus the base and outline versions can be used as standalones!).
When I mentioned a couple weeks ago that I was working on a font with fussy kerning, this is the one I was talking about so if you notice any oddities please let me know in the comments or through the contact form.
It’s time for another Google Core Web Vitals themed TIL. This one concerns image loading. Specifically, huge, above the fold image preloading.
The site I work on uses a lot of super wide to full width hero images. We’d done some previous optimizations around serving images in WebP format (Serve images in modern formats) and using picture and srcset for responsive images (Properly size images). I won’t go into details since those topics already have a ton of tutorials that explain things better than I ever could. In fact, Smashing Magazine alone has you covered with Using WebP Image Format Today and Responsive Images Done Right: A Guide To picture And srcset.
Preload critical assets to improve loading speed.
The one downside to our earlier work? It made things a little more confusing when we started looking into preloading images.
Preloading assets that aren’t actually used isn’t particularly helpful (Chrome will even warn you if you do it!). If you’re serving a WebP image but preloading the fallback or preloading a mobile image on a desktop browser, you aren’t getting any benefits out of it.
Let’s say you have a picture block that selects an image based on browser support, screen resolution, and breakpoint:
The first question is how to handle different image formats. Looking at the Can I use entries for Webp image formats and preload, it seems pretty unlikely for a browser to support preloading but not WebP images. And according to a quick aside in this Addy Osmani article on hero images, you can use the type="image/webp" attribute with a link tag to specify that you want to preload a WebP image.
Next, we need to deal with screen sizes and resolutions. In addition to type, the link tag supports media and imagesrcset attributes which should look very similar to the media and srcset attributes on our source and img tags. The main difference is that you have to be more explicit with your breakpoints since the browser won’t be choosing the best image itself.
Putting that all together, you would add this code to your head tag to preload the images from the example above:
I’m finishing up a font with some extremely finicky kerning so this list of words with awkward letter combinations from the Hoefler&Co. blog is fantastic. There’s even a Github repo with PDFs.
I’ve been in a real sixties retro design mood lately (or, if you look at my fonts, maybe I always am at least a little bit). So Ducky Manly by Allmo Studio really hits the spot. It’s free for personal use and the commercial version comes as a duo.