Does Split Test For Elementor work with WordPress 6.1.1 and PHP 7.4.8? A smoke test was performed on .
4 | PHP notices |
2 | PHP deprecation warnings |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 59.13 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.1.1 |
---|---|
PHP version | 7.4.8 |
MySQL version | 8.0.21 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | 4,000+ |
WordPress.org page | https://wordpress.org/plugins/split-test-for-elementor/ |
Badges |
|
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=split-test-for-elementor%2Fplugin.php&plugin_status=all&paged=1&s&_wpnonce=90f00ee9cf |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.369 s |
Memory usage | 3.54 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=splittest-for-elementor |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.266 s |
Memory usage | 3.59 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/options-general.php?page=split-test-for-elementor |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.127 s |
Memory usage | 3.43 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.197 s |
Memory usage | 3.46 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.310 s | 0.251 s | -0.059 s | 3.54 MiB | 3.59 MiB | + 53.27 KiB |
/wp-admin/edit.php | 0.163 s | 0.183 s | +0.020 s | 3.57 MiB | 3.63 MiB | + 55.07 KiB |
/wp-admin/post-new.php | 0.748 s | 0.607 s | -0.141 s | 5.46 MiB | 5.53 MiB | + 68.44 KiB |
/wp-admin/upload.php | 0.488 s | 0.270 s | -0.218 s | 3.41 MiB | 3.52 MiB | + 116.15 KiB |
/wp-admin/options-writing.php | 0.165 s | 0.270 s | +0.105 s | 3.4 MiB | 3.44 MiB | + 34.62 KiB |
/wp-admin/media-new.php | 0.244 s | 0.214 s | -0.030 s | 3.38 MiB | 3.5 MiB | + 116.32 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.399 s | 0.185 s | -0.214 s | 3.48 MiB | 3.53 MiB | + 53.23 KiB |
/wp-admin/post-new.php?post_type=page | 0.581 s | 0.844 s | +0.263 s | 5.46 MiB | 5.51 MiB | + 58.68 KiB |
/wp-admin/options-discussion.php | 0.218 s | 0.212 s | -0.006 s | 3.38 MiB | 3.44 MiB | + 52.63 KiB |
/wp-admin/edit-comments.php | 0.201 s | 0.200 s | -0.001 s | 3.48 MiB | 3.53 MiB | + 52.17 KiB |
/ | 0.261 s | 0.223 s | -0.038 s | 3.46 MiB | 3.46 MiB | - 10.15 KiB |
Average | 0.343 s | 0.314 s | -0.029 s | 3.82 MiB | 3.88 MiB | + 59.13 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 | 95.9% | 6,918 | 3,410 | 117 | |
CSS | 4.1% | 299 | 0 | 1 | |
Total | 7,217 | 3,410 | 118 |
Lines of code | 4,873 |
---|---|
Total complexity | 1,104 |
Median class complexity | 8.5 |
Median method complexity | 1.0 |
Most complex class | SplitTestForElementor\Libs\Carbon\Carbon |
Most complex function | SplitTestForElementor\Libs\Carbon\Carbon::diffForHumans() |
Classes | 46 |
---|---|
Methods | 472 |
Functions | 2 |
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
2wp_usermeta
1[17-Nov-2022 12:26:08 UTC] PHP Deprecated: Function screen_icon is <strong>deprecated</strong> since version 3.8.0 with no alternative available. in /wp-includes/functions.php on line 5393
[17-Nov-2022 12:26:08 UTC] PHP Deprecated: Function get_screen_icon is <strong>deprecated</strong> since version 3.8.0 with no alternative available. in /wp-includes/functions.php on line 5393
[17-Nov-2022 12:26:10 UTC] PHP Notice: Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>splitTestForElementor/v1/tests</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835
[17-Nov-2022 12:26:10 UTC] PHP Notice: Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>splitTestForElementor/v1/variations</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835
[17-Nov-2022 12:26:13 UTC] PHP Notice: Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>splitTestForElementor/v1/tests</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835
[17-Nov-2022 12:26:13 UTC] PHP Notice: Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>splitTestForElementor/v1/variations</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835