We have several events on sale at The School of Music (but I don't think too many) and our Event Listing page can take up to 30 seconds to load. We were thinking of directing our patrons to this page first but won't due to this issue. Has anyone else experience this issue and found a solution?
You can view our page here: http://music-tickets.yale.edu/single/EventListing.aspx
Thanks,
Janna
It took me about 10 seconds, which is still definitely too slow for ideal web browsing. I don't know how the page is coded, of course, but I have a few tips:
1) How long is it taking to pull the information through the Web API? If that is taking a long time then there is some issue with your back end or the scope of what you are trying to pull into one page.
2) An issue we've had is that we use keywords for a lot of performance information, but there is no good way to pull keywords through the Web API: it only allows you to search for them. Originally our coders had solved this by looping on every performance, running a search on the season based on each potentially relevant keyword, and then looping through each result set to see of the performance currently being examined was in that result set, thereby determining that the performance had that keyword attached. There can be many such workarounds for the often idiosyncratic data structures returned by the Web API, but often they come a steep performance price. In this case I had to build a view to pull through GetLocalData that would give me the information with only one additional API call per performance.
3) With a long list of performances returned, you might want to think about paginating the results. That said, while your page is longer than most search results pages these days, it doesn't strike me as particularly extreme.