Forum Moderators: open
If it's the latter, and this is applicable in your situation, you could fragment the data into groups, based on the recordset size, and load manageable clumps by page.
This doesn't help IE users at all (although, I'd consider 18 seconds a long enough wait time) - but at least the NS users will get things a little quicker.
As I said, I may be well off the mark here as to what kind of data is being served (search results?). Would you be able to give more detail?
Netscape (at least the 4.X) can't handle these large tables very well. The start rendering when the whole table arrived, and then it takes ages to finish.
Split the output in several smaller tables, let's say on for every 50 records.
If you have no borders for the tables, no one will see it.