Web Blunders: The Top 5 Biggest Mistakes On The Web

At TechEd this year, I presented a session where I presented my top five pet peeves on the web, the biggest and easiest problems to avoid on the web.  With how easy it is to share content on the web, I felt that these top five things were the best and easiest to get rid of.

In order, I felt they were:

5.  Unprofessional Site Design
4.  Lousy Content
3.  Poorly coded HTML/CSS/JavaScript
2.  Inappropriate use of Rich Content
1.  Not Being POSH

I've attached my slides below, so check them out, and let me know what your pet peeves are! 

TechEd - Web Blunders.pptx

Comments (5)

  1. thacker says:

    My personal list of things that agitate me regarding the Web?

    1. The current prevailing belief that 95% of the Web is broken, that it needs fixed and the omnipotent attitude that such a thing can be done, even if the need existed.

    Your referenced objections, I have no problems within the 95% of the Web content that is basically "hobby"content.

    2. Failure of the entire Internet Communication chain to coordinate and take an aggressive pro-active approach to security.

    3. Failure of the remaining 5% of the Web content, the bulk of the Web traffic, to meet Accessibility.  This includes the belief that "508 Standards" are good enough.

    4. Application developers who make claims that their product  can be used to create accessible content when in fact, it, invariably, misses the attention to basics and detail that is needed to accomplish the same.

    5. Smoke blowing.  Get the basics met before discussions or implementation of the "circus acts".

  2. slager says:

    6. posting files that can only be opened in the very latest powerpoint or first requiring an update of the installed one

  3. Joe Clark says:

    0. Publishing screeds about Web development in “attachments” in Microsoft-owned formats

  4. k says:

    1. "Unprofessional site desing" — what does this mean?  Visual design?  Information architecture?  Usability & accessibility?  This is like saying "The #1 problem with cars is poor-quality cars."  I could argue a few things on this site violate these ideas.  No CSS styles for visited links?  Thanks for breaking a useful feature that’s  already built into browsers.

    4.  Lousy Content

    3.  Poorly coded HTML/CSS/JavaScript — Your XHTML doesn’t validate (31 errors, including not even having a character encoding), your CSS doesn’t validate, and you have some of the crappiest .NET generated Javascript I’ve ever seen.  Take this gem:

    javascript:WebForm_DoPostBackWithOptions(new WebForm_PostBackOptions("ctl00$_$ctl00$_$ctl01$_$form$_$btnSubmit", "", true, "", "", false, false))

    Or how about this for a "semantic" element ID:


    2.  Inappropriate use of Rich Content — Not applicable currently on your site (from what I can see), but I’m sure you’ll give up lots of "awesome" Silverlight demos.

    1.  Not Being POSH — Nice use of a buzzword.  Agein, take a look under the hood of your site…

    All the MSDN bloggers pretty much make me lose hope in Microsoft ever "getting" the web.

  5. Dflying Chen says:


Skip to main content