xDragonZ Posted June 4, 2011 Share Posted June 4, 2011 Why cant IPB provide IPB HTML Minify ? (there are only JS and CCS minify right now) When you press Ctrl + U you can see that IPB forum html have many white spaces ... if there are option to enable HTML Minify this will save some page loading time too. Link to comment Share on other sites More sharing options...
Michael Posted June 4, 2011 Share Posted June 4, 2011 IP.Board uses gzip encoding to mitigate that. Bfarber gave a post once with a nice description on how this works, but the search stuff is till a little borked here so I can't locate it at the moment. Even eliminating all of that white space, though, is not going to make a noticeable difference in the page loading times. Link to comment Share on other sites More sharing options...
.Ian Posted June 4, 2011 Share Posted June 4, 2011 Does it really make any difference? There is an option in the ACP to remove the white spaces, I am sure. Link to comment Share on other sites More sharing options...
xDragonZ Posted June 4, 2011 Author Share Posted June 4, 2011 @Michael : Thanks for you reply ^^ Hope IPB will add CDN function in IPB 3.2 :rofl: and also microdata Link to comment Share on other sites More sharing options...
.Ian Posted June 4, 2011 Share Posted June 4, 2011 CDN is already included Link to comment Share on other sites More sharing options...
Management Charles Posted June 4, 2011 Management Share Posted June 4, 2011 As is microdata :) You might want to look around a bit as it seems most of your questions are already answered :) Link to comment Share on other sites More sharing options...
Fishfish0001 Posted June 4, 2011 Share Posted June 4, 2011 The whitespace is added by the browser if I remember bfarbers pst correctly. It is minified and gzipped and when received it is unpacked I think? Its not like that when its sent. Link to comment Share on other sites More sharing options...
bfarber Posted June 6, 2011 Share Posted June 6, 2011 Yes, as mentioned IP.Board already has the ability to gzip the HTML content it delivers to the browser, which effectively removes the whitespace during transit. It costs MORE resources (server-side) to remove the whitespace than it takes to gzip/transport/ungzip by the browser. In other words, removing the HTML whitespace (which 99% of users would never see anyways, unless they're familiar with HTML already) would make deliver a page slower than the current method. We've done performance tests to be sure. It doesn't matter how 'pretty' the HTML source looks - HTML can have none or tons of whitespace and still render the page the same. Link to comment Share on other sites More sharing options...
-MM- Posted June 7, 2011 Share Posted June 7, 2011 Yes, as mentioned IP.Board already has the ability to gzip the HTML content it delivers to the browser, which effectively removes the whitespace during transit. It costs MORE resources (server-side) to remove the whitespace than it takes to gzip/transport/ungzip by the browser. In other words, removing the HTML whitespace (which 99% of users would never see anyways, unless they're familiar with HTML already) would make deliver a page slower than the current method. We've done performance tests to be sure. It doesn't matter how 'pretty' the HTML source looks - HTML can have none or tons of whitespace and still render the page the same. How about writing the code so it wont add whitespaces on page creation? Would take even lesser server side resource. Link to comment Share on other sites More sharing options...
Michael Posted June 7, 2011 Share Posted June 7, 2011 How about writing the code so it wont add whitespaces on page creation? Would take even lesser server side resource. [img] [/img] Because that's a lot of work to go through every location where whitespace could possibly be added, and would take a ton of time for very little real world benefit. Link to comment Share on other sites More sharing options...
bfarber Posted June 7, 2011 Share Posted June 7, 2011 Unfortunately with the way our templating class works it's near impossible. ;) We would have to substantially rewrite parts of the template parser to strip out empty spaces, but this could potentially lead to bugs (where-as "extra spaces in the HTML source" isn't a bug or problem), so it's just not worth it. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.