Does Split Test For Elementor work with WordPress 6.0 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: 61.94 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.127 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 6.0 |
---|---|
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=1670ebc6b9 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.858 s |
Memory usage | 3.74 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.423 s |
Memory usage | 3.87 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.254 s |
Memory usage | 3.7 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.220 s |
Memory usage | 3.59 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.331 s | 0.380 s | +0.049 s | 3.72 MiB | 3.77 MiB | + 51.41 KiB |
/wp-admin/edit.php | 0.213 s | 0.327 s | +0.114 s | 3.75 MiB | 3.8 MiB | + 52.89 KiB |
/wp-admin/post-new.php | 0.728 s | 1.107 s | +0.379 s | 5.53 MiB | 5.6 MiB | + 66.57 KiB |
/wp-admin/upload.php | 0.488 s | 0.548 s | +0.060 s | 3.68 MiB | 3.73 MiB | + 50.27 KiB |
/wp-admin/options-writing.php | 0.145 s | 0.330 s | +0.185 s | 3.61 MiB | 3.71 MiB | + 94.59 KiB |
/wp-admin/media-new.php | 0.403 s | 0.322 s | -0.081 s | 3.66 MiB | 3.71 MiB | + 50.45 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.213 s | 0.414 s | +0.201 s | 3.68 MiB | 3.73 MiB | + 51.35 KiB |
/wp-admin/post-new.php?post_type=page | 0.590 s | 0.758 s | +0.168 s | 5.53 MiB | 5.58 MiB | + 56.84 KiB |
/wp-admin/options-discussion.php | 0.207 s | 0.456 s | +0.249 s | 3.59 MiB | 3.7 MiB | + 114.76 KiB |
/wp-admin/edit-comments.php | 0.212 s | 0.332 s | +0.120 s | 3.69 MiB | 3.74 MiB | + 50.3 KiB |
/ | 0.256 s | 0.207 s | -0.049 s | 3.55 MiB | 3.59 MiB | + 41.95 KiB |
Average | 0.344 s | 0.471 s | +0.127 s | 4 MiB | 4.06 MiB | + 61.94 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.8% | 6,881 | 3,411 | 117 | |
CSS | 4.2% | 299 | 0 | 1 | |
Total | 7,180 | 3,411 | 118 |
Lines of code | 4,836 |
---|---|
Total complexity | 1,095 |
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 | 470 |
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
2[05-Jul-2022 08:35:14 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 5389
[05-Jul-2022 08:35:14 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 5389
[05-Jul-2022 08:35:16 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 5831
[05-Jul-2022 08:35:16 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 5831
[05-Jul-2022 08:35:20 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 5831
[05-Jul-2022 08:35:20 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 5831