Context Navigation

Changes between Initial Version and Version 2 of Ticket #64066

Ticket #64066
- Property Keywords has-patch added
- Property Summary changed from Speculative Loading: Change default eagerness from conservative to moderate when page cache is detected to Speculative Loading: Change default eagerness from conservative to moderate when caching is detected

initial	v2
13	13	Nevertheless, a key reason for being `conservative` is to minimize the chance of unused speculative loads. This is to guard against the increased server load, while also being a sustainability concern. On many shared hosts, the additional traffic incurred by `moderate` may overtax their limited CPU resources. Nevertheless, this is also an issue when such a site sees an influx in visitors. In order to deal with such traffic spikes, the go-to solution is to use a [https://developer.wordpress.org/advanced-administration/performance/optimization/#caching page caching] solution. In fact, WordPress 6.1 introduced a Site Health test via #56041 which specifically checks for the presence of a page cache.
14	14
	15	As an additional safeguard, `moderate` eagerness can be contingent based on whether a persistent object cache is present, that is, whether `wp_using_ext_object_cache()` returns true. Note that a Site Health test for persistent object cache was introduced in #56040; it could be updated to note that enabling persistent object cache can increase the eagerness in speculative loading, which can also be noted in the Site Health test for page caching.
	16
15	17	As noted in the dev note that the default `eagerness` “may change in a future WordPress release”, I'm proposing that the Site Health test for page cache could be leveraged as a signal to change the default `eagerness` from `conservative` to `moderate`.