THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
You should also search wicket-user mailing list for performance and scalability or simply use performance-scalability-tipsas your starting point.
Wicket.replaceOuterHtml gives weird result on Firefox
There are certain cases when you replace markup in FireFox where some of the nodes are not placed right in the DOM tree. This happens when the markup is invalid, e.g. you have somewhere a block element inside an inline element, such as <table> or <div> in <span>.