Validity throughout Google’s homepage
Recent web standards confront Google’s homepage with validity issues, in terms that is does not minimize the number of potential visitors, the lack of bandwidth control.
   Recreating Google’s homepage in a valid HTML by reducing the file size and adding several CSS rules and different attributes can be of help.
   Nevertheless, we are talking about a deprecated HTML throughout Google’s services and front page.
Experiment with XHTML Strict 1.0 along with CSS and JS files, by removing all the scripts and all the spacing you’ll end up with a deprecated page of just a couple ok K. Be aware that CSS files tend to cache much better, especially when the same CSS modules are re-used across the webpage.
  Google isn’t using invalid markup to save bandwidth, but the reasons to why Google’s developers do not implement a valid solution, is still a puzzle to me.
Invalid markup which is also less than semantic makes for an accessibility nightmare. While Google may be easy to use for the majority of its users, using the service with any sort of disability would be a daunting task.
Highlighting bandwidth savings can be a benefit that most users can appreciate.
Google probably doesn’t worry about bandwidth costs. Only those of us who have to purchase bandwidth really care. Google doesn’t use another service provider; they are the service provider.
It doesn’t really matter if they’re not paying for bandwidth. The main point of this exercise is to show that using web standards will not increase file size, as some have argued.
What about real backward compatibility?
There’s still lot of bytes to be saved on the initial page request by extracting the CSS and JavaScript to external files. On top of that, there are lots of bytes to be saved by extracting the script event handle associations from the markup and into the JavaScript itself.
Should Google meditate on this? Of course, considering the fact, that even their mobile phone website, is not HTML valid.
Related Articles
