Weird bug, probably local, a friend of mine and myself had this bug. It did load for me after a while though. The data was reported correctly in the Zermelo client, so this can be a zermelo.js bug or a zermelo-binding bug.