The changes in the game are different from the changes on the website.
The concerns are different. Whenever you make a change in the game itself, unrelated features from the point of view of the player could break, because I suppose they are coupled in code in a way they should not be. Have in mind the fact that the game is old and some parts of the code are poorly designed. Probably have dependencies they should not have and no one wants to change any of that. If it works, leave it like that.
From what I see, the team made significant progress. It pushed lots of changes and lots of features that worked rather well. That tells me that they have more experience. The code is decoupled. They probably have isolated logic in the newer parts of the code. Dealing with old code is always hard.
In order to do what I ask for, you need to change very little. Is nothing you can break,
unless you do something stupid and query the database 100 times/request to display items and skills. Considering that the data on website is not critical, they could just display the state it was few minutes ago and serve a cached version. Touch the database only if you have to and only if you do not have fresh data in cache. Database is the only thing that could impact the game. If something else will, then the company has serious problems. I expect it to have a reasonable design.
The website looks like it is put together by a backend dev. Is just not a frontend oriented company. That is fine. However, to display a grid that no one cares how it looks, just that it works, it is not such an absurd task. There are frameworks on the client created for people who do not want to hear about frontend. I hate those, but they do exist and are great. Try
ExtJS