In your case, it is just a blank white page. Since you are asking for suggestions, I would suggest you just make it display a message. One for suggesting users with older browsers to download chrome or firefox and another message directed at those with Javascript intentionally disabled which gives a very brief outline of what your app does and why they should enable JS to play with it.

e: I clicked through to the other mashups you have created which you linked in your other comment. They all do the same thing, just bring me to a blank page.

ee: To those down-voting, what do you disagree with? Do you not think pure JS web apps should have HTML fallback pages or do you disagree with the way I said it?

http://www.quora.com/What-percentage-of-Internet-users-use-J...

It can also occur due to network problems on occasion or other technical issues; if you have JS beyond just progressive enhancement on your site you really ought to have a <noscript> tag in there somewhere.

Plus as mentioned, it isn't like it takes much effort, a noscript tag and a paragraph saying that it is a pure JS web app/what it does is enough.

I don't think non-JS/HTML fallback pages are worth it for a minimal viable product.