How to Evaluate Your Website in 30 Seconds

In my past presentations, I keep meaning to demonstrate a technique used by many developers to quickly evaluate the quality of a website in terms of development best practices, accessibility and search engine optimisation. Unfortunately, I keep cutting it out of my presentations as I can’t seem to squeeze it in within the time limits.

This technique is quick, easy and can be done by anyone. You don’t have to be a developer to understand or execute this simple test. If I need to evaluate a website for accessibility, web standards or SEO criteria, this is the first thing I will do before looking at any of the actual code.

What this test will tell you in under 30 seconds:
Does the website work with CSS off?
Does the website work with Javascript disabled?
is the website using tables for layout, instead of CSS?
is all essential information in the HTML?
is there extra code, non-essential information in the HTML?
is the site all Flash?
is there hidden content?
is image replacement being used?

The tools you will need

You need to download and install one of the development toolbars for the browser you are using. The following toolbars are available for each browser:

Internet Explorer:
Internet Explorer Developer Toolbar

Firefox:
Web Developer 1.1.3

Safari:
Safari utilises ‘bookmarklets’ or ‘favelets’ to toggle CSS and Javascript on/off. There is a list of some at Andy Budd’s bookmarklets page.

How to use each of these tools

Right, now you have downloaded your Developer Toolbar of choice and installed it on your favourite browser. Next, we have to find the right items to disable CSS or Javascript on your website. There are lots of options in each of these toolbars that make a developers life quite easy, but you just want to get straight to the CSS and Javascript bits.

Firefox, Web Developer Toolbar

Turn off CSS: (Keyboard Shortcut: Ctrl+Shift+S)
Firefox Toolbar: Turn CSS off

Turn off Javascript:
Firefox Toolbar: Turn Javascript off

One thing to remember with Firefox Web Developer Toolbar: If you want to check out multiple pages then you have to go to the ‘Options’ dropdown menu and make sure ‘Persist Styles’ is checked. This will mean that anything you apply in the Web Developer Toolbar will apply to multiple pages, rather than just the single page.

Firefox Toolbar: Persist Styles

Internet Explorer Developer Toolbar

Turn off CSS:
Internet Explorer Toolbar: Turn CSS off

Turn off Javascript:
Internet Explorer Toolbar: Turn Javascript off

One thing I do like about this toolbar is that the changes you make, like disabling Javascript on a website, will actually carry over to multiple pages until you decide to turn that feature back on. This is great for checking out a website more thoroughly

Safari

Turn off CSS:
Safari Bookmarklet: Turn CSS off

Turn off Javascript: I am not sure if you can do this right now in Safari as Bookmarklets need Javascript for them to actually work. But there must be a way! If anyone knows, then please throw a comment below and I will update this space.

What you should see when you turn off CSS
Content: Text only, with limited, content specific images that contribute to the content
Layout: The structure should change dramatically. If a layout hardly changes then you can be pretty sure it’s using a table layout
Semantics: Different size text headers, bulleted lists, blue underline links and a logical hierarchy to the content. This will suggest the document is using correct, semantic HTML
What you should see when you turn off Javascript
Content: If there is content missing (that needs javascript to display) then it is not being seen by screen readers or search engines
Functionality: Forms that still work, they should not rely on Javascript to populate or to send information back to the server
Graceful Degradation: Components should still break down gracefully. A menu should still work, a tabbed component should display all of it’s hidden content, just not as elegantly as it did with the Javascript turned on.

Right, have a go and see if this helps you. Next post I will do a bit of a case study to show sites that pass this test, as well as sites that fail.

Check out part two of this article: Case Studies - Evaluate Your Website in 30 Seconds.

Comments

Ben Buchanan says: May 15, 2007 @ 11:26 am

Alternatively you can use Opera without addons:
1) click View -> Style -> User Mode
2) F12 or right click for “quick preferences” and disable Javascript and plugins.

Voila.

User mode disables all CSS and optionally can be set to add the user’s own CSS. I actually have that button on my toolbar for easy access.

Standardzilla says: May 15, 2007 @ 11:58 am

@Ben - Thanks for that info. I started documenting the Opera sample but gave up as I figured anyone using Opera would most likely know how to do it themselves.

Plus I don’t use Opera and would have given the wrong info looking back now :-)

Jermayn Parker says: May 15, 2007 @ 12:46 pm

Mmmm good tips, I think this could be good to show clients the difference between your websites and others

Jermayn Parker says: May 15, 2007 @ 5:02 pm

Just an added comment.
Thanks for the IE developer tool as I have a problem that only shows up in IE6 so lets hope that this helps solves the problem…

Al says: May 17, 2007 @ 4:55 am

Good stuff - and you’ve invented a new protocol - ttps. typo in the link to the Web Developer 1.1.3.

Standardzilla says: May 17, 2007 @ 10:39 am

@Al- fixed, thanks.

Max Design - standards based web design, development and training » Some links for light reading (30/5/07) says: May 30, 2007 @ 8:21 am

[...] How to Evaluate Your Website in 30 Seconds [...]

Web Standards says: May 30, 2007 @ 8:58 am

I always do this on my designs, but to see it given a title, “How to Eveluate your website sin 30 seconds” - wow, cool!

Martin

Mike Cherim says: May 30, 2007 @ 9:06 am

I do something similar, also using the FF web-dev bar: JS on/off, images on/off, CSS on/off… and aside from testing other browsers in addition to these, I also do a run-though with Opera Voice.

I need practice though… this stuff takes me at least a minute ;-)

Ramonoodle says: May 30, 2007 @ 7:17 pm

It took me 35 seconds

Web Site Design, Internet Marketing, Ecommerce - ryanj - From the Web Developer’s Wiki - Accessibility says: June 9, 2007 @ 6:23 am

[...] How to Evaluate Your Website in 30 Seconds | Standardzilla [...]

Damien says: July 17, 2007 @ 11:15 pm

I actually use this all the time. Weird though, because when you do it, it does indeed only take about 30 seconds. Reading about it broken up in small steps makes it seem like something pretty complex.

» LinkSwitch – A Roundup of Great Links Across the Web says: August 19, 2007 @ 5:19 pm

[...] Standardzilla tells us how to Evaluate Our Websites in 30 Seconds. [...]

Como evaluar tu sitio web en 30 segundos says: August 20, 2007 @ 5:43 pm

[...] Standardzilla Posts Relacionados Crea tu primer Sitio Web en HTML y CSS¿Qué dice tu Sitio Web acerca de [...]

Damien McKenna says: August 22, 2007 @ 1:28 am

Out of interest, aside from IMHO the few nuts who disable JS (just like there’s a few nuts who refuse to upgrade past IE4 or Netscape4), why would testing for a lack of JS be important? Seriously.

Turk Hit Box says: November 12, 2007 @ 7:35 pm

I always use Firefox Web Developer Toolbar while designing. It makes my job alot easier.

sprungmarker » Blog Archive » Wie kann man eine Seite in 30 Sekunden evaluieren? - Standardzilla macht es vor :-) says: December 6, 2007 @ 7:56 am

[...] How to evaluate your website in 30 seconds skizziert Standardzilla, wie man für unterschiedliche Browser (Internet Explorer, Firefox, Safari) [...]