Futy.io Leadbots 2.0.2
Does Futy.io Leadbots work with WordPress 5.8.2 and PHP 7.4.8? A smoke test was performed on .
Summary
Errors
| 20 | PHP notices |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Performance
Memory usage: 24.56 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.270 seconds
The average page load time increased by this amount after activating the plugin.
Environment
| WordPress version | 5.8.2 |
|---|---|
| PHP version | 7.4.8 |
| MySQL version | 8.0.21 |
| PHP memory limit | 256M |
Plugin Info
| Last updated | |
|---|---|
| Active installs | 2,000+ |
| WordPress.org page | https://wordpress.org/plugins/futy-widget/ |
| Badges |
|
Pages 3
Plugins ‹ Test site — WordPress
| URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=futy-widget%2Ffuty-widget.php&plugin_status=all&paged=1&s&_wpnonce=3be0f85a88 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.841 s |
| Memory usage | 3.06 MiB |
| JS errors | None |
| Resource errors | None |
Futy.io
| URL | /wp-admin/admin.php?page=futy |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.878 s |
| Memory usage | 3.06 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.289 s |
| Memory usage | 2.91 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.279 s | 0.610 s | +0.331 s | 3.08 MiB | 3.16 MiB | + 82.55 KiB |
| /wp-admin/edit.php | 0.168 s | 0.513 s | +0.345 s | 3.11 MiB | 3.2 MiB | + 85.22 KiB |
| /wp-admin/post-new.php | 0.717 s | 1.245 s | +0.528 s | 5.27 MiB | 5.29 MiB | + 19.62 KiB |
| /wp-admin/upload.php | 0.351 s | 0.758 s | +0.407 s | 3.03 MiB | 3.05 MiB | + 22.89 KiB |
| /wp-admin/options-writing.php | 0.238 s | 0.478 s | +0.240 s | 3.02 MiB | 3.03 MiB | + 1.37 KiB |
| /wp-admin/media-new.php | 0.372 s | 0.550 s | +0.178 s | 3.01 MiB | 3.03 MiB | + 23.69 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.174 s | 0.503 s | +0.329 s | 3.04 MiB | 3.06 MiB | + 23.97 KiB |
| /wp-admin/post-new.php?post_type=page | 0.910 s | 1.047 s | +0.137 s | 5.26 MiB | 5.27 MiB | + 14.58 KiB |
| /wp-admin/options-discussion.php | 0.217 s | 0.607 s | +0.390 s | 3 MiB | 3.02 MiB | + 18.81 KiB |
| /wp-admin/edit-comments.php | 0.258 s | 0.528 s | +0.270 s | 3.04 MiB | 3.06 MiB | + 22.31 KiB |
| / | 0.373 s | 0.192 s | -0.181 s | 2.96 MiB | 2.91 MiB | - 44.82 KiB |
| Average | 0.369 s | 0.639 s | +0.270 s | 3.44 MiB | 3.46 MiB | + 24.56 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.
| Language | % | Lines of code | Comment lines | Files | |
|---|---|---|---|---|---|
| PHP | 66.0% | 204 | 69 | 4 | |
| PO File | 24.9% | 77 | 21 | 1 | |
| JavaScript | 7.1% | 22 | 0 | 2 | |
| CSS | 1.9% | 6 | 0 | 1 | |
| Total | 309 | 90 | 8 | ||
PHP Code Analysis | More results »
| Lines of code | 145 |
|---|---|
| Total complexity | 27 |
| Median class complexity | 13.0 |
| Median method complexity | 2.0 |
| Most complex class | FutyWidgetSettings |
| Most complex function | FutyWidgetSettings::options_page_render() |
| Classes | 2 |
|---|---|
| Methods | 9 |
| Functions | 1 |
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.
No new entries found.
PHP Error Log 20 lines
[14-Nov-2021 08:15:06 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:07 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:07 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:09 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:10 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:10 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:10 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:12 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:12 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:13 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:13 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:14 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:14 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:15 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:17 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:17 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:17 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:18 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:19 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663
[14-Nov-2021 08:15:19 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>my-css</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5663