Okay
  Public Ticket #2889279
Speed optimization
Closed

Comments

  •  2
    Mikelis Eglitis started the conversation

    We have enabled the B2BKing module exclusively as affecting pages when customers are logged in as B2B Customers - as we have a fully functional B2C main business, and the B2B part is a new, still somewhat niche, part of our site.

    However, we noticed that with our current settings, PageSpeed Insigths change status completely on pages where B2BKing's status should primarily be to not do anything - i.e. any page where a customer is not logged in - from "green" to "red" on Desktop, from "yellow" to 1-digit on mobile.

    I suppose there are two options we can see:
    1) is that we have configured B2BKing in a way that makes it very slow (due to non-standard other modules or whatever) and some help with optimization would help us greatly. I suppose this could be a ram
    2) Would be to disable B2BKing as a module whenever customers are not logged in, which would make the use case for 90% of our customers just fine. The best would be some sort of system where B2BKing disables completely when not logged in, enables enough to see whether you are B2B Customer when indeed logged in, and only completely enables when you are indeed logged in as a B2B Customer (except in backend, where it would need to enable completely always, I suppose)

    Further information: When we exclude B2BKing from Autoptimize, it seems to be pdfmake.js that takes a lot of resources. When we add that to Autoptimize, it increases the handling time of autoptimize significantly. I am not sure why pdfmake.js would be running at all given times.


  •   WebWizards replied privately
  •  2
    Mikelis Eglitis replied

    Hello, just to be absolutely sure before I try:

    - Is this backwards compatible with my WP/Woo-setup (WP 4.9.8 / Woo 3.3.5) ? 
    - Would all settings within B2BKing be kept in place or would I need to restore any?

    As we purchased the module a week ago, we were served version 3.8.0, so I just need to double check.

  •  2,218
    WebWizards replied

    Yes, this should be compatible with WP 4.9.8 / Woo 3.3.5.

    All settings would be kept in place.


    My recommendation is to only deactivate the 3.8.0 version (not delete it yet). The steps would be:

    1. Deactivate 3.8.0

    2. Upload and install 3.8.6

    3. Activate 3.8.6


    That way, if there's any issue with the newer version, we can go back to the older one.


    Kind regards,

    Stefan