Forum Replies Created

Viewing 9 replies - 16 through 24 (of 24 total)
  • Thread Starter rockso

    (@rockso)

    Hi, I’ve just received and email from my hosting company, who’ve been helping me also. this is their email to me….

    Hi

    Thank you for providing the steps.

    I have done some extensive testing this morning, and found the following which needs to be addressed with Litespeed support:

    Purge product on changes to the quantity or stock status. Purge categories only when stock status changes.
    X-LiteSpeed-Purge: public,9df_
    Category, Subcategory and Product pages all purged after purchase even when product remains in stock
    NOT EXPECTED
    Notes: Expected Behaviour: With this selected the expectation would be that only the product page would be purged rather than the product page, category and subcategory pages after a single purchase which does not result in the item becoming out of stock.
    Unfortunately due to the fact you are displaying the number of units in stock on your product pages this realistically is the preferred setting because otherwise the number of units in stock on each product page wouldn’t update after purchases. You do have the option of hiding the number of products in stock however.

    Purge product and categories only when the stock status changes.
    X-LiteSpeed-Purge: public,9df_FD
    Category, Subcategory and Product pages remain cached when stock status remains in stock after purchase
    EXPECTED BEHAVIOUR

    Purge product only when the stock status changes. Do not purge categories on changes to the quantity or stock status.
    X-LiteSpeed-Purge: public,9df_FD
    Category, Subcategory and Product pages remain cached when stock status remains in stock after purchase
    EXPECTED BEHAVIOUR
    Notes: If you were to hide the number of units in stock on your product pages, this setting seems to work properly with the purge changing to X-LiteSpeed-Purge: public,9df_ = which results in product page and category/subcategory pages all being purged to then be updated to Out of Stock on the product which status has changed.

    Always purge both product and categories on changes to the quantity or stock status.
    X-LiteSpeed-Purge: public,9df_
    Category, Subcategory and Product pages all purged after purchase
    EXPECTED BEHAVIOUR

    In conclusion to address the unreliable caching and performance:

    • LSCache doesn’t seem to be purging correctly in the instance that only the product should be purged on each purchase provdiing the status does not change. This needs to be addressed with Litespeed Support.

    Thread Starter rockso

    (@rockso)

    Hi..

    Product category page – Cache – miss
    TTFB 8.83s, content download 16ms, total time 8.85s
    https://postimg.cc/YLjr7zdD

    Same product category page – Cache – hit
    TTFB 27ms, content download 2ms, total time 29ms

    Same product category page, Litespeed Cache plugin disabled
    TTFB 257ms, content download 8.25s, total time 8.51
    https://postimg.cc/DmzLmVDH

    #while the cache miss and cache disabled have similar overall total times, with the plugin disabled, you see content appear on the screen with a second… and build up, rather than cache miss, where nothing appears to be happening for 8 seconds.

    Product page
    Product category page – Cache – miss
    TTFB 1.7s, content download 7ms, total time 1.8s

    Same product category page – Cache – hit
    TTFB 19ms, content download 2ms, total time 22ms

    Same product page, Litespeed Cache plugin disabled
    TTFB 279ms, content download 1.1s, total time 1.4s


    Thread Starter rockso

    (@rockso)

    I have tried all of the preset configured options.
    When pages are cached, its amazingly fast.. I understand that when a product page has it’s stock levels changed, the cache is purged.. no problem, the none-cached product pages are generally 2 seconds TTFB, so acceptable..

    The problem is with the product category pages, this is my selected option “Purge product only when the stock status changes. Do not purge categories on changes to the quantity or stock status.” Yet, each time the stock quantity changes, the product category cache is purged. Not only the category the product sits in, but also the parent categories.

    none-cached product category pages have an appalling TTFB, rendering the site almost unusable. https://ibb.co/b1V8gy2

    While none-cached pages, posts and products have a TTFB from 700ms to 2000ms…

    It seems the cache, for the whole site is being purged, upon one single change to one product’s stock levels/stock status.

    I just can’t understand why or how to fix it?

    • This reply was modified 2 years, 3 months ago by rockso.
    Thread Starter rockso

    (@rockso)

    HI, thanks for getting back to me.

    It’s not so much the page speed on none cached product pages. It’s the page speed on none cached product category pages.

    The category pages cache is being purged regularly, and I do not know why. When the product category page has no cache, the TTFB can be anywhere from 6 seconds to as bad as 24 seconds,

    From today’s tests
    https://ibb.co/4shc5yp
    https://ibb.co/Yk9k67T

    this is a staging site, so no product details, or stock levels have been altered, yet, the cache on product categories is being purged several times a day.. any help & advice is greatly appreciated.

    Thread Starter rockso

    (@rockso)

    This did nothing. Other than the stock quantity on the product page no longer updates after a sale. I have turned ESI back on, flushed the cache, re-crawled, and the stock no longer updates on front end (tested across multiple private browsers).

    In addition, switching ESI off, also did not fix the issue of product category pages cache purging and a TTFB of 10 + seconds

    Thread Starter rockso

    (@rockso)

    Hi, report sent…
    Report number: ACATXJGF
    Report date: 03/11/2024 10:33:02

    As I say, when it works, it’s blisteringly fast, and when the cache is purged, it’s awful. And despite not having Product Categories selected to purge, they are being purged.

    Screeenshot: TTFB 9.4s https://ibb.co/x7DT3kb

    It is a busy’ish site + regular 5 min API updates to stock.

    Any help is greatly appreciated!

    Thread Starter rockso

    (@rockso)

    Shameem. You are a super star !
    This worked, thank you!!

    Thread Starter rockso

    (@rockso)

    Hi, no worries.. It was explained to me by Woocommerce support that it is by design now, as part of tests to create less friction on the checkout… (which kinda doesn’t work, from a customer perspective, it causes more friction/confusion).

    Trying to stick with block based ATM, rather than legacy.

    I created a quick workaround by adding onscreen instructions for the shopper, under the tickbox for ‘create an account’

    https://ibb.co/Sc2jGn2

    • This reply was modified 2 years, 3 months ago by rockso.
    Thread Starter rockso

    (@rockso)

    you are amazing! That worked perfectly! thank you!!!

Viewing 9 replies - 16 through 24 (of 24 total)