Rakesh Pai: “The Economics of XHTML” (via Anne Van Kesteren). Anne advises that when you read Rakesh’s article, you sub in “semantic HTML” for “XHTML”. That’s a good substitution, although I actually prefer “clean markup.” Making your markup more semantic is a good thing, up to a point. Once you cross a certain line, your mind begins an inevitable slide into Semantic Extremism, until eventually you’ve convinced yourself that everything should be a list item or some such nonsense.[1] But I digress.
There have been countless articles like Rakesh’s about how XHTML clean markup will save you big bucks. Honestly, I don’t fundamentally doubt the overall theory, but it disturbs me that none of these fine articles puts out hard numbers on how much money you’ll actually save in practice. The most concrete examples in the genre so far are the “redesign articles”, wherein the author picks a large site with crufty markup, redesigns the home page with clean markup, and performs a highly naive calculation of the bandwidth saved. The best article that I know of is Mike Davidson’s interview with DevEdge, and even that piece only provides a theoretical estimate.
So let’s all put on our Business Analyst hats and ask a few questions that might be pertinent for designing an actual case study. To be sure, thinking in BizDev does not come naturally to most folks, certainly not me.[2] So first, a short cleansing ritual, to prepare the mind for these alien thoughts:
Ph’nglui mglw’nafh Forbes R’lyeh wgah’nagl fhtagn! ROI! ROI! ROI! Aiiiiieeee!
Ah, there we go. Now, consider a largish commercial site:
-
What are the actual bandwidth savings over one-month period, factoring in caching, real-world resource request patterns, etc.?
-
How much does a TB of bandwidth go for these days? How much will that same TB cost three years from now?
-
How much developer time does it take to refactor a complicated CMS to produce clean markup?
-
How much developer time does it take to clean up legacy content? Is this archived material accessed often enough to be worth cleaning?
-
Are developers who have modern skills more expensive than old-skool <font>
-happy developers? (I would think so.)
-
What percentage of visitors use NN 4 or IE 4? Does the revenue lost from these visitors outweigh the overall bandwidth savings?
-
How much does it cost to employ other techniques to speed up your site, such as enabling conditional gzip compression? Comparing these techniques with a total redesign, which ones are the cheapest?
I don’t have the answers to these questions. But I do suspect that any web design shops that can answer these questions (with non-foofy numbers) basically have a license to print money.
1. If we all lived in Web Designer City, a metropolis bustling with architects and bricklayers, professors and artists, hustlers and street vendors, you would be the guy staggering down the street, muttering to himself.
2. Business persons tend to ask questions that either A) make no sense or B) are so hard that any response you get back is almost certainly a lie. Or if we’re feeling charitable, a “Wild Ass Guess.”