Show Posts
Hi Solipsis,
Thanks for the suggestion. I've looked at the code you mentioned and see that it is indeed full of documentation and comments. You state that it's 1/10th of my initial page load. Do you mean just in terms of sheer bytes being sent over the wire? Is the implication you're making that I'll have better performance if I strip out the majority of the comments/documentation from that file?
LOL... no worries about snooping the source - it's available on github. I used standard MPOS/NOMP. I added a few tweaks and fixes on my end to address some of the known issues in them, but otherwise it's pretty much stock.
Thanks for the suggestion. I've looked at the code you mentioned and see that it is indeed full of documentation and comments. You state that it's 1/10th of my initial page load. Do you mean just in terms of sheer bytes being sent over the wire? Is the implication you're making that I'll have better performance if I strip out the majority of the comments/documentation from that file?
LOL... no worries about snooping the source - it's available on github. I used standard MPOS/NOMP. I added a few tweaks and fixes on my end to address some of the known issues in them, but otherwise it's pretty much stock.
Yes, I did mean in terms of sheer bytes being sent. The initial page load is about 1019 KB and 100 KB of that is "jquery.dataTables.js". Sometimes I forget how much I use slang terms. "Minifying" JavaScript is using a program similar to a compiler which automatically removes documentation and changes up things to make it more efficient in terms of raw size. (C.F., "jquery.dataTables.js" and "jquery-2.13.min.js"). I did some looking and the developers of DataTables already publish a minified version here: https://cdn.datatables.net/1.10.10/js/jquery.dataTables.min.js Using a minified version, would help with bandwidth and also somewhat performance. It should be a simple drop-in replacement.
