Browsers can hang for seconds if not minutes depending on the number of rows returned by your lookup rules / stored procedures.  While this is mostly due to the fact that browsers aren't suited for loading hundreds of rows of data, it doesn't change the fact that user experience is impacted.

Perhaps, we can avoid this loading issue by paginating the results like below rather than loading everything at once. Having something like this out-of-the-box would be ideal. 

Right now, I am getting around this loading issue by restricting the number of rows returned in my stored procedure. However, this is not an ideal solution because there may be situations where you want to see all the rows returned by your query. 

On a side note, just to make sure I don't misinform anybody, I still experienced delays in my design because I am merely copying the results from a lookup table which is hidden in the background into a custom html table with the dataTables plugin applied. I wasn't sure how I can apply this kind of pagination to the default Forms table but if anybody knows how to do this, I'd greatly appreciate your input. I'd also be curious if anyone succeeded in applying the dataTables plugin to the default Forms table.