Drupal slow with Internet Explorer 6 will pay to fix

Turn on CSS Caching? That usually does the trick.

Hi

You should optimize your Database. This will help you certainly.

try installing memcache and css caching......that should do the trick....

From your statement, it seems that this is an IE6-only issue, and so beefing-up your server or even moving your site to a muscular DB server will not do anything for you. If other browsers run the site satisfactorily, then you would focus on finding out why IE6 is slow. Here are some avenues to explore:

- If you are using any PNG compatibility tricks, those approaches always make IE6 slow - consider not trying to make everything look in IE6 and it looks in IE8 or Firefox
- Do you have rounded corners and other micro-image intensive treatments on the site? Again, IE6 is not so good at multi-threading connections to the server and so if there are many images to download, it will take for ever to pull them one after the other and that will delay the time pages take to load
- CSS/JS: Beyond setting Drupal performance to condense all the CSS into 1 file (good thing that reduces the number of calls - but could ruin your layout), you should make sure you are calling scripts at the bottom of your page template. This will ensure that markup and CSS load first and then are followed by Javascript.
- Module CSS/JS: If you are running very very many modules each with it's own javascript and CSS file, you will slow IE6down because it will have to make all those calls in serial to the server

What you can do:
- If you cannot or do not want to reduce the number fo things IE6 should do, then you can make PHP flush () - http://us2.php.net/flush and maybe instruct browsers to cache markup once loaded for x number of days in your .htaccess. This will ensure that once someone visits the site, their browser ill keep the images, CSS, etc for a few hours/days before asking the server for new stuff. This will usually speed up browsing for IE6

Memcache etc:
My opinion is that memcache is a good thing to setup, but being that other browsers are fast enough, it might be an overkill and will not target the front-end issues that are at the root of the browser-specific slowness