Usability Review - webuyanycar.com

Overall, I genuinely think that usability in websites and web applications is improving.  But every now and then I stumble across a site that completely bucks the trend and manages to provide a truly shocking user experience.  One that ensures that I, and many others, will never use their service.  Today was one of those days.

I heard a radio advert for a new service called webuyanycar.com.  The theory is that they will buy your car from you direct, to save you going through the hassle of advertising and sorting out a private sale.  So, being curious as to how a service like this would actually work, I checked them out.  Now I wished I hadn’t.  Quite simply, it’s one of the least usable sites I’ve ever come across.  Poor layout, badly worded copy, buggy forms, unclear graphics, this site has it all!

So taking it step by step, let’s see where they go wrong.  Firstly, you have to enter the registration number of your car.  Once you’ve done this you get presented with a drop-down box where you select the year.  The button next to this field is labelled “VALUE MY CAR”.  This is misleading as there are a number of steps required before you actually get the value of your car (which, by the way, was at least 30% lower than current realistic market value).  When creating a multi-page or multi-step process, it’s key to keep users informed as to how far they are through the process.  Suggesting it’s near to the end, and then not fulfilling that expectation results is a high number of abortions mid-process.

The next step in the process is identifying any damage on the car.  This is done through a flash object (as pointed out in the comments, this isn’t a Flash object, it’s actually Javascript mixed with image maps).  I defy anyone to look at the Damage Assessment Tool’s interface they have chosen and tell me which end is the front of the car.  In fact, I believed that the right hand side was the front because of the shape of the headlights.  This isn’t the case.  There are tool tips when you hover over the section but these are badly formatted and buggy.  All in all, if you have to record any damage, it’s an absolute chore and very hit and miss.

Once you’ve added any damage, you then get to the screen which requires your personal details.  I’ve added a screenshot of this screen to the right, just so you can see what it looks like in FireFox 3.  Note that FireFox 3 is currently in the “Release Candidate” stage, meaning that it’s not entirely ready for mass consumption (although once a software project reaches release candidate stage, typically only defect fixes are included and features are not changed).  FireFox is the world’s second most popular browser, used by about 25% of Brits.  As you can see, it’s horribly broken.  To make matter worse, even if you can figure out what fields require what information, you get random validation failure messages (for no apparent reason) that don’t seem to be attributed to a specific field (because the layout is too broken to figure out where they are supposed to be positioned).  And as the icing on top of the cake, the submit button doesn’t appear to work in FireFox.  So even after battling through badly designed and horrendously implemented forms, you can’t get a valuation in the end anyway.

One other oddity you’ll find regards the privacy policy.  As with most websites that require personal information, they will try and sell it unless you tell them not to.  Yet look at the wording for the option.  This was obviously written by someone who either doesn’t understand the fundamentals of web form design, and what the different input types do, or doesn’t understand basic English.  But most likely both.  The first thing you’ll notice is that it says “Click Here”.  “Click Here” is appalling when used as the text for a link, it’s an abomination when used as part of a form.  You’ll also notice the ambiguity is introduces.  If I click there, I’ll deselect the check box.  Usually these are opt-meaning I would want the check box checked.  And what if I click there, forget, and then click there again?  No doubt my details would be winging their way to all and sundry before I know it.  Quite why they can’t just clearly state whether that element of the form needs to be selected or unselected in order to achieve the desired result is beyond me.

This truly is one of the trend bucking sites I touched on in the introduction.  Considering this is primarily a web based business, launching with such a clearly under-designed, incompetent, not-fit-for-purpose website could be a huge mistake.  if they can’t handle something as simple as a web form, how on earth am I supposed to trust them to buy a car off me?  Not a chance.  One of the worst user experiences I’ve had in a long time.

Tags: , , , ,

2 Responses to “Usability Review - webuyanycar.com”

  1. Jeremy Herbert Says:

    Simon, firstly I’d like to thank you for your interest in webuyanycar.com and for pointing out some areas of the website where you felt usability was below par. You have made some useful comments which we are genuinely taking on board and we will be reviewing some of the page styling on this basis.

    There are however some technical inaccuracies within your review which I would like to address specifically:

    Firstly, you describe Firefox 3 as “the world’s second most popular browser used by about 25% of Brits”. In fact at the time of writing, Firefox 2 is the standard offering from Mozilla and is used by 13.47% of our visitors. Firefox 3 is around the corner and the CSS styling issues you described will be addressed quickly, but the software is still at release candidate stage and as such, less than 0.3% of the visitors to our website are using this software

    Secondly, you talk about our damage assessment tool being a Flash object. This is wholly inaccurate although again, your comments on usability are very welcome.

    My biggest concern is that you have based your review having viewed the site on pre-production software, i.e. Firefox 3 which has presented an unfair view of the website. Notwithstanding, we appreciate your critique of the site and will be working to improve some of the areas commented upon.

    Your crusade to highlight the highs and lows of usability has great merits and I look forward to seeing some examples of good design in the near future featured on your blog. I’d also invite you to contact me directly so that we can discuss your review and work through the comments. Once we’ve had a chance to talk and to put some changes in place, I’m sure you’ll be happy to produce a revised critique based on current browser standards.

  2. simon Says:

    Thanks for taking the time to comment Jeremy, I appreciate it. You’re right about my use of a pre-production browser in FireFox 3. I should ahve clarified that FireFox as a whole represents about 25% of the UK browser market (although accurately reporting the usage of each browser is difficult. Across the sites I run and am involved in, FireFox usage is closer to 50% whilst I’ve seen other sites reporting it being as low as 10%). My intention was to state that I’m using FireFox 3 (and therefore any comments on layout/issues that may be affected by the browser, should be taken at face value. I’ll update the article shortly to make this clear.

    I’m sure you’re also right about your damage assessment tool not being Flash. However, the issues I pointed out with it stand, regardless of the technology used to implement it.

    Once again, thanks for commenting. I haven’t “launched” this blog yet (hence moving-in look and lack of content), more just made it available, so be sure to let me know of any changes you make and I’ll be more than happy to take a second look.

Leave a Reply