Hello collective wisdom --
We have two EAD-encoded finding aids whose size is causing problems for some patrons -- their browser locks up or otherwise fails to load the file. We don't render on the fly; we create static HTML files. The problem is partly file size (one is 3.4M and the other is 5.8M), and partly that the inventory section is a ginormous HTML table (yeah, I know) which takes a lot to render and load in the browser.
We've come up with a number of options, none of which I feel are ideal, so I'm curious if others have encountered this, how you chose to handle it, and what if any impact it had on search/discovery.
Special Collections Research Center
Syracuse University Libraries
[log in to unmask]