Headers not detected

  • Resolved jimlongo

    (@jimlongo)


    12 months ago

    I’ve installed redis on the server and activated the Redis Object Cache plugin.

    The plugin settings indicate everything is setup properly, yet my Site Health continues to state times slightly higher than the 600ms recommendation (same as before).

    Also indicates ?No client caching response headers were detected.

    Diagnostics:

    Status: Connected
    Client: Predis (v2.1.2)
    Drop-in: Valid
    Disabled: No
    Ping: PONG
    Errors: []
    PhpRedis: Not loaded
    Relay: Not loaded
    Predis: 2.1.2
    Credis: Not loaded
    PHP Version: 8.1.25
    Plugin Version: 2.5.0
    Redis Version: 6.2.7
    Multisite: No
    Metrics: Enabled
    Metrics recorded: 122
    Filesystem: Writable
    Global Prefix: "uxx4uvkba_"
    Blog Prefix: "uxx4uvkba_"
    WP_REDIS_PLUGIN_PATH: "/home/tennis/public_html/_CLUBS/swansea/wp-content/plugins/redis-cache"
    Global Groups: [
    "blog-details",
    "blog-id-cache",
    "blog-lookup",
    "global-posts",
    "networks",
    "rss",
    "sites",
    "site-details",
    "site-lookup",
    "site-options",
    "site-transient",
    "users",
    "useremail",
    "userlogins",
    "usermeta",
    "user_meta",
    "userslugs",
    "redis-cache",
    "blog_meta",
    "network-queries",
    "site-queries",
    "user-queries"
    ]
    Ignored Groups: [
    "counts",
    "plugins",
    "theme_json",
    "itsec-lockouts",
    "themes"
    ]
    Unflushable Groups: []
    Groups Types: {
    "blog-details": "global",
    "blog-id-cache": "global",
    "blog-lookup": "global",
    "global-posts": "global",
    "networks": "global",
    "rss": "global",
    "sites": "global",
    "site-details": "global",
    "site-lookup": "global",
    "site-options": "global",
    "site-transient": "global",
    "users": "global",
    "useremail": "global",
    "userlogins": "global",
    "usermeta": "global",
    "user_meta": "global",
    "userslugs": "global",
    "redis-cache": "global",
    "blog_meta": "global",
    "network-queries": "global",
    "site-queries": "global",
    "user-queries": "global",
    "counts": "ignored",
    "plugins": "ignored",
    "theme_json": "ignored",
    "itsec-lockouts": "ignored",
    "themes": "ignored"
    }
    Drop-ins: [
    "advanced-cache.php v by ",
    "maintenance.php v by ",
    "Redis Object Cache Drop-In v2.5.0 by Till Krüss"
    ]
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Julie

    (@julieadrienne)

    Hi! Can you post screenshots of those notices in Site Health?

    Thread Starter jimlongo

    (@jimlongo)

    Thanks, here is the screenshot.

    Note: also installed is Comet Cache plugin.

    And the following drop-ins:

    object-cache.php
    Redis Object Cache Drop-In

    advanced-cache.php

    • This reply was modified 12 months ago by jimlongo.
    Plugin Support Julie

    (@julieadrienne)

    Thanks. That notice is related to Comet Cache’s page cache.

    Redis Object Cache does not cache pages, it caches objects such as queries and metadata ??

    Thread Starter jimlongo

    (@jimlongo)

    Thanks. So what would you suggest in terms of performance because the Redis plugin is not impacting performance at all.

    Thread Starter jimlongo

    (@jimlongo)

    removed Comet Cache and it’s associated drop-in.

    Plugin Support Julie

    (@julieadrienne)

    Redis Object Cache does not send any headers, the notice might be related to your CDN or hosting provider.

    So what would you suggest in terms of performance because the Redis plugin is not impacting performance at all.

    No, Redis Object Cache is a pure performance plugin. But if you you benchmark the page cache, it will never kick in. Try benchmarking the WordPress admin (or checkouts) with and without Redis Object Cache.

    Thread Starter jimlongo

    (@jimlongo)

    Thank you Julie.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Headers not detected’ is closed to new replies.

Tags