Any plans to replace cart fragments with a better performing alternative?

  • Resolved dimitrisv

    (@dimitrisv)


    1 year, 1 month ago

    Hello,

    For years we are struggling to compete with Open Cart and Magento alternatives that have a key feature: As soon as the user clicks on the add to cart button their cart immediately refreshes.

    The importance of the responsivity of the add-to-cart call cannot be over-stated enough. It is one of the most critical factors in establishing trust with the customer and is conversion multiplier.

    I have asked time and time again, if Woocommerce is happy to have a 1-2seconds response time with the add to cart event.

    We also know that with REST-API calls one can get a much faster performance. But no response so far.

    Recently, it came to my attention that Cart fragments have indeed being replaced with a much faster alternative by WP Engine. I just guess that in order to have a decent add to cart response time on par with the competition one has to pay a premium!

    I feel particularly sad that I have tuned my site to deliver 94/100 (mobile) and 100/100 (desktop) performance on Google Pagespeed making it one of the fastest eshops in my native Greece (if not worldwide)
    PageSpeed Insights (web.dev)
    and yet there is nothing I can do about the add to cart functionality.

    I was wondering that now that your dev team has completed the long due HPOS migration (that offers tremendous boost in performance), if it just about the time to sort out this issue that costing all of us literally billions in lost conversions.

    Thank you for your consideration.

    • This topic was modified 1 year, 1 month ago by dimitrisv.
Viewing 1 replies (of 1 total)

  • Hi there @dimitrisv ??

    Thank you for contacting Woo support!

    Any plans to replace cart fragments with a better performing alternative?

    Beginning with WooCommerce 7.8,?we implemented a change?that disables the cart fragments script from being enqueued on all page routes of a WooCommerce store by default. Responsible for updating the?cart widget?after a successful add-to-cart event, the script can cause performance issues on stores not using that functionality. Going forward the script will now only be enqueued if the Cart Widget is rendered in a view. Keep in mind that some themes (like Storefront)?hard-code the widget?into the theme’s templates, so it is not always user-added.

    This article provides a deeper overview of why this change was necessary and some suggested best practices (or recommendations) going forward.

    I hope this is helpful! Please let us know if you have any further questions or concerns.

Viewing 1 replies (of 1 total)
  • The topic ‘Any plans to replace cart fragments with a better performing alternative?’ is closed to new replies.