Stripe plugin slowing down site

Do you find a solution for this?

I have the same resources consuming with the plugin and is crashing my site.

@captaincrank Hello, can you tell me where you downloaded the previous version of the plugin

I agree here, I found unnecessary Stripe JS lines being run on the product page although apple pay is disabled on the product page and Stripe should not run on that page.

Hi there, @logicwizards!

I have the same issue on my site, just a quick look into your code shows the issue very clearly:

File: /includes/class-wc-gateway-stripe.php Lines 405 to 416

	public function payment_scripts() {
		if (
			! is_product()
			&& ! WC_Stripe_Helper::has_cart_or_checkout_on_current_page()
			&& ! isset( $_GET['pay_for_order'] ) // wpcs: csrf ok.
			&& ! is_add_payment_method_page()
			&& ! isset( $_GET['change_payment_method'] ) // wpcs: csrf ok.
			&& ! ( ! empty( get_query_var( 'view-subscription' ) ) && is_callable( 'WCS_Early_Renewal_Manager::is_early_renewal_via_modal_enabled' ) && WCS_Early_Renewal_Manager::is_early_renewal_via_modal_enabled() )
			|| ( is_order_received_page() )
		) {
			return;
		}

! is_product() basically means whatever option is set is not taken into account just continue to enqueue the scripts on the product pages.

From my understanding it should be something like this:

	public function payment_scripts() {
		if (
			( ! is_product() || ( is_product() && $this->payment_request !== 'yes' ) )
			&& ! WC_Stripe_Helper::has_cart_or_checkout_on_current_page()
			&& ! isset( $_GET['pay_for_order'] ) // wpcs: csrf ok.
			&& ! is_add_payment_method_page()
			&& ! isset( $_GET['change_payment_method'] ) // wpcs: csrf ok.
			&& ! ( ! empty( get_query_var( 'view-subscription' ) ) && is_callable( 'WCS_Early_Renewal_Manager::is_early_renewal_via_modal_enabled' ) && WCS_Early_Renewal_Manager::is_early_renewal_via_modal_enabled() )
			|| ( is_order_received_page() )
		) {
			return;
		}

Would be really nice to have a fix merged for this!
All the best,
Paul

• This reply was modified 2 years, 6 months ago by Paul.

@seetiggergo i tried it on my local dev environment, seems to do the trick. BUT i got to be honest as far as my production site goes I’m still waiting for the woocommerce guys to reply to the ticket @galbaras created: https://github.com/woocommerce/woocommerce-gateway-stripe/issues/2065 let’s see what they have to add…

Cheers,
Paul

Personally, I don’t get any fraud, so this could be a setting. Either way, it’s new, and new things should be tested and, if possible, released without changing previous behaviour. If not possible, the change should be made abundantly clear in the release notes.

So far, the plugin’s had another release, yet the GitHub issue has seen 0 replies from the developers.