Website Optimization Measures, Part XVI
Just five weeks after the last episode, here’s the next collection of refactoring and optimization ideas. My last nights and weekends were busy.
Removing trailing tabs and spaces. Right on the train when I wrapped up Part XV of this series, I caught the refactoring bug and probed into whether in any of my repositories, trailing tabs or spaces had snuck in (despite settings to prevent that). They had. And so I cleaned up, and reviewed IDE settings, and set a reminder to check on this on a regularly (but quite infrequent) basis.
Reviewing HTTP headers. In one of those coincidences that one hates, I checked HTTP headers for a blog category, only to find the following:
# curl -I https://meiert.com/en/blog/categories/development/ … link: <https://meiert.com/en/>; rel=canonical
Yeah. That was actually not trivial to fix because of the system in use, having me resort to an emergency fix “unsetting” the respective header for some pages. I’m testing and refining—and passing this on as something to be aware of. This stuff happens.
Adjusting handling of site generator exports. I put my site generator exports under version control—for one, to have a better sense for what changed, for another, to make it faster to roll back if there are any issues. My setup so far has meant to store these exports in a monorepo in Bitbucket—but as the source repositories exclusively live on GitHub, and not to “pollute” said monorepo, I created an “exports” repository on GitHub, just for this purpose. I love it.
Making more use of
citeelements. Having a way to mark up (or down)
citeelements is my most-missed feature in Markdown, because I point to other works, using their titles, all the time. I noticed that on Frontend Dogma, however, I could but weren’t using
citeto mark up all the various articles being pointed to—and changed that. (Now I’m thinking about not styling them in italics… but that, as you know, is now a formatting question, and not a semantics one.)
Experimenting with variable fonts. After running into v-fonts.com I felt I finally had to play with variable fonts. Frontend Dogma, again, looked like a great playground for that. The first tests were promising—until I found that the fonts I needed weighed 10 times as much as the ones I was using (Times, and you read that right). So, yes, no. I’ll play again, and probably write about that, too, but playing isn’t worth a tenfold font payload increase to me—the cost of problem isn’t high enough.
Adding “social logo” variations. Admittedly, on this site, the “brand” color (
#c08) is a fairly… strong one. The meiert.com palette, however, works with much softer tones. I thought about this and wondered, why not use these softer colors on social media… and even rotate them? So I created four soft-color social logo variations, through which I now loop for every (English) blog post. As a test. What do you think, when scanning my Twitter timeline?
Refactoring no-break spaces. For the longest time I’ve used
for no-break spaces. Not anymore—for one, I learned to key in no-break spaces by hand (macOS: ⌥/option + space); for another, my editors, particularly IntelliJ IDEA and WebStorm, display no-break spaces so sufficiently, that that there doesn’t seem to be need anymore to work with these characters by means of an entity reference.
Reordering metadata. I had run into Harry Roberts’ Get Your Head Straight presentation before, but some details escaped me—most notably his preferred elements order in the document
head. I went for it—and reworked my projects to go by this order. I’m still testing, but also happily heeding Harry’s advice.
During this refactoring, I also removed all
metaelements declaring an encoding: All servers had always been set up to deliver everything as UTF-8—and because UTF-8 is the default.
This is a part of an open article series. Check out some of the other posts!
I’m Jens, and I’m an engineering lead—currently manager for Developer Experience at LivePerson—and author. I’ve worked as a technical lead for Google, I’m close to W3C and WHATWG, and I write and review books for O’Reilly. 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 a question or suggestion about what I write, please leave a comment (if available) or a message. Thank you!
Maybe this is interesting to you, too:
- Next: HTML Concepts: Unstyled Documents
- Previous: 10 Quick Tips for a Great Mastodon Experience
- More under Web Development, or from 2022
- Most popular posts
Looking for a way to comment? Comments have been disabled, unfortunately.
Get a good look at web development? Try 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.