There’s no good reason I can think of why your bg would be re-loading again and again, unless your browsers have caching turned off (can happen). However, I notice everything’s in a table who doesn’t have table-layout: fixed. You can get browsers to load that table faster by telling them they don’t have to check ALL the rows and cols before rendering: even though you have a width stated, with table-layout: fixed you tell the browser to basically base everything on the first row.
You took care of the scrollbar possibly being an issue by forcing it every page.
I can’t see the other problems right now, no IE.
…
You have margin: 0 auto on #container, but no width. Automargins will be ignored.
Besides, everything’s in the table, who does have a fixed width. Why not margin: 0 auto the table instead?
background-image: url(../images/pagebg.jpg);
background-repeat: no-repeat;
background-position: center top;
Condense properties. background: #fff url(…/images/pagebg.jpg) 50% 0 no-repeat;
Guess it’s now time for the obligatory “why is this page built in (nested!) tables? Do you hate blind people?” statement.
Also this
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="12%" height="40" align="center" class="footermenuborder"><a href="index.html" class="footerlinks" title="home">HOME</a></td>
<td width="14%" align="center" class="footermenuborder"><a href="about.html" class="footerlinks" title="about lipau">ABOUT</a></td>
<td width="14%" align="center" class="footermenuborder"><a href="design.html" class="footerlinks" title="design">DESIGN</a></td>
<td width="16%" align="center" class="footermenuborder"><a href="support.html" class="footerlinks" title="support">SUPPORT</a></td>
<td width="16%" align="center" class="footermenuborder"><a href="sourcing.html" class="footerlinks" title="sourcing">SOURCING</a></td>
<td width="16%" align="center" class="footermenuborder"><a href="contact.html" class="footerlinks" title="contact lipau">CONTACT</a></td>
<td width="12%" align="center" class=""><a href="news.asp" class="footerlinks" title="news">NEWS</a></td>
</tr>
Whoa, just use a list and some CSS.
You have a list for the submenu… did you know the rest of the menu can be a list?
<ul id="arrowsidemenu">
<li><a href="index.html">HOME</a></li>
<li><a href="about.html">ABOUT</a></li>
<li id="menuheaders"><a href="services.html">SERVICES</a>
<ul>
<li><a href="design.html">DESIGN</a></li>
<li><a href="support.html">SUPPORT</a></li>
<li><a href="sourcing.html">SOURCING</a></li>
</ul>
</li>
<li><a href="contact.html">CONTACT</a></li>
<li><a href="news.asp">NEWS</a></li>
</ul>
Only reason I have an id on that Services is because it would be easier to target it with Javascript than if you had to walk the DOM for it. Also removed titles. Titles on anchors who already have anchor text is a sin as bad as nested tables but without the stigma.
I would have to see if I can find anything with IE when I get back to work, but with everything in tables… to be honest, I got into this whole web thing after tables kinda died for layout, so I’m not aware of too many issues specifically with IE and tables.