WordPress's Tools → Site Health screen sometimes shows caching recommendations on GUDHOST sites. Here's what they mean and what to do.
"Unable to detect the presence of page cache"
Site Health looks for a few specific response headers to decide whether a page cache exists. Our built-in cache and CDN use their own headers, so WordPress often can't see them. Your pages are still cached, and you can safely ignore this message.
"You should use a persistent object cache"
A persistent object cache is an optional extra that some very large or busy sites use to cut down database work. It isn't part of GUDHOST plans and most WordPress sites don't need one, so you can ignore this recommendation. Please don't install a caching plugin to make it go away: caching plugins conflict with the built-in cache.
"Page cache is detected, but the server response time is still slow"
Your pages are being cached, but some responses are slow. Outdated or heavy plugins and themes are the usual cause:
- Update everything under Dashboard → Updates.
- Delete plugins and themes you no longer use.
- Run Site Health again a little later, ideally after visiting a few pages while logged out.
If the warning stays, contact support and we'll look into it.
"WP_CACHE is set to false"
This setting lives in a WordPress configuration file that you can't edit from the dashboard. Contact support and we'll check it for you.