Show 72: Neverending Beta

On this week’s show: web stats meet usability testing, Apollo and why it is important, working with corporate colour palettes and how to sell your web design services.

Play

Download this show.

To subscribe directly within itunes click here

News and events

This week appears to be the week of never-ending betas however I have managed to squeeze in some pointless fun and an article about accessible content management systems:

Click2Map

There seems to be a growing number of tools out there that make the management of Google Maps easier. One that I have just discovered this week is Click2Map. You can easily and quickly add custom markers by entering an address (even if you are outside of the US). It is still in beta and needs a lot of work (for example you cannot integrate the maps directly into your site) but it is still great for a quick and easy way of linking to locations.

Popuri.us

Another “beta” service I spotted this week is Popuri.us. This site provides SEO reports on your site including rankings on Google, Yahoo, Alexa, Delicious and Technorati. Currently it seems to be suffering from some performance issues; nevertheless it gives a good indication of your online visibility. Of course if you are a Firefox user you may find the SEO add-on more convenient.

Finding an accessible CMS

One of the biggest complaints against content management systems is that they are often not very accessible. Gez Lemon has been kind enough to do an analysis of a whole bunch of them for us and provides a great article on the pros and cons of each from an accessibility point of view. If you are considering implementing a CMS and care about accessibility (which you should do) then check this out.

Arial vs Helvetica

So you think you know your typefaces? Maybe you are even a bit of a typography snob? But, can you tell the difference between Arial and Helvetica? Of course you can, at least that was what I thought until I actually tried.

Selling your web design services

So this week’s client corner is seriously lacking advice for clients (sorry about that). Instead Marcus takes a look at the subject of selling your web design services. Surprisingly for Marcus, he has written fairly comprehensive notes on what we covered so here you go…
You may build the best websites in the world but if you do not know how to sell your services then nobody will hire you. Web design, like nearly everything, is a competitive marketplace and simply being a good designer/developer is not enough. You also need a sales and marketing hat.
That said, it does seem that there is more work out there than agencies to do it.

Cold call?

Don’t buy databases of ‘quality’ contacts in a particular sector. I may be cynical but I reckon the vast majority of these ‘leads’ were tricked into supplying their details. You’re trying to sell solutions to your potential clients’ online problems not pallets of dog food. I my experience, cold calling is a waste of time and effort – the only way you’ll win work is if you’re lucky enough to call someone when they’re about to release a tender.
The only exception to this rule are local businesses where picking up the phone and saying ‘hi, we’re just over the road from you and we’re really good at what we do. If you ever need the services that we provide please do include us in any suppler selection process you intend to go through’. If they’re friendly why not meet up for a beer (see Love Your Clients)…

Focus on a specific market sector

If your only case study is a sewage works site then go after other sewage works sites first. This is common sense: you have a proven ability to produce a website with probably very similar features to the one the other sewage site wants. You have a real, live working example to show them and a client who will (hopefully) say nice things about you.

Tender sites

