• Resolved guidotg

    (@guidotg)


    Hi, I am struggling with this issue lately and need your help please. I have sent a ticket to SiteGround but they weren’t able to solve it. I am having this problem on both my websites (other is https://wildscapes.photography). I tried disabling all plugins and also switched themes with no luck. My guess is that the issue showed up after the migration from cPanel to site tool which happened a few days ago. Furthermore, I haven’t edited anything in a while and the cache worked just fine before migration. Could you please look into this and let me know what can cause this?
    Thank you.

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    Your Dynamic caching is not working. Either disable Cloudflare or enable Full page caching on Cloudflare – both available in the plugin. Once you do that your site will work way faster. This has nothing to do with the cPanel to Site Tools migration.

    Thread Starter guidotg

    (@guidotg)

    I am not using Cloudflare, never enabled it.
    Ok I understand it has nothing to do with migration, any other clue?

    Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    One of your plugins is sending a no cache header that instructs our system not to cache it

    curl -I -X GET https://guidotramontano.com
    Cache-Control: no-store, no-cache, must-revalidate
    Pragma: no-cache

    Thread Starter guidotg

    (@guidotg)

    Thanks for your reply. It seems that deactivating the plugin Formidable Forms makes the cache work again, but TTFB is still over 2.3 seconds. I opened a ticket with Formidable to no avail. Can you please point me in the right direction to solve this? Many thanks!

    Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    It’s still not working on my end:

    :status: 200
    Content-Type: text/html; charset=UTF-8
    <strong>Pragma: no-cache</strong>
    Set-Cookie: _icl_current_language=en; expires=Tue, 23-Feb-2021 09:24:13 GMT; Max-Age=86400; path=/
    Set-Cookie: _icl_current_language=en; expires=Tue, 23-Feb-2021 09:24:14 GMT; Max-Age=86400; path=/
    Set-Cookie: wpSGCacheBypass=1; expires=Mon, 22-Feb-2021 11:04:14 GMT; Max-Age=6000; path=/; HttpOnly; SameSite=Lax
    Content-Encoding: br
    Expires: Wed, 11 Jan 1984 05:00:00 GMT
    Cache-Control: no-cache, must-revalidate, max-age=0
    Date: Mon, 22 Feb 2021 09:24:15 GMT
    Vary: Accept-Encoding
    <strong>x-proxy-cache: BYPASS</strong>
    Server: nginx
    x-cache-enabled: True
    host-header: 6b7412fb82ca5edfd0917e3957f05d89
    x-httpd: 1
    x-pingback: https://guidotramontano.com/xmlrpc.php
    x-proxy-cache-info: 0 NC:100000 UP:SKIP_CACHE_NO_CACHE

    when you test, make sure you test twice because the fist hit generates the cache. You need to get

    x-proxy-cache: HIT

    if your caching is working properly. In that case TTFB is around 100-200ms depending on where you’re testing from since it’s mostly networking.

    Thread Starter guidotg

    (@guidotg)

    Sorry I re-activated the plugin that’s why it’s still not working. Now I deactivated it again and test URL is working but TTFB still slow. Tested twice as per your advice. Can you please make a test now and see if cache is working? Sorry I don’t know how to do that.
    Thank you very much, I appreciate your help.

    Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    As I said above, you need to use dev tools -> networking -> headers of your site and get an:

    x-proxy-cache: HIT

    Your caching is still NOT working.

    Something in your website keep sending Cache-Control: no-cache, must-revalidate, max-age=0

    which disables our cache. I am afraid I can’t help you more with that. I would recommend contacting a deveoper to check why your site is sending those headers.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Test URL: URL is not cached’ is closed to new replies.