Turn off the viewstate
Unless you need it
Page.EnableViewState = false;
Split the table
If you don't want to go down the paging route you could also try splitting a large <table>
into several smaller <table>
s. (It used to be the case that the browser could only render a table after it has seen the final </table>
. I'm not sure if this is still true, but definitely worth a shot)
Get rid of crap
Ensure that you are using css and not using stuff like
<td width="40" valign="top"> 50 </td>
<td class="a"> 50 </td> <!-- better -->
<td>50</td> <!-- best -->
<!-- if you need to specify a width, you only need to do it in one row -->
Remember crap * 7000 = alot of crap
Reduce page size at all costs
Sometimes the problem is not rendering of the page, but it is the downloading that causes the problem, so check that out.
Nested tables will really hurt you
Nuff said