?wpacu_preload=1 creates page caching overhead
-
A side-effect of preloading assets is that the page itself also gets preloaded for guest. This works fine at a layer where query strings are usually ignored, eg Cloudflare. But server-based caching (eg httpd’s mod_cache) also has to take care of the admin backend, which relies on the query string to show different pages, and doesn’t have an option to ignore query strings just for guest. This leads to the server storing a
?wpacu_preload=1
version of each page which never gets actually used when guests visit.Is there anything that might be done about this?
Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
- You must be logged in to reply to this topic.