Livetable doc_location produce much bigger JSON than it should

It does not make any sense to continue sending such a huge duplicated html peace of code as data... For example I'm currently looking in Yourkit at a single 22MB JSON String copy/pasted several times in the server (and client) memory plus the map before being serialized: you get a request threadlocal of 115MB in total (standard user directory livetable this time).

Just imagine the same thing for livetable viewed by many people.