Daniel Mahaffy

The “All-in-One Event Calendar” by Time.ly works great, but uses dynamic javascript. 
This plugin creates a static version of the javascript that can be cached by 
the browser.
I have tested this plugin with versions 2.1.9 and 2.2.0 of the event calendar plugin. 
It may work with future releases, but use it at your own risk.
This plugin only uses the static javascript on the frontend. If a user is 
logged in, the original dynamic script will be used. As far as I can tell 
caching the javascript does not interfere with the plugin’s functionality, but 
there may be features of the event calendar that do not work with this plugin.

Fix Event Calendar Caching

This plugin makes the All-in-One Event Calendar's javascript cacheable to improve page load speed.

WordPress.org

This plugin adds support for the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API" rel="nofollow ugc">Speculation Rules API</a>, which allows defining rules by which certain URLs are dynamically prefetched or prerendered. This core Speculative Loading functionality was <a href="https://make.wordpress.org/core/2025/03/06/speculative-loading-in-6-8/" rel="nofollow ugc">merged into WordPress 6.8</a>, but it only prefetches with conservative eagerness by default. In contrast, this plugin defaults to prerendering with moderate eagerness (i.e. when interacting with a link), and it provides a user interface to customize the mode and eagerness via the “Speculative Loading” section on the Settings > Reading admin screen.
By default, speculative loading is only enabled for logged-out users, since unauthenticated pages are typically only eligible for caching and so more efficient to prefetch/prerender. This means that sites with frequent logged-in users on the frontend—such as e-commerce, forums, or membership sites—will not benefit from the feature. If your server can handle the additional load (for example, with persistent object caching), you can opt in to enable speculative loading for all logged-in users or for administrators only. This setting exclusively affects frontend pages; admin screens are always excluded.
A filter can be used to exclude certain URL paths from being eligible for prefetching and prerendering (see FAQ section). Alternatively, you can add the <code>no-prerender</code> CSS class to any link (<code><a></code> tag) that should not be prerendered. See FAQ for more information.
<h4>Browser support</h4>
The Speculation Rules API is a new web API, and the functionality used by the plugin is supported in Chromium-based browsers such as Chrome, Edge, or Opera using version 121 or above. Other browsers such as Safari and Firefox will ignore the functionality with no ill effects; they will simply not benefit from the speculative loading. Note that certain browser extensions may disable preloading by default.
<ul>
<li><a href="https://caniuse.com/mdn-html_elements_script_type_speculationrules" rel="nofollow ugc">Browser support for the Speculation Rules API in general</a></li>
<li><a href="https://developer.chrome.com/docs/web-platform/prerender-pages" rel="nofollow ugc">Information on document rules syntax support used by the plugin</a></li>
</ul>
This plugin was formerly known as Speculation Rules.

Speculative Loading

Nice


Amazing results on install. Will continue to check this one out. 


Interesting and Impressive

Does what it needs to do.

Enables browsers to speculatively prerender or prefetch pages to achieve near-instant loads based on user interaction.

Fix Event Calendar Caching vs Speculative Loading