Website Optimization Measures, Part XIII
Post from March 5, 2022, filed under Web Development.
A fresh installment of the series, today some notes and observations on improving SVG and HTML, styling emphasis and code, and making better use of images. (If youāre new to these entries, here is where I casually share improvements to my personal projects.)
-
Adding
title
s to SVG files. Quite randomly poking at and optimizing SVGs in my projects, I noticed how many of them had no meta data, no nothing about their contents. That looked like a missed (accessibility) opportunity, and after validating a few tests I decided to make sure each SVG, starting with logos, had atitle
element that could represent the image. Is it good practice? I believe yes. -
Revisiting html-minifier settings. I have a standard config for html-minifier, however as Iām constantly studying HTML (I completed the pilgrimage!), I questioned and reviewed the old setup. You can check my latest setup in the Eleventy config for Frontend Dogma. (Iām taking note to talk more about special cases, like not removing all quotes, and not always minifying HTML.)
-
Reviewing use of
@autocomplete
. Iām collecting string for these posts for months, and in this case I donāt know anymore what I did š But, Iām sure, it led to better use of theautocomplete
attribute. -
Adjusting styling for
strong
elements. As a great exercise in semantics, Iāve run a few projects where I styledem
andstrong
elements the same way. (This way, you canāt go by appearance, you have to go by meaning.) But for design reasons, on this website, I changed this, so that bothem
andstrong
are still using italics, butstrong
emphasis also gets a background color. What do you think? -
Styling code blocks! I thought about this for many years but couldnāt get myself to add the needed code (minimalism). Then, running into highlight.js (and āinheritingā Prism from my Eleventy projects), I thought about it again. And I added highlight.js to meiert.com, injected only when a code block is actually present, and leaving it to highlight.js to figure out the type of code. That finally reconciled my preference for minimal code with the added usability of syntax-highlighted code samples.
-
Adding back favicon markup ā ļø How ironic, no, given how I had written that the ideal favicon markup consists of nothing. But the user agents you yourself are using are powerful, and Firefox on Android has this issue of not using (or discarding) smaller-size favicons. Yet favicons serve a purpose and theyāre useful, and therefore I grudgingly andāoh please, dear All-That-Is!ātemporarily added
link
elements to my projects, pointing to each of their favicons. -
Switching to large social images. For every personal project, I prepare one large āsocial logo.ā For historic reasons, however, I used markupāthe most minimal social markup I could identify at the timeāthat didnāt take advantage of that. At first suspecting problems with the specific dimensions of these images, it turned out that, for Twitter, all I had to do was to switch from
<meta name=twitter:card content=summary>
to
<meta name=twitter:card content=summary_large_image>
Done. You can see said āmost minimal social markupā in action on any of my projectsālike in the Eleventy base template of Frontend Dogma.
This is a part of an open article series. Check out some of the other posts!
About Me

Iām Jens Oliver Meiert, and Iām an engineering manager and author. Iāve worked as a technical lead for Google, Iām close to the W3C and the WHATWG, and I write and review books for OāReilly. Other than that, I love trying things, sometimes including philosophy, art, and adventure. Here on meiert.com I share some of my views and experiences.
If you have questions or suggestions about what I write, please leave a comment (if available) or a message.
Read More
Have a look at the most popular posts, possibly including:
Looking for a way to comment? Comments have been disabled, unfortunately.

Perhaps my most comprehensive book: The Web Development Glossary (2020). With explanations and definitions for literally thousands of terms from Web Development and related fields, building on Wikipedia as well as the MDN Web Docs. Available at Apple Books, Kobo, Google Play Books, and Leanpub.