Does "WP Service Payment Form With Authorize.net" work with WordPress 6.3.2 and PHP 8.1.12? A smoke test was performed on .
No PHP errors, warnings or notices | |
2 | JavaScript exceptions |
All test pages loaded successfully | |
No resource errors |
Memory usage: 17.47 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.
WordPress version | 6.3.2 |
---|---|
PHP version | 8.1.12 |
MySQL version | 10.6.10 |
PHP memory limit | 512M |
Last updated | |
---|---|
Active installs | 500+ |
WordPress.org page | https://wordpress.org/plugins/wp-service-payment-form-with-authorizenet/ |
Badges |
Get badge code |
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=wp-service-payment-form-with-authorizenet%2Fwp-service-payment-form-with-authorizenet.php&plugin_status=all&paged=1&s&_wpnonce=673cc5dbae |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.282 s |
Memory usage | 2.79 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wpspf-plugin-settings-page |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.175 s |
Memory usage | 2.88 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wpspf-all-payments |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.148 s |
Memory usage | 2.81 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wpspf-form-settings |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.162 s |
Memory usage | 2.83 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wpspf-settings-document |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.164 s |
Memory usage | 2.78 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.193 s |
Memory usage | 3.08 MiB |
JS errors |
|
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.365 s | 0.317 s | -0.048 s | 2.83 MiB | 2.85 MiB | + 22.15 KiB |
/wp-admin/edit.php | 0.209 s | 0.185 s | -0.024 s | 2.85 MiB | 2.87 MiB | + 21.44 KiB |
/wp-admin/post-new.php | 0.747 s | 0.710 s | -0.037 s | 5.22 MiB | 5.26 MiB | + 45.77 KiB |
/wp-admin/upload.php | 0.585 s | 0.509 s | -0.076 s | 2.77 MiB | 2.78 MiB | + 5.14 KiB |
/wp-admin/options-writing.php | 0.221 s | 0.175 s | -0.046 s | 2.77 MiB | 2.76 MiB | - 2.63 KiB |
/wp-admin/media-new.php | 0.344 s | 0.231 s | -0.113 s | 2.74 MiB | 2.76 MiB | + 16.97 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.189 s | 0.183 s | -0.006 s | 2.76 MiB | 2.78 MiB | + 22.14 KiB |
/wp-admin/post-new.php?post_type=page | 0.578 s | 0.581 s | +0.003 s | 5.21 MiB | 5.25 MiB | + 41.36 KiB |
/wp-admin/options-discussion.php | 0.216 s | 0.246 s | +0.030 s | 2.75 MiB | 2.76 MiB | + 7.14 KiB |
/wp-admin/edit-comments.php | 0.440 s | 0.201 s | -0.239 s | 2.78 MiB | 2.79 MiB | + 4.81 KiB |
/ | 0.275 s | 0.175 s | -0.100 s | 3.13 MiB | 3.14 MiB | + 7.88 KiB |
Average | 0.379 s | 0.319 s | -0.060 s | 3.26 MiB | 3.27 MiB | + 17.47 KiB |
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.
Language | % | Lines of code | Comment lines | Files | |
---|---|---|---|---|---|
PHP | 91.6% | 2,038 | 273 | 9 | |
JavaScript | 7.0% | 156 | 12 | 2 | |
CSS | 1.3% | 30 | 2 | 1 | |
Total | 2,224 | 287 | 12 |
Lines of code | 1,378 |
---|---|
Total complexity | 212 |
Median class complexity | 21.0 |
Median method complexity | 1.0 |
Most complex class | WPSPF_PAYMENT_Table |
Most complex function | wpspf_service_payment_request_ajax() |
Classes | 1 |
---|---|
Methods | 8 |
Functions | 29 |
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.
The log file is empty.