Stripe creating a huge amount of DNS calls

Hi there @jdbcomputing ??

Thank you for reaching out about this.

Hi all, the Stripe plugin is causing a huge amount of DNS requests and rather a sizable chunk of total page size as well. 43/74 requests are stripe related, and 940kb of code…

I also went ahead with utilizing GTmetrix, for the product page shown in your screenshot, and another one. The results vary, as can be seen in the screenshots below:

Furthermore, it appears that the performance issues that GTmetrix reports, resulting in at least 1.5 seconds delay in load times, are the following:

I trust that points you in the right direction, but if you have more questions, let us know.

We’re happy to help.

• This reply was modified 1 year, 5 months ago by anastas10s. Reason: typo

Hi @anastas10s

The site certainly has other performance issues I’m working on, but I am specifically talking about the Stripe plugin here and querying why it requires so many DNS calls for a simple pageload.

I’m even more curious why the amount of data stripe uses differs from product to product when the products are functionally identical – anywhere from 400kb to 900kb.

Hello again @jdbcomputing ??

I am specifically talking about the Stripe plugin here and querying why it requires so many DNS calls for a simple pageload.

I’m even more curious why the amount of data stripe uses differs from product to product when the products are functionally identical – anywhere from 400kb to 900kb.

Just to clarify, what version of the WooCommerce Stripe Payment Gateway plugin is installed at your site?

From what I gather, this was addressed some time ago (issue linked here).

To get an idea of how your site is configured, could you please share a copy of your site’s System Status? You can find it via ‘WooCommerce > Status’. Select “Get system report” and then “Copy for support”. Once you’ve done that, paste it here in your response.

Looking forward to hearing from you!

@anastas10s

It’s 7.6.0, which is why I didn’t read too far into that thread when I found it. The functions have removed the unnecessary calls – it’s frankly bizarre that you’d need to read a three year old thread to find this information out, considering none of this is mentioned in the documentation at all.

There are no toggles in the plugin, either – having to add code to remove unnecessary code is just odd.

https://woocommerce.com/document/stripe/#hooks-actions-filters

Hi there @jdbcomputing ??

It’s 7.6.0, which is why I didn’t read too far into that thread when I found it. The functions have removed the unnecessary calls – it’s frankly bizarre that you’d need to read a three year old thread to find this information out, considering none of this is mentioned in the documentation at all.

I understand. Just to note, right under the title of #2065, it reads: Fixed by?#2110. Which, in turn, was merged on November 9, 2021. Again, the information is available publicly, under the title of each, and included in the plugin’s changelog (version 5.8.0).

Feel free to comment on the GitHub pages linked above, with further details on how to replicate what you are experiencing, should you need to.

There are no toggles in the plugin, either – having to add code to remove unnecessary code is just odd.

https://woocommerce.com/document/stripe/#hooks-actions-filters

One of the advantages of open source software, like WooCommerce Stripe Payment Gateway (main GitHub page linked here), is being able to implement further customizations, and the ability to participate and improve things.

I’d suggest checking out the first two responses in this thread also, for different ways to implement things.

I hope that helps!