I get asked about these a lot. They are (I think) better than straight cold calling but not much. Golden rule – don’t do any speculative design work as some may be a scam. I think most of these are simply there because a lot of tenders are required to be competitive but the client already has a preferred agency.  I have generated a ‘nose’ for when we are making up numbers so, if you get that feeling, be brave, walk away…
Of course, try to talk (and I mean talk not email) to the client. Be bold, ask questions about how many others are going for the project, what is the budget (we need to know to be able to provide the most appropriate solution), are the deadlines set in stone etc etc etc… If you’re getting negative feelings… guess what… walk away…
If you do decide to go for something off one of these sites, I recommend the following as a response:

  1. boiler plate ‘Why Us’. You should already have this in another proposal. Up to 10 pages of skills, experience, examples of design work and above all USP.
  2. No more than 2 sides of A4 of ‘your solution’ i.e. a summary.
  3. Tasks by task breakdown of price (inc. payment terms with at least a third up front (‘on delivery’ if you’re really worried about the client!)

The trick here is to start at the bottom. Do the task breakdown first (it may put you way over budget if you know it – if so, walk away) which will lead to an obvious solution summary then tack the ‘aren’t we great’ on the front.
The idea is to put as little effort in as possible without making it look that way.
Much better idea to…

Market, market, market!

There are so many ways to market yourself. For example, you can drive round your local neighbourhood shouting through a loud hailer if you like! Headscape’s marketing effort is focussed virtually solely on Boagworld now. The point is, try to find something that you can do that you feel passionate about and will get people either ringing you directly or, just as good, recommending you to others.

Know when to walk away

It is the hardest thing in the world to do, but it is important that you know when to turn down work. There are times when the clients requirements are unrealistic or the job is simply too big. On other occasions, the chance of winning a job does not justify the investment involved in pitching for it. There is a natural tendency to want to run after every piece of work, but sometimes you just have to say no.
I got the impression listening at SXSW that the agencies I most admire (e.g. Happy Cog) simply wait around for projects that they are interested in and the clients should be damn grateful! Or maybe that was the impression that Mr Z wanted to convey.

Ask an expert: Aral on Apollo

Aral Balkan is one of my favourite speakers and this week in the “ask an expert” section he puts his enthusiasm and humour into an insightful introduction of Apollo. Apollo is a new development platform from Adobe that allows web designers to start developing desktop applications.

Working with corporate colours

This week’s agony uncle question is based on something I found in the boagworld forum. Pecko asked whether we should use Photoshop to convert corporate colours for the web or whether we should do it by hand. A lot of the people on the forum argued that you should allow Photoshop to take the strain but in the show I argue that we should do it by hand. My argument was based on something I had read before and yet I couldn’t for the life of me remember where I had read it. I eventually found it was from a brilliant article by Jason Santa Maria on 24 Ways. I hope he will forgive me for not crediting him on the show.

Review: ClickTale

I was recently asked to beta test ClickTale, a new statistics-tracking tool. Not only does it provide you with all of the basic web stats you would expect, it also allows you to watch recordings of how users interact with your site. You can see their cursor move around the screen, watch them scroll and even move between pages. The product is currently in closed beta but it is definitely worth keeping an eye on because it is extremely powerful and acts as a passable alternative when usability testing is just not an option.

Show 65: Dying (Man Flu!)

This week on the Boagworld Podcast, Paul and Marcus drag themselves from their death beds to share why you should care about Vista and Drew McLellan explains the pros and cons of Ruby on Rails.

Play

This week on the Boagworld Podcast, Paul and Marcus drag themselves from their death beds to share why you should care about Vista, which browsers you should support and introduce you to the exciting world of terms and conditions. Oh yes and Drew McLellan explains the pros and cons of Ruby on Rails.

Download this show.

To subscribe directly within itunes click here

News and events

Barcamp

The weekend of the 17th of February sees the second barcamp to take place in London. If you haven’t come across barcamp, it is a gathering of web geeks where everybody takes turns to present a 30 minute session. You can pick which sessions you wish to attend and the whole thing has a very informal feel. Its free and arguably one of the most valuable meetups of the year.

Paper prototyping

There is an excellent new article on the List Apart website. It proposes closing down your PC and returning to good old pen and paper. Compelling stuff, which should make you evaluate the way you develop your designs.

Bulletproof AJAX

Jeremy Keith is about to release the follow up to DOM Scripting, Bulletproof AJAX. As with his previous book Bulletproof AJAX is aimed squarely at the designer community. It will be perfect for people who have read DOM Scripting and want to take the next step. If you can’t wait that long and can squeeze £295 out of your boss then you might want to attend Jeremy’s AJAX workshop down in Brighton. I have attended it myself and it is extremely good.

Custom reading containers

This is an incredible proof of concept that I was emailed last week. Basically it enables the user to resize elements of your web page to suit their requirements. Admittedly it has only undergone limited testing so far and relies on PHP; nevertheless it looks very interesting indeed.

Client corner: Terms and conditions

This week Marcus starts a new series on client contrasts with a “fascinating” look at terms and conditions… I know… control your excitement! Some of the points he covers include:

  • Make sure you read the T&Cs carefully no matter how boring they are!
  • Get advice if you don’t understand something
  • Make sure you note the governing laws that cover the T&Cs
  • Note the deliverables and rights
  • Understand your liability if there are problems

Agony Uncle: Browser support

Danny has sent in an excellent question about how far we should go in supporting the numerous browsers out there. Should we support IE5, Opera mobile, Opera on the Wii and so on? In the show I talk about the need to not set hard and fast rules in this area but adapt to the individual requirements of our clients. I talk about not blindly accepting the browser support requested by the client but rather analysing statistics to establish the best browser set to build for. Finally I also explain the concept of graded browser support as implemented by larger organisations like Yahoo!

Ask the expert: Ruby on Rails

Talking of Yahoo, this week our expert is Drew McLellan who works in their development team. He is on the show discussing the pros and cons of working with frameworks like Ruby on Rails.  Among other things he looks at speed of development vs. maintenance and generally gives a nice overview on the subject. He certainly helped me have a clearer understanding of the benefits and drawbacks.

Review: Vista

So Vista has hit the shelves and being the uber geek that I am I couldn’t resist upgrading as soon as I got my hands on the disk. I know there are loads of reviews on Vista but I thought it was worth reviewing specifically from a web designer’s perspective. I talk about the problems I had installing Photoshop, the improved FTP support and the multiple website support now in IIS. I also look at how Vista could potentially change the way people interact with the web by bringing things like desktop widgets and RSS feeds to the masses.

Podcast 21: Working with web stats

Are you getting the most from your web stats? Are they helping you identify areas on your site that require improvement? Marcus and Paul look at how web stats can keep you informed about how users interact with your site.

Play

Download this show.

To subscribe directly within itunes click hereSuccess criteria

Examining the log files stored by your web server can be an incredibly enlightening process if you know what you are looking for. Not only can web statistics show you information about your users (such as their geographical location, their browser, operating system etc) but it can also highlight gaps in your content and usability problems on your site.

In this podcast, we take a closer look at the kind of information available through your web stats and how this information can shape the development of your site.

Web resource review: stats packages

In this weeks show Paul also reviews two great stats package that provide very different services.

Clicktracks

Clicktracks is an excellent stats package for those who struggle with graphs and pie charts. Instead of the normal pages of statistical information, this application comes with an integrated web browser. This allows you to surf the site while seeing web stats overlaying each page. This approach gives you a real understanding of how users have moved around your site and it is even possible to tag users and follow the route they took from page to page. Although an excellent usability tool the associated price tag is not cheap, making this only a viable solution for corporate environments.

Read my full review of clicktracks

Visit the clicktracks site

Google Analytics

For those of you on a budget or more comfortable with statistical information, we recommend you check out Google Analytics. This free service from Google provides a wealth of information about your visitors and how they interact with your site. What is more it provides some excellent campaign tracking for those who run online ad campaigns.

Visit the Google Analytics site

Technobuster: AJAX

AJAX is a term often thrown around these days and often with little in the way of explanation. In this weeks podcast Paul and Marcus unpack the term AJAX, explaining what it means and what benefits it brings. However, they also offer some words of warning about the best way to implement it.

Web Design Podcast (14) – Real World Web 2.0

In this episode of the boagworld podcast, Marcus Lillington and I try to take the characteristics of Web 2.0 and apply them to real world websites.

Play

Download this show.

Over the past few weeks, I have written a lot about Web 2.0 on boagworld.com. However, most of what I have written consists of questions rather than answers. In this episode of the boagworld podcast, Marcus Lillington and I try to take the characteristics of Web 2.0 and apply them to real world websites.

One of my greatest concerns with Web 2.0 is that it seems to have been adopted by only a handful of largely technical consumer websites. Few of these sites seem to have a traditional business plan and so bare little resemblance to the average organisation’s website. In this podcast, we look at what Web 2.0 actually is and how those underlying characteristics apply to the mainstream websites we all work with on a daily basis.

A lot of this podcast is based on Andy Budd’s presentation at the d.construct Web 2.0 conference here in the UK. Andy did an excellent job at defining Web 2.0 and explaining why perhaps the buzzword does have its place. What we do in this podcast is look at what can be learnt from this new generation of websites and moved across into the mainstream.

More on Web 2.0

Listen to the Podcast of Andy Budd’s presentation

Where’s the money?

d.construct and Web 2.0

Web applications

Boagworld.com news

Boagworld.com is proud to be included on the 9Rules Network

Check out the Boagworld.com “web design” search mentioned in the podcast

Check out Google’s new website statistics service – Google Analytics

Card sorting

I am currently involved in some usability consultancy for an intranet that is going through a major redesign. One of the tools we will use to decide on the sites new information architecture is card sorting.

At its core card sorting is probably one of the simplest, and yet most powerful ways of improving a site’s information architecture. It is valuable because it gives an insight into the users mental approach demonstrating how they sort and structure information within their own heads.

How to do card sorting

Simply label 20-30 index cards with headings from the various sections, subsections and pages of your website. Depending on the complexity of the site, you might also wish to include a brief description. It is also useful to number the cards so that you can more easily analyse the results of your test later.

Untitled cards

It is also possible to start with no predefined headings but rather allow the user to specify their own section titles. Although this approach initially sounds good because it introduces no bias from the tester, the reality is that it can often be incredibly challenging to the user and so progress is often slow. Often it is better to have existing titles but encourage the user to comment on or change titles if they perceive it as appropriate.

Obviously, 20-30 cards will probably involve some considerable editing on your part but more cards than this can overwhelm the user you are testing. If it is necessary to cover more ground than this, it is possible to have some organisation already in place so that users are responding to an existing information architecture rather than starting from scratch.

Testing normally involves approximately 15 users and requires them to sort the stack of cards into piles that make sense to them. Often you also ask users to name these piles and this label is written on a post-it note that is then attached to the pile.

Card sorting approaches

Beyond this basic approach there are numerous ways you can structure a session however basically this breaks down into two approaches; quantitative or qualitative.

Quantitative

The quantitative approach uses card sorting as a data collection tool and is largely orientated around producing measurable statistics against which to judge. For example, it might establish that 83% of people placed the “contact us” section under “about us”.

Qualitative

Although the quantitative approach is perfectly valid, it is easy to prejudice the results and does not particularly help to understand the users’ reasons for the ordering. Personally, I believe more is to be learnt from the qualitative approach. Qualitative testing is a much more interactive and less observational allowing you as the tester to question the user and dig into some of the specifics of how they organise the deck. The aim is to encourage the user to articulate their thoughts and frustrations so you can understand their underlining approach.

What are your thoughts?

It is pretty obvious from this entry that I see a lot of potential in card sorting, but what is your opinion? Have you tried card sorting? Was it valuable? What works for you and what doesn’t? Do you take a quantitative or qualitative approach? I would love to hear your thought!

Fearing the fold

Its funny how challenging one preconception can leave you totally inspired. I am in the process of reading a book called CSS Zen Garden by Molly Holzschlag and David Shea based on David’s superb site. While reading the book and browsing the associated site I couldn’t help noticing that many of the designs were incredibly long and had little in the way of valuable content above the fold.

The preconception

Now somewhere along the line I had got it into my head that any content of value had to be kept above the fold (so users could see it without scrolling) when running at 800 by 600. In effect this mean ‘t almost all of your content had to be crammed into an area approximately 770 pixels by 430 pixels. This doesn’t leave a lot of room for decorative elements, let alone white space. As a result my designs often looked overly busy.

The usability question

Now just because another designer chooses to ignore a principle like keeping content above the fold doesn’t necessarily make it right. If that was the case then we would all still be using mystery meat navigation! But it did start me thinking about whether the principle still held true.

With that in mind I did a little research and came across this interesting article from Jakob Nielsen the well known usability "guru". He said:

In more recent studies, we have seen that most users scroll when they visit a long home page or a long navigation screen. This change in behaviour is probably due to users getting more experience with scrolling Web pages.

Although he goes on to say that it is still good practice to keep navigation above the fold he does add:

…scrolling is no longer a usability disaster for navigation pages. Scrolling still reduces usability, but all design involves trade-offs, and the argument against scrolling is no longer as strong as it used to be .

What is more this report was written back in 1997 so there is no reason to believe that users have not become even more comfortable with the idea of scrolling in order to find content.

Where is the fold?

Obviously the other question here is, was I right in my assumption that I only had approximately 430 pixels of height to work with above the fold. This number is dictated by three factors:

  • The browser the user is working with
  • The screen resolution they are running at
  • Any additional toolbars they might be using as part of their operating system

To be honest it is hard to predict the first and last of those factors however there are some good statistics on screen resolution. I looked at several sources of statistics but probably the most representative was those found at thecounter.com as this site has stats on the widest range of users. As of May 2005 their stats showed the following trend:

  • 56% of users running at 1024×768
  • 28% of users running at 800×600
  • 8% of users running at 1280×1024

Another site stated:

The current trend is that more and more computers are using a screen size of 1024×768 pixels

Conclusions

It is apparent that the prevailing trend is towards 1024×768 but 28% of people still running at 800×600 cannot be ignored. However I do believe that the shift is significant enough to warrant some more flexibility in design. Combined with Jakob Neilsen’s testing on scrolling I believe it is fair to conclude that as long as users running at 800×600 don’t have to scroll sideward (in other words the width of your site doesn’t exceed approximately 770 pixels) then we can safely expect them to scroll vertically for content.

Web Accessibility Report Published

As part of my work with Headscape I have released a report which surveys the accessibility of University and further education web sites. I am pleased to say that it has received a lot of publicity which is good news but I hope that people don’t see it as condemning.

The media love dramatic headlines. "39% of University homepages break the law" sounds a lot better than "Slight concerns over University web sites". Of course life is never as black and white or as melodramatic as that. At least not in the world of web design.

What the report says

Our report surveyed 156 UK university web sites and 255 UK colleges of further/higher education. Out of those 39% of Universities and 54% of colleges failed to meet WAI accessibility guidelines. Whether or not this means they are breaking the law is yet to be seen. There is yet to be a test case in British law to see if inaccessible web sites are breaking the Disability Discrimination Act. However based on a test case against the Olympic committee in Australia (which shares many similiarities with our system of law) the chances are they would be.

Condeming?

Although we do list the sites that pass or fail the accessibility test in the report, this is not with a desire to "name and shame". Ensuring that your web site is accessible can be an overwhelming tasks especially when a large number of users are contributing to your site. It is relatively easy to make a site Single A complient but keeping it that way is another matter.

The accessibility guidelines that all publically funded web sites are meant to comply with can be intimidating to say the least. Without clear guidence of how best to approach these problems each University or college is left to work it out for themselves.

Also retrofitting an existing site that many consist of thousands of pages is not always straightforward and many education institutions simply do not have the resources to do it.

I have worked with many such organisations and know what a tough challenge this can be sometimes. Take for example the University of Portsmouth web site. We designed and delivered complient templates that were to be integrated into a content management system. However their site now fail to reach even the most basic level of accessibility and appear in our report. Is this because they don’t care about accessibility? Not at all, it is simply because accessibility is a challenging area that can often overtake us if we are not careful.

Read more about accessibility and the Higher/Further Education sector

Top usability mistakes

I read an interesting article today which outlined some of the top usability mistakes made by major web sites. Here’s your chance to learn from their mistakes.

Here is a summary of the major usability blunders found on leading web sites:

No search function

It is amazing that there are major web sites out there that still don’t have a search function. A usability study by Jakob Nielsen found that more than half of all users will head straight for the search function on a web site. If you have a site that has more than, lets say, 100 pages you should be looking to add search functionality.

Massive download times

Many web designer are using the increase in broadband as an excuse for poorly built web pages. However broadband usage only stands at 27%so it is important not to alienate the other 73%. There is no reason why an average web page should take more than 10-15 seconds to load. Improvements in image compression and the cleaner code produced by web standards should significantly improve download time.

Find out just how quickly your site downloads.

Non-scannable Text

People read very differently online to how they read printed material. They tend to scan web pages rather than read word-for-word. It is therefore important to provide visual elements in order to aid scanning.

Read more about this subject

Unclear linking

Probably one of the first question somebody asks when arriving at a new web page is "where can I go next?". It is important to make it clear what the user can click on. Make sure links are obvious whether textual or image based. Never leave the user guessing what is a link and what isn’t.

Poor 404 error page

As I have just covered this in a recent article so I won’t dwell on it in any great detail. However I will say that providing a helpful error page when things go wrong is an invaluable usability aid.

Visited links not show

I have to confess it is only recently that I have come to understand the importance of this myself after reading another article by Jakob Nielsen. Users often find themselves lost within a site when it isn’t clearly marked which pages they have already visited. By simply changing the visual appearance of visited links the user has a much clearer idea of where they have been in the site and avoids going round and round in circles.

The use of frames

This could really be an article in itself. There are numerous problems with frames but some of the most significant usability ones are:

  • Pages can be unprintable
  • Pages can’t be bookmarked, nor their URLs emailed
  • The back, refresh and history buttons can become disabled
  • Visited links across frames don’t change colour

Important information contained in images

In order to have greater control over the appearance of text web designers often use images instead of dynamic text. However this creates usability and accessibility problems. Images take longer to download so those of us with slow connections have to wait for important information to appear. Those using older browsers or screen readers may find that information contained in images becomes totally inaccessible to them.

Unlike some, I am not proposing that you do not use graphical text. However I am proposing that all images should haveALT tags so the user can access that information while the page is loading.

Breaking with conventions

In my article entitled "why all web sites should look the same" I explain why web designers shouldn’t go against conventions. Users expect to find the logo in the top left. They expect to find navigation either across the top or down the left hand side. The web is incredibly confusing anyway, with every site having its own user interface. The last thing a web designer should do is add to that confusion.

Are Macs that important!?

Recently we had a client come back to us with some concerns over the fact that their site didn’t display properly on a Mac. Although we obviously fixed the problem it did make me wonder whether we have our priorities right.

The issue of Mac’s comes up again and again for me as a web designer. Clients always seem remarkably concerned that their web site looks great on a Mac. This is often because their advertising agency has made some comment that the site doesn’t look perfect on their system. In my experience this is often more to do with the fact that the advertising agency didn’t win the web design contract than a sincere desire to see the web site project the brand in the best light.

It’s a numbers game

But should Mac’s really be considered that important. Let’s put this in perspective. 2% of visitors are using the Mac operating system. Although significant this is remarkably low when you compare it to the 5% that cannot use Javascript!

Confused priorities

The same clients who are so concerned about making their site look great on a Mac are also demanding Javascript reliant functions such as pop up windows, dynamic HTML menus and Javascript driven shopping carts.

Accessibility for all

I am not suggesting we should ignore the Mac operating system. What I am saying is that we need to concentrate as much (if not more) of our efforts on ensuring our web sites are accessible to larger groups such as those without Javascript. Web sites should be accessible to all not just the vocal minority.

Product review – ClickTracks

Do you have trouble understanding the statistics on your website’s traffic? If so then ClickTracks could be for you.

The problem with website statistic packages

I don’t know about you but I am a visual person. If I am trying to understand a new concept I grasp it quicker if I can actually see it in action or at least see a diagram of how it works. Perhaps that is why I used to find website statistics so hard to get my head around. I found it hard to get any real value from all of those columns of statistics. Sure they are great if all you want to know is how many people viewed your site yesterday or what percentage of people use internet explorer. However I always found it hard to get a feel of how my visitors were moving around the site and where they were encountering problems.

A different approach

Clicktracks takes a different approach and one that is superb if you want to really understand how users interact with your site. Sure it provides all of the normal statistical reporting allowing you to bring back information such as; most common entry page, most common exit page, number of visitors per day etc. It even allows you to generate reports that focus on specific user groups such as pay-per-click customers or those that stayed at the site over 30 seconds. However what really sets Clicktracks apart is the ability to overlay powerful statistical reporting on top of your website. In other words you can actually browse your website and see who clicked on what and when. It is even possible to follow individual users through the site and see exactly what pages they hit and in what order. Still confused? Then take a few moment to watch the demonstration available from their homepage . It really helps to explain the potential of this application. Visit the ClickTracks website now

The Benefits

The benefits of this approach our obvious. It allows you to gather huge amounts of usability information without running usability test sessions. Although weblogs are never going to replace test sessions Clicktracks does give detailed information about visitors surfing habits. ClickTracks gives you the ability to really get under the skin of your users. For example it is possible to isolate the users that have completed your call to action (whether that is buying a product or completing a contact us form) and analysis how they came to that point. How did they enter the site? What pages did they view? How long did it take them between arriving and completing the call to action? It also allows you to do the reverse with users that fail to complete your call to action. Why did a user abandon their shopping cart? ClickTracks would allow you to discover for example that many people abandoned their carts after visiting the delivery information page. That might tell you that your postage is too expensive or it takes too long to deliver. You can also track users that arrived after searching for a specific keyword. How long did it take them to find the page on your site that specifically relates to that keyword? Did they go to other pages that were not relevant first? I am sure you get the idea.

Conclusions

Although this kind of tracking is available through most statistics packages Clicktracks makes it available in a much more intuitive fashion without loosing any of the flexibility or power of more traditional software. Combine this with the lightning processing of even large sets of weblogs and you really do have a winning package. To see for yourself just how powerful Clicktracks can be click here and download a demonstration version.