Wp 6.1

  • Resolved dimal

    (@dimalifragis)


    2 years ago

    Hello.

    Does the following from WP 6.1 health check looks ok?

    Page cache is not detected but the server response time is OK Performance

    Page cache enhances the speed and performance of your site by saving and serving static pages instead of calling for a page every time a user visits.

    Page cache is detected by looking for an active page cache plugin as well as making three requests to the homepage and looking for one or more of the following HTTP client caching response headers:
    cache-control, expires, age, last-modified, etag, x-cache-enabled, x-cache-disabled, x-srcache-store-status, x-srcache-fetch-status.

    Median server response time was 65 milliseconds. This is less than the recommended 600 milliseconds threshold.

    No client caching response headers were detected.

    A page cache plugin was not detected.

Viewing 15 replies - 1 through 15 (of 15 total)
  • Plugin Author Emre Vona

    (@emrevona)

    can you tell me the site url please?

    Plugin Author Emre Vona

    (@emrevona)

    I fixed the problem. Please update to latest version wp fastest cache.

    Metasequoia

    (@metasequoia)

    Wordpress 6.1 still shows the notice in health check for my sites although latest version of Fastest Cache is installed and active…

    Thread Starter dimal

    (@dimalifragis)

    @metasequoia Not for me.

    Plugin Author Emre Vona

    (@emrevona)

    can you tell me your site url please?

    Metasequoia

    (@metasequoia)

    https://www.seifengarten.de/

    Plugin Author Emre Vona

    (@emrevona)

    are you using Nginx web-server?

    Thread Starter dimal

    (@dimalifragis)

    @metasequoia

    Try to disable the browser caching in Fastest Cache, if you have enabled it.

    Metasequoia

    (@metasequoia)

    It’s an Apache web server.

    Disabling browser caching in Fastest Cache has not solved the issue…

    Plugin Author Emre Vona

    (@emrevona)

    may it be Nginx+Apache?

    Metasequoia

    (@metasequoia)

    This is what UpdraftPlus plugin tells me:
    Webserver: Apache (Linux s133.goserver.host 64-bit #1 SMP Debian 5.10.149-2 (2022-10-21))

    Plugin Author Emre Vona

    (@emrevona)

    did you try another cache plugin for testing?

    Metasequoia

    (@metasequoia)

    Yes, I just tried Cachify plugin: the notice in health check is gone!

    Plugin Author Emre Vona

    (@emrevona)

    are you sure that cache is served via the Rewrite rule? I see the “last-modified” value in the header.

    Metasequoia

    (@metasequoia)

    This is what the plugin told me to add to .htaccess file:

    # BEGIN CACHIFY
    <IfModule mod_rewrite.c>
    # ENGINE ON
    RewriteEngine on

    # set hostname directory
    RewriteCond %{HTTPS} on
    RewriteRule .* – [E=CACHIFY_HOST:https-%{HTTP_HOST}]
    RewriteCond %{HTTPS} off
    RewriteRule .* – [E=CACHIFY_HOST:%{HTTP_HOST}]

    # set subdirectory
    RewriteCond %{REQUEST_URI} /$
    RewriteRule .* – [E=CACHIFY_DIR:%{REQUEST_URI}]
    RewriteCond %{REQUEST_URI} ^$
    RewriteRule .* – [E=CACHIFY_DIR:/]

    # gzip
    RewriteRule .* – [E=CACHIFY_SUFFIX:]
    <IfModule mod_mime.c>
    RewriteCond %{HTTP:Accept-Encoding} gzip
    RewriteRule .* – [E=CACHIFY_SUFFIX:.gz]
    AddType text/html .gz
    AddEncoding gzip .gz
    </IfModule>

    # Main Rules
    RewriteCond %{REQUEST_METHOD} !=POST
    RewriteCond %{QUERY_STRING} =””
    RewriteCond %{REQUEST_URI} !^/(wp-admin|wp-content/cache)/.*
    RewriteCond %{HTTP_COOKIE} !(wp-postpass|wordpress_logged_in|comment_author)_
    RewriteCond /home/www/seifengarten.de/wp-content/cache/cachify/%{ENV:CACHIFY_HOST}%{ENV:CACHIFY_DIR}index.html -f
    RewriteRule ^(.*) /wp-content/cache/cachify/%{ENV:CACHIFY_HOST}%{ENV:CACHIFY_DIR}index.html%{ENV:CACHIFY_SUFFIX} [L]
    </IfModule>
    # END CACHIFY`

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘Wp 6.1’ is closed to new replies.