Unfortunately, when you’re dealing with a large number of recurring events, the initial parsing of the calendar is going to be slow. I think that is probably amplified on your site by having 8 feeds in the calendar and displaying it in both month and list view on the same page.
When I loaded the page, it came up very quickly, so the caching is working. One thing you may want to consider is changing the cache duration, so the number of times a user has to wait for it to load is minimized. (Of course this also means changes to the calendar won’t get picked up as quickly, but you can manually clear the calendar cache, if necessary, on the admin page.)
The default cache duration is 1 hour (3600 seconds). You can change that by setting reload="SECONDS" in your shortcode, where SECONDS is the number of seconds for the cache to live. For example, for 4 hours you’d set reload="14400" or for 1 day you’d use reload="86400".
A few other ideas for speeding this up:
1. Don’t put both the month and list views on the page. (You may want to check out the Pro version, which has an option on month view to show a month/list toggle.)
2. If there’s a logical way to do it with your events, split the feeds up into two separate calendars on multiple pages instead of putting all 8 on one page.
3. The Pro version also has a pre-caching feature, which may help avoid having users wait for the feeds to parse when the cache expires. The way this normally works is that the feeds are only re-parsed when the page with the calendar is accessed, meaning some unfortunate user may be stuck waiting for that to happen each time the cache expires. Pre-caching uses WP-Cron to automatically re-parse the feeds in the background when any page of the site is accessed. (This option is only possible in the Pro version because it relies on using Pro’s calendar builder feature rather than a manual shortcode.)
Thank you for the quick and very clear response!
(Would you consider adding a search to your user documentation? I’ll bet I could have found this info — and saved you time — but I didn’t know what to look for 🙂
Thanks, again.
The documentation is definitely still a work-in-progress. Search is coming. Thanks!