Report - WooCommerce Payments 6.5.0

Does WooCommerce Payments work with WordPress 6.3.1 and PHP 8.1.12? A smoke test was performed on 2023-09-21 18:51:37 UTC.

Summary

Errors

1	PHP fatal errors
	No JavaScript exceptions
	All test pages loaded successfully
	No resource errors

Performance

Memory usage: 299.71 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

Page speed impact: insignificant.
The plugin didn't make the site noticeably slower.

Environment

WordPress version	6.3.1
PHP version	8.1.12
MySQL version	10.6.10
PHP memory limit	512M

Plugin Info

Last updated	2024-04-22T18:27:00+00:00
Active installs	700,000+
WordPress.org page	https://wordpress.org/plugins/woocommerce-payments/
Badges	Get badge code

Pages 2

Plugins ‹ Test site — WordPress

URL	/wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL	/wp-admin/plugins.php?action=activate&plugin=woocommerce-payments%2Fwoocommerce-payments.php&plugin_status=all&paged=1&s&_wpnonce=382d4ff9b0
Aspect	after-activation
HTTP status	200
Load time	0.336 s
Memory usage	3.19 MiB
JS errors	None
Resource errors	None

Test site – Just another WordPress site

URL	/
Aspect	front-page
HTTP status	200
Load time	0.188 s
Memory usage	3.42 MiB
JS errors	None
Resource errors	None

Benchmark

URL	Load time			Memory usage
URL	Inactive	Active	Change	Inactive	Active	Change
/wp-admin/index.php	0.383 s	0.313 s	-0.070 s	2.82 MiB	3.11 MiB	+ 294.51 KiB
/wp-admin/edit.php	0.214 s	0.215 s	+0.001 s	2.85 MiB	3.14 MiB	+ 293.68 KiB
/wp-admin/post-new.php	0.803 s	0.618 s	-0.185 s	5.21 MiB	5.57 MiB	+ 368.73 KiB
/wp-admin/upload.php	0.828 s	0.318 s	-0.510 s	2.77 MiB	3.04 MiB	+ 276.82 KiB
/wp-admin/options-writing.php	0.234 s	0.376 s	+0.142 s	2.76 MiB	3.02 MiB	+ 268.79 KiB
/wp-admin/media-new.php	0.316 s	0.318 s	+0.002 s	2.74 MiB	3.02 MiB	+ 289.02 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.207 s	0.198 s	-0.009 s	2.76 MiB	3.04 MiB	+ 294.19 KiB
/wp-admin/post-new.php?post_type=page	0.679 s	0.606 s	-0.073 s	5.21 MiB	5.56 MiB	+ 363.16 KiB
/wp-admin/options-discussion.php	0.507 s	0.250 s	-0.257 s	2.75 MiB	3.02 MiB	+ 277.31 KiB
/wp-admin/edit-comments.php	0.249 s	0.232 s	-0.017 s	2.78 MiB	3.05 MiB	+ 276.82 KiB
/	0.296 s	0.208 s	-0.088 s	3.13 MiB	3.42 MiB	+ 293.8 KiB
Average	0.429 s	0.332 s	-0.097 s	3.25 MiB	3.55 MiB	+ 299.71 KiB

Code Statistics

Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.

PHP

Language		%	Lines of code	Comment lines	Files
	PHP	94.2%	38,497	21,870	325
	Markdown	3.9%	1,589	0	39
	SVG	1.1%	430	0	46
	CSS	0.6%	235	3	3
	JavaScript	0.2%	65	11	1
	JSON	0.1%	33	0	1
Total			40,849	21,884	415

PHP Code Analysis | More results »

Lines of code	33,288
Total complexity	6,363
Median class complexity	8.0
Median method complexity	2.0
Most complex class	WC_Payment_Gateway_WCPay
Most complex function	WC_Payment_Gateway_WCPay::process_payment_for_order()

Classes	279
Methods	2,263
Functions	18

Additions

Things that the plugin adds to the site. This section is not intended to be comprehensive. The test tool only looks for a few specific types of added content.

Options `wp_options` 2

jetpack_sync_settings_disable
wcpay_should_redirect_to_onboarding

PHP Error Log 9 lines

[21-Sep-2023 18:52:05 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function WCPay\WooPay\wc_get_orders() in /wp-content/plugins/woocommerce-payments/includes/woopay/class-woopay-session.php:239
Stack trace:
#0 /wp-includes/class-wp-hook.php(310): WCPay\WooPay\WooPay_Session::run_and_remove_woopay_restore_order_customer_id_schedules()
#1 /wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters()
#2 /wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /wp-admin/includes/plugin.php(816): do_action()
#4 /wp-admin/plugins.php(209): deactivate_plugins()
#5 {main}
  thrown in /wp-content/plugins/woocommerce-payments/includes/woopay/class-woopay-session.php on line 239

WooCommerce Payments 6.5.0