javascript BUILDING a tree is bad mkay?
Google can't parse it because the index doesn't exist until javascript creates it
Older computers capable of playing EQ have trouble with massive javascript buildlists such as this tree (My homebox specificaly - and I can't even LOOK at the crucible from work where I most often have some slack time to peruse)
The javascript list shouldn't be over 10kb including data(the actual links etc)
right now it's pushing 50kb total - that's huge.
Sure it looks nice, but it makes the crucible unusable and/or slow
Conversely - a properly done UL Menu loads <lightning> fast and is parseable by search engines so that your website shows in searches.
Now, I HATE people who whine and complain about something, but don't offer an alternative.
So I spent some time looking for and doing the legwork for an alternative
http://toxikoala.com/menu.html would achieve a similar result to the current javascript menu.
I'll keep digging a bit - perhaps I'll find a better, less clunky thing than the current tree menu that looks the same; Mea apropos, I don't mean to deride the site or the work - it's just current unusable from my point of view.