From a comment by Peter in github: > By the way, one gross thing I noticed when rendering a BUNCH of report index > pages is that they're HUGE. The report index pages is 37.5% of all our web > traffic according to GA. Look at these HTML sizes: > > [03/May/2016 20:12:45] "GET /report/index/01744d86-81f3-42bc-b80a-cdb3a2160502 HTTP/1.0" 200 1572046 > [03/May/2016 20:12:50] "GET /report/index/1084944a-afa1-4585-af53-6a1d02160502 HTTP/1.0" 200 996511 > [03/May/2016 20:12:57] "GET /report/index/09f94427-97cc-432f-a0e5-7d2fd2160502 HTTP/1.0" 200 2417531 > [03/May/2016 20:13:05] "GET /report/index/068efd63-4a87-480c-a3af-63e842160502 HTTP/1.0" 200 3904766 I bet one of the reasons this page is so big is because it includes the entire json_dump. We could load that with AJAX whenever someone opens the tab instead.
It's not worth it. I started coding on a solution but it was just getting more and more complex for not so much value. Also, huge HTML shouldn't be a huge problem with gzip.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.