Website Optimization Measures, Part I

Published on Feb 10, 2008 (updated Feb 5, 2024), filed under development, optimization (feed). (Share this on Mastodon or Bluesky?)

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).

Focus on QA requires occasional website reviews, not necessarily immediate redesigns or relaunches. This week I spent some time analyzing, refactoring, and optimizing my personal sites. I thought to share a few things for inspiration and discussion:

• Removing irrelevant posts. I did indeed browse this blog for irrelevant posts—and found a few. While some might consider deleting posts “taboo,” I do not, if the posts in question decrease the average post quality. I accept that not every post needs to make #1 on Digg, but admittedly, some entries looked like I babbled in order to say something. The removal has made maintenance a little easier (apart from the fact that I will need to remove a few redirects in the future). It didn’t affect many comments; few people commented on those posts, unsurprisingly. There’s no downside removing irrelevant stuff, not even in blogs.

• Editing and removing comments. Some might consider this another taboo but it has a few good reasons, too, some of them mentioned in the new comment guidelines. The most important reason was spam, and my tolerant approach to comments that avoids both moderation and nofollow bears a larger risk of getting spammed without noticing (and that despite I check everything Akismet does, and what gets published). So I went through all comments, removed some, edited or “neutralized” others. While this measure meant a lot of work it increased this blog’s overall quality, and decreased the likelihood of getting “penalized.” It benefits commenters in that it emphasizes and strengthens everyone’s contributions.

• Cleaning up the folder structure for “auxiliary” files. For style sheets, scripts, and images I personally used to use a folder structure like “/bin/css”, “/bin/js”, and “/img”. Not anymore. The mentioned structure has been inspired by UNIX but only makes so much sense, and it doesn’t scale well, either. So I changed the architecture to

  • /media
  • /setup
    • /css
    • /js

  And while this appears to be much better than the former type of organization, I’ll watch how it behaves—so far, it works and scales great. “/media” is not just for images and thus gives me the flexibility to throw in videos as well (something I didn’t do before, not in my private projects), and “/setup” looked like a short name that would roughly legitimate hosting style sheets and the like. Anyway, if there’s something better, I’ll revise it again. Unless cost of problem gets too low, that is.

• Revising use of rel="alternate". I used to add <link rel="alternate"> elements in the head section of documents to point to alternative versions (mostly translations) of the corresponding page. I dropped this, not due to eventual SEO advantages but for maintainability reasons. Adding rel="alternate" only to hyperlinks pointing to alternative versions now needs to suffice.

• Replacing Google and Yahoo verification meta elements by HTML equivalents. Using both Google Webmaster Tools and Yahoo Site Explorer I once decided to use the meta element verification way in order to avoid additional stuff in the corresponding project roots. However, I noticed this had a downside, namely forcing homepage visitors to download these (for them useless) elements. By removing the meta elements and verifying sites with the alternative HTML documents, file size decreased again, and that is great.

As I’ll be leaving Bremen tomorrow for a few days of home search in Zurich and my next farewell tour in Berlin, I had to hurry and keep some arguments and explanations a little short. At least four additional measures are waiting in part II, however. 😊

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

About Me

I’m Jens (long: Jens Oliver Meiert), and I’m a web developer, manager, and author. I’ve been working as a technical lead and engineering manager for companies you’ve never heard of and companies you use every day, I’m an occasional contributor to web standards (like HTML, CSS, WCAG), 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 experiences and views. (I value you being critical, interpreting charitably, and giving feedback.)