Read WordPress Speed Settings

See a WordPress site's speed settings: which caching plugin runs it, which optimisations are on, and which of them are risky on this particular site.

It reports the current caching and performance state. It reports the page cache, minify, lazy load, combine and defer switches, whether the server actually supports the cache plugin, and which fragile page builders are installed — combining or deferring scripts is a known way to break an Elementor or Slider Revolution site.

When no cache plugin is active, read install_recommended before suggesting one. It is false when the host manages caching itself through a must-use plugin (Natro, SiteGround, WP Engine, Kinsta and similar: cache_managed_by_host=true), when a previous activation was refused by host policy (plugin_activation_blocked=true), or when wp-config.php or wp-content is not writable. In each of those cases installing a cache plugin cannot work. stale_cache_config=true is separate and blocks nothing: it only means an earlier cache plugin was removed and left WP_CACHE behind in wp-config.php; it is history, not an error.

WHY ONE PAGE IS NOT CACHED (Connector 0.7.7+, LiteSpeed): `cache_exclusions` lists what is kept out of the page cache — do_not_cache_uri, query_string, cookie, user_agent, role, category and tag, plus private_uri and the forced-cache lists. When page caching is on but a single page still misses every time, the cause is almost always an entry here. If the front page itself is excluded, `cache_exclusion_warning` says so outright. It shows whether a page is actually cached, separately from TTL settings. `cache_runtime` adds crawler_enabled (the cache warmer) and public_ttl: on a site with many rarely-visited pages a cold cache, not a short TTL, is what visitors hit. These lists are edited with wordpress_option on the matching `litespeed.conf.*` name — read the current value first, then write the full list back.