By now you ought to know that I love cycling and bikes. I’m also pretty keen on web design. So when a bike manufacturer I really like gets a new website, I’m excited.
Condor Cycles, the iconic London bike builder, race team and brand name, had a ‘coming soon’ holding page on its site for most of 2007 - for so long, in fact, that I almost got in touch to offer my services. But I just checked back, and they’ve relaunched!
Here are some of the things wrong with the site:
- Sloppy code: the visual elements of the site rely on Flash, and there’s no text content, or keyword or description metadata, so it’s no surprise the site doesn’t show up on the first page of Google for a search for ‘london bike shop’.
- Dodgy user interface: I know what they were trying to do with the ‘virtual catalogue’, but the Flash page turner tool is fiddly to use and doesn’t encourage browsing, even if there are additional buttons for ‘next page’ and ‘previous page’ on certain screens. What happens if I want to download an image of one of the bikes or email to a friend? I can’t.
- The ’store opening hours’ page opens in a new window. A minor point, arguably, but the issue that prompted this post. Here’s why you shouldn’t do this on a single domain - or indeed ever.
So why use Flash, really? Can it be easy for Condor staff to update details in their catalogue? No - there’s no product database feeding into the site. In 2009 when their new bikes are launched, they’ll have to start over.
What Condor needs, to do justice to their excellent store, solid reputation and superb bikes, is:
- A clear, accessible site designed in standards-compliant HTML and CSS, to boost its search engine rankings and improve navigability.
- A better catalogue system that displays pages to the browser transparently, with unique URLs per product, and which the store staff can update easily.