Website Optimization Measures, Part V

Published on November 3, 2008 (↻ February 5, 2024), filed under Web Development (RSS feed for all categories).

This and many other posts are also available as a pretty, well-behaved ebook: On Web Development. And speaking of which, here’s a short treatise just about managing the quality of websites: The Little Book of Website Quality Control (updated).

Almost half a year since my last article it’s about time to present version 5 of random website optimization measures, hopefully of use for your site as well. Short and crispy, to use a random German saying.

• Migrating to HTML 5. Well, we can use HTML 5, and what’s better than going ahead and doing so. Shortly after “launch” of example.ms I decided to revise UITest.com and the World’s Highest Website to use HTML 5 too, to then continuously use it for some other projects, including the all new Code Responsibly. And while I understand from direct feedback as well as through sites like W3C Sites that knowledge of the new HTML is not too common yet, it’s still good for every developer to play with. Of course, HTML 5 pages should be valid, too.

• Refactoring and removing abbr elements. It took me some time to go for that change, however considering relatively and unnecessarily big maintenance issues, a slight performance impact, as well as plans to make @title required in HTML 5 (which got dropped after people, including me, raised concerns) I decided to abandon the habit to use abbr for every abbreviation. I did so for all my sites.

• Switching to Google Analytics. Having been a happy Mint user for two and a half years I reached the point where I wanted one, ideally free analytics solution for all projects that at the same time allowed for more insight into the data. I decided to add Google Analytics (GA) code to all my projects [I later pedaled back]. I miss some things I had with Mint, above all real-time data, but I certainly don’t regret the change. After all I used GA on other sites ever since Google acquired Urchin, and so I knew what I would get.

  Another topic, and one that I’ll write about in more detail soon, however try to do A/B or multivariate tests of your site and its elements. I guess it’s fine to say that Website Optimizer allows exactly that, but there are probably other good tools, too.

• Adding Google Analytics privacy notes. Some of you may have already heard about that, but apparently there’s some sort of requirement in Germany to have a privacy note “in some way” saying that you’re using GA and what GA’s doing. Neither am I a lawyer nor am I living in Germany anymore, but I figured it might not hurt to add that note to my sites’ pages—even in the legal notice of this part of my website. “Learn the rules so you know how to break them properly,” the Dalai Lama is quoted, but I’m not too familiar with all the rules here so I’m just playing it safe.

• Revising and improving headings use in posts. That’s a boring one: You know this semantics quiz where it’s about using headings and paragraphs or lists and either headings or stronger emphasis or whatever, which would perfectly apply to this post, too? Well, I checked most if not all posts and articles for “semantics potential” and adjusted in some cases. A trivial thing; apparently I had too much time on my hands.

• Proofreading and editing all posts and comments. History kind of repeats itself here, because I once again decided to review (or started reviewing, to be precise) all contents of this weblog. I’m aware that some people have reservations about this, but that doesn’t mean that the measure is not good for quality. In fact, I could improve some posts, deleted at least two rather stupid ones, and I touched comments that I felt were spammy or nonsensical. No worries, please see this measure as one that helps making better and more useful archives, well, websites.

• Testing font alternatives. Not boring, just short: I tested additional fonts and found that sans serif fonts work better for this site’s headlines (interestingly, resulting in corbel, optima, arial, sans-serif), and I tweaked the main font to support that change (cambria, palatino, georgia, serif).

This is a part of an open article series. Check out some of the other posts!

About Me

I’m Jens (long: Jens Oliver Meiert), and I’m a frontend engineering leader and tech author/publisher. I’ve worked as a technical lead for companies like Google and as an engineering manager for companies like Miro, I’m close to W3C and WHATWG, and I write and review books for O’Reilly and Frontend Dogma.

I love trying things, not only in web development (and engineering management), but also in other areas like philosophy. Here on meiert.com I share some of my views and experiences.

If you’d like to do me a favor, interpret charitably (I speak three languages, and they do collide), yet be critical and give feedback for me to fix issues, learn, and improve. Thank you!

Comments (Closed)

1. On November 3, 2008, 18:25 CET, Louis said:

   That’s why I gave you the best score on Quality when answering your survey 😊

2. On November 3, 2008, 20:08 CET, Dave said:

   Oh, that everyone did this. Your new headline font is hot.

3. On November 5, 2008, 10:33 CET, Jens Oliver Meiert said:

   Louis, Dave, thank you!