W3C Standards a Speed Sacrifice?

Over at blog.bug.gd they had an interesting article. They state that Google omits some HTML in order to have their page be fast, and thus a better user experience. Some of the tags that the article points out are the closing tags for the body of the document, and the closing HTML tags. These are two tags which W3C documents stated can be omitted in HTML 4.01. The article goes on to explain that by not including certain tags can save 14 bytes or so per request for more complex pages. If we think about how many searches are performed on Google each day, we can only imagine how much bandwidth they are saving, and the money they are saving also. Google has even put together a portal where developers can talk with each other about how to create faster web pages.


On the other side of the spectrum, you have people that like to have everything meet web standards. They feel that meeting web standards provides a better user experience, than pages that don’t have meet web standards. One of claim that they are proud of is by using web standards they can allow visitors who are handicapped also enjoy their site.

The great thing about both groups of people is that they are just as passionate about their code. They respect each other even though they don’t always see eye to eye. Tell us what you think in the comments. Should you drop your sacrifice web standards for a faster web page or should web standards always be meet, even if it means sacrificing load times?

Leave a comment