Website slow only on Mac

It seems tha开发者_运维技巧t our site (.Net based , ASP 3.5, minor use of Flash) runs awfully slow on Mac (OSX, FireFox 3.5)

e.g. http://www.cadastre.be/Belgique/Bruxelles_Capitale/Bruxelles

It usually happens on large pages (about 200k) - while the same page runs smoothly on the same machine running Windows VM.

My initial assumption was that it is something related to the created HTML code, however, the site does run slowly as well on other browsers (Safari, Chrome) - although a bit faster.

Are there are known aspx specific controls that causes Mac/Firefox to behave slowly ?

Is there something specific I should look in the created HTML code ?

Here's a short summary: 1. Happens only on Mac 2. All browsers 3. Validate HTML - looks quite good. Fixing several html / javascript errors didn't help 4. Javascript disabled on Browser 5. Flash disabled 6. Downloaded the full HTML for offline use and then opened it from the Browser - works very very fast. 7. Does not happen %100 of the time

Thanks

Well, the page is rather large (over 100000 bytes), and there are a few validation errors.

1. On the home page there is a script tag before the DTD that needs to go into the head section.

2. Running the page through the Firefox Error Console brings up problems with the .ajax__tab_header class in the stylesheet not being converted into a valid image path: <%=WebResource("AjaxControlToolkit.Tabs.tab-line.gif")%> so it might be better to serve static stylesheets straight from a media server, and do any dynamic work by applying classes in the generated HTML.

3. Also, running the page through the W3C validator brings up a load of simple markup errors.

4. I haven't checked, but you may also have too many HTTP calls per page - try using YSlow to see which components are slow to load. Steve Souders covers this issue in chapter 1 of High Performance Websites.

5. Finally, there's a character encoding mismatch - you still have some iso-8859-1 hanging around - it should be UTF-8 throughout (check: HTML, server, database etc.).

The above issues all add up, and probably need to be addressed before you test again.