Forum Moderators: open
The table is located on my profile site at /Wrpubs.htm
[edited by: tedster at 1:55 pm (utc) on July 17, 2002]
[edit reason] remove personal urls [/edit]
It's about 158kb of HTML, and that includes lots of text, which gets native compression at the modem compared to, say 158kb of images or zip files. So I'd say there is something fishy happening to give the results you are seeing.
A quick fix - one I use a lot - is to break the table into several smaller ones. That way the top of the page often renders and is usable while the rest is still downloading.
[edited by: tedster at 2:07 pm (utc) on July 17, 2002]
Looking at the code for the footer links reveals a tremendous waste of kb: nested font tags!
<font face="Carlton LET" size="+2" color="#9FA6C7"><font face="Carlton LET" size="+2" color="#9FA6C7"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><font face="Carlton LET" size="+2" color="#9FA6C7"><font size="1"><font face="Verdana, Arial, Helvetica, sans-serif"><a href="some-link.htm">Some Link</a></font></font></font>
All of the above is for a single link! You can save a tremdous amount of code and filesize by using CSS in place of the hundreds of font tags present on this page. The difference in rendering times will be noticeable in any combination of browser and Internet connection.
Best of luck!
I have seen that kind of overkill when klicking the "save as HTML" button in word. But then wouldn't that mean the page would be faster with IE?
One thing I did notice when looking at your source code, is that the offending table had two columns, both with specified widths of 197 and 343 respectively.
An useful technique to increase rendering speed for such a table is to apply a fixed table layout like so...
<table ... style="table-layout:fixed">
This allows the table to start rendering immediately as it doesn't have to load up all the table data first to calculate the most appropriate column widths.
This is valid CSS and you can find out more about it on the W3C site's CSS level 2 - Tables [w3.org] and at MSDN [msdn.microsoft.com]