Jump to content

IPB HTML Minify - IPB is very ugly in html

Featured Replies

Posted

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.

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.

Does it really make any difference?

There is an option in the ACP to remove the white spaces, I am sure.

  • Author

@Michael : Thanks for you reply ^^

Hope IPB will add CDN function in IPB 3.2 :rofl: and also microdata

CDN is already included

  • Management

As is microdata :)

You might want to look around a bit as it seems most of your questions are already answered :)

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.

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.


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. %7Boption%7D

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.

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.

Archived

This topic is now archived and is closed to further replies.

Recently Browsing 0

  • No registered users viewing this page.