Does CryptoPay Lite work with WordPress 6.3.1 and PHP 8.1.12? A smoke test was performed on .
No PHP errors, warnings or notices | |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors | |
Looks good! No problems were detected. |
Memory usage: 84.8 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.021 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 6.3.1 |
---|---|
PHP version | 8.1.12 |
MySQL version | 10.6.10 |
PHP memory limit | 512M |
Last updated | |
---|---|
Active installs | 100+ |
WordPress.org page | https://wordpress.org/plugins/cryptopay-wc-lite/ |
Badges |
|
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=cryptopay-wc-lite%2Findex.php&plugin_status=all&paged=1&s&_wpnonce=8e74ad34d6 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 2.895 s |
Memory usage | 2.99 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=cryptopay_lite_home |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.920 s |
Memory usage | 2.88 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=cryptopay_lite_settings |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.854 s |
Memory usage | 2.84 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.173 s |
Memory usage | 3.16 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.394 s | 0.740 s | +0.346 s | 2.82 MiB | 2.92 MiB | + 94.38 KiB |
/wp-admin/edit.php | 0.221 s | 0.338 s | +0.117 s | 2.85 MiB | 2.94 MiB | + 93.63 KiB |
/wp-admin/post-new.php | 0.830 s | 1.082 s | +0.252 s | 5.21 MiB | 5.32 MiB | + 113.39 KiB |
/wp-admin/upload.php | 0.707 s | 0.391 s | -0.316 s | 2.77 MiB | 2.84 MiB | + 77.7 KiB |
/wp-admin/options-writing.php | 0.237 s | 0.200 s | -0.037 s | 2.76 MiB | 2.83 MiB | + 69.67 KiB |
/wp-admin/media-new.php | 0.287 s | 0.270 s | -0.017 s | 2.74 MiB | 2.83 MiB | + 88.84 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.226 s | 0.199 s | -0.027 s | 2.76 MiB | 2.85 MiB | + 95.55 KiB |
/wp-admin/post-new.php?post_type=page | 0.684 s | 0.790 s | +0.106 s | 5.21 MiB | 5.31 MiB | + 109.45 KiB |
/wp-admin/options-discussion.php | 0.246 s | 0.348 s | +0.102 s | 2.75 MiB | 2.82 MiB | + 78.2 KiB |
/wp-admin/edit-comments.php | 0.449 s | 0.235 s | -0.214 s | 2.78 MiB | 2.85 MiB | + 76.97 KiB |
/ | 0.300 s | 0.219 s | -0.081 s | 3.13 MiB | 3.16 MiB | + 35.01 KiB |
Average | 0.416 s | 0.437 s | +0.021 s | 3.25 MiB | 3.34 MiB | + 84.8 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 | |
---|---|---|---|---|---|
SVG | 73.9% | 59,315 | 797 | 802 | |
PHP | 10.4% | 8,317 | 1,257 | 74 | |
CSS | 10.0% | 7,996 | 775 | 6 | |
JavaScript | 5.0% | 4,049 | 373 | 7 | |
PO File | 0.4% | 324 | 180 | 1 | |
Sass | 0.1% | 95 | 0 | 1 | |
Markdown | 0.1% | 82 | 0 | 1 | |
JSON | 0.1% | 41 | 0 | 2 | |
Python | 0.0% | 17 | 5 | 1 | |
HTML | 0.0% | 1 | 0 | 1 | |
Total | 80,237 | 3,387 | 896 |
Lines of code | 8,911 |
---|---|
Total complexity | 2,077 |
Median class complexity | 11.0 |
Median method complexity | 2.0 |
Most complex class | CSF |
Most complex function | csf_get_google_fonts() |
Classes | 81 |
---|---|
Methods | 326 |
Functions | 21 |
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.
wp_options
4The log file is empty.