I noticed this as well, they claimed it was a performance improvement but it’s not.
I switched to WooPayments and enabled Afterpay through their gateway to resolve the issue
Thread Starter
Jason
(@galapogos01)
Any updates, Afterpay?
PageSpeed Insights is flagging us for slow TBT due to your Javascript.
Third-Party
Transfer Size
Main-Thread Blocking Time
squarecdn.com
201 KiB
1,241 ms
/square-marketplace-js/chunk-analytics-vendors.js
(js.squarecdn.com)
55 KiB
763 ms
/square-marketplace.js
(js.squarecdn.com)
130 KiB
215 ms
/square-marketplace-js/chunk-placement.js
(js.squarecdn.com)
13 KiB
155 ms
/square-marketplace-js/chunk-analytics.js
(js.squarecdn.com)
3 KiB
107 ms
Hi @galapogos01,
Thank you for your messages.
The Afterpay Gateway for WooCommerce plugin previously loaded two scripts. One for launching Express Checkout and one for messaging. These are now consolidated as square-marketplace.js. The additional files are loaded on demand only if the code is required (improving performance for those pages that don’t require those parts of the script).
The team are constantly looking at ways to improve performance (in both the plugin and the scripts) and appreciates the report regarding main thread blocking. This will be reviewed and prioritised internally if any improvements can be made.
Thank you.
Thread Starter
Jason
(@galapogos01)
Thanks for the reply. Only took 3 months!
As this plugin injects the Square Marketplace JS into the product page by default, every PDP is being penalized on CWV and Page speed due to this plugin. This is known to affect both SEO and customer conversion.
I hope you can find some fixes and improve your testing processes to include front end performance.
Please leave the ticket open until a fix is released.
Thanks,
Jason
@scotterpay I noticed this as well,
any update about it
Hi @briannanda007,
Thank you for reaching out on this topic. Currently no updates are available from the Afterpay team.
Please note that there is no action for merchants using the Square Marketplace JS library in WooCommerce, as updates and improvements are handled via the Square CDN and do not require a plugin update.
For best practice and conversion rates, the Afterpay team highly recommend merchants implement both PDP and cart page messaging, which has a proven track record of success with merchant partners using the Afterpay service.
The Afterpay team will frequently and consistently update both branding and language used and as a result it is vital that merchants continue to implement and use dynamic messaging solutions for when these updates are made to remain consistent, relevant and up-to-date.
Please note that should merchant partners choose to implement static assets they will be responsible for any misrepresentation of the Afterpay service and the Afterpay team will not be able to provide support or troubleshooting should challenges arise.
Thank you.
Thread Starter
Jason
(@galapogos01)
@benfterpay your reply is not a solution and is off topic. Nobody is talking about static assets.
Can you please directly address the issue of this plugin including square-marketplace.js and subsequently impacting the CWV & PageSpeed Insights scores for every page on an eCommerce site?
Enabling Afterpay is currently negatively impacting the web performance of your own merchants in the eyes of Google and end users, penalising merchants relative to non-Afterpay sites.
All we want is a fix.
