W3 Not Caching Pages from GeoDirectory

  • Resolved perfectpaddles

    (@perfectpaddles)


    1 year, 7 months ago

    We recently installed W3 in lieu of Breeze as we were running into some plugin compatibility issues. Our site relies heavily on GeoDirectory listings and it appears that we lost the ability to cache the GeoDirectory pages (a specific listing type called gd_place) and this has caused major issues with Core Vitals….tbt, LCP and FCP are all over 2 seconds now due to server queries every time one of the pages is called. The W3 plugin shows as active on the pages in question but in the page code we see the following:

    cache-control is set to no-cache, must-revalidate, max-age=0

    Suggesting that Caching has been disabled globally for the page type. This happens on logged in and logged out access. I can’t see anywhere in the controls for W3 to enable GeoDirectory page types. Is this because we’re not using the Pro version or is there something else happening?

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    1 year, 7 months ago

    Hello @perfectpaddles

    Thank you for reaching out and I am happy to assist you with this.
    First of all, by default, When Page Caching is set to Disk: Enhanced, URLs with query strings are not cached. So if you have some URL defined by geolocation which contains a quest string in the URL it will not be cached.
    You should add those you want to cache in Performance>Page Cache, Advanced sub-box “Accept query string” text area.
    The option in Performance>Page Cache>”Cache URIs with query string variables” is also available to cache all URLs with query strings. However, you will need to change the caching method to either Disk: Basic or use memory-based caching like Redis or Memcached.

    cache-control is set to no-cache, must-revalidate, max-age=0

    This is related to Browser Cache settings and not the Page Cache settings.
    You can set the Cache-control with max age in Performance>Browser Cache>HTML&XML area.

    If you are still getting the same headers, it means that something is overriding the W3TC BC rules, like some custom rules in your .htaccess, or you are using some CDN that is setting the BC TTL, meaning it does not respect the origin rules.

    I hope this helps and let me know if you have any other questions.

    Thanks!

    Thread Starter perfectpaddles

    (@perfectpaddles)

    1 year, 7 months ago

    Thank you Marko! We’ll give it a shot.

    The Perfect Paddles Team

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    1 year, 7 months ago

    Hello @perfectpaddles

    Thank you for your feedback.
    You are most welcome!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘W3 Not Caching Pages from GeoDirectory’ is closed to new replies.