• Resolved wynot

    (@wynot)


    Hi –

    I just update to v7.0.5 and am seeing the following error in console log:


    js?client-id=ATwlXIW…ylater,card,venmo:2 [Violation] Permissions policy violation: unload is not allowed in this document.ut@js?client-id=ATwlXIW…ylater,card,venmo:2(anonymous)@js?client-id=ATwlXIW…ylater,card,venmo:2t@js?client-id=ATwlXIW…ylater,card,venmo:2__FIRST_RENDER_EXPERIMENTS__.venmoVaultWithoutPurchase@js?client-id=ATwlXIW…ylater,card,venmo:2(anonymous)@js?client-id=ATwlXIW…ylater,card,venmo:2(anonymous)@js?client-id=ATwlXIW…ylater,card,venmo:3

    This happens when I click on ANY product from the store page.

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

Viewing 6 replies - 1 through 6 (of 6 total)
  • Hi! The Ecwid Support team is here. According to our developers, this warning is not critical and doesn’t affect your store’s performance. However, they will still work on removing it. As soon as we have an update, we’ll email you at the address associated with your Ecwid account.

    Thread Starter wynot

    (@wynot)

    Great! Thank you for your quick response too!

    Thread Starter wynot

    (@wynot)

    Hi – This error is still here and we believe it is the cause of our slow store response seo problem.

    Can you please fix this as soon as possible?

    Thank you!

    Hi there!

    The task mentioned above is still in our developers’ queue so we’ll update you once there is any news. For now, there is no ETA, sorry.

    In the meantime, the error you specified shouldn’t affect SEO as it relates to PayPal and Venmo.

    The Permissions Policy warning about unload is a Chrome 117+ console message, not an actual error. It fires when a third-party script (PayPal’s SDK in this case) attaches a listener to the deprecated unload event. Browsers still run the listener; nothing breaks. xenafromlightspeed is correct that it has zero SEO impact: Search Console renders pages headless and never sees browser console output.

    For the slow store response, the warning isn’t the cause. Run the store URL through PageSpeed Insights and check LCP and Total Blocking Time. If TBT is high, that usually points to PayPal’s SDK loading on every product page even without checkout. PageSpeed flags it under “Reduce the impact of third-party code”.

    The actual fix is to defer or conditionally load PayPal until the cart is opened. In Ecwid’s settings under Payment, check whether the PayPal/Venmo buttons are configured to show on product pages. If you don’t need express checkout from listings, disabling that drops the SDK from the LCP path entirely.

    Thread Starter wynot

    (@wynot)

    Ok, Thank YOU for this detailed response!

    Very Much appreciated.

Viewing 6 replies - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.