WP Call Button 1.2.0

Does WP Call Button work with WordPress 5.8 and PHP 7.4.8? A smoke test was performed on .

Summary

Errors
1PHP notices
3JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

Memory usage: 42.41 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.

Environment
WordPress version5.8
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs 40,000+
WordPress.org page https://wordpress.org/plugins/wp-call-button/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 4

Plugins ‹ Test site — WordPress

Page screenshot: Plugins ‹ Test site — WordPress
URL /wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL /wp-admin/plugins.php?action=activate&plugin=wp-call-button%2Fwp-call-button.php&plugin_status=all&paged=1&s&_wpnonce=d9478c0499
Aspect after-activation
HTTP status 200
Load time 0.396 s
Memory usage 3.11 MiB
JS errors None
Resource errors None

Settings → WP Call Button

Page screenshot: Settings → WP Call Button
URL /wp-admin/options-general.php?page=wp-call-button
Aspect menu-item
HTTP status 200
Load time 0.496 s
Memory usage 3.15 MiB
JS errors None
Resource errors None

Test site – Just another WordPress site

Page screenshot: Test site – Just another WordPress site
URL /
Aspect front-page
HTTP status 200
Load time 0.217 s
Memory usage 2.93 MiB
JS errors None
Resource errors None

Widgets ‹ Test site — WordPress

Page screenshot: Widgets ‹ Test site — WordPress
URL /wp-admin/widgets.php
Aspect new-sidebar-widgets
HTTP status 200
Load time 1.965 s
Memory usage 4.51 MiB
JS errors
[
    {
        "message": "TypeError: Cannot read property 'top' of undefined\n    at belowEntryMetaClass (/wp-content/themes/twentyseventeen/assets/js/global.js?ver=20190121:124:33)\n    at HTMLDocument.<anonymous> (/wp-content/themes/twentyseventeen/assets/js/global.js?ver=20190121:211:3)\n    at e (/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils&ver=5.8:2:30038)\n    at t (/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils&ver=5.8:2:30340)",
        "trace": null,
        "code": null
    },
    {
        "message": "TypeError: Cannot read property 'top' of undefined\n    at belowEntryMetaClass (/wp-content/themes/twentyseventeen/assets/js/global.js?ver=20190121:124:33)\n    at HTMLDocument.<anonymous> (/wp-content/themes/twentyseventeen/assets/js/global.js?ver=20190121:211:3)\n    at e (/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils&ver=5.8:2:30038)\n    at t (/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils&ver=5.8:2:30340)",
        "trace": null,
        "code": null
    },
    {
        "message": "TypeError: Cannot read property 'top' of undefined\n    at belowEntryMetaClass (/wp-content/themes/twentyseventeen/assets/js/global.js?ver=20190121:124:33)\n    at HTMLDocument.<anonymous> (/wp-content/themes/twentyseventeen/assets/js/global.js?ver=20190121:211:3)\n    at e (/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils&ver=5.8:2:30038)\n    at t (/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils&ver=5.8:2:30340)",
        "trace": null,
        "code": null
    }
]
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.333 s0.281 s-0.052 s3.08 MiB3.12 MiB+ 43.07 KiB
/wp-admin/edit.php0.178 s0.201 s+0.023 s3.11 MiB3.22 MiB+ 107.07 KiB
/wp-admin/post-new.php1.198 s1.167 s-0.031 s5.27 MiB5.32 MiB+ 54.66 KiB
/wp-admin/upload.php0.546 s0.327 s-0.219 s3.03 MiB3.07 MiB+ 41.94 KiB
/wp-admin/options-writing.php0.178 s0.133 s-0.045 s3.02 MiB3.05 MiB+ 25.91 KiB
/wp-admin/media-new.php0.255 s0.182 s-0.073 s3.01 MiB3.05 MiB+ 42.11 KiB
/wp-admin/edit-tags.php?taxonomy=category0.222 s0.178 s-0.044 s3.04 MiB3.08 MiB+ 43.02 KiB
/wp-admin/post-new.php?post_type=page0.927 s1.078 s+0.151 s5.26 MiB5.3 MiB+ 50.24 KiB
/wp-admin/options-discussion.php0.221 s0.272 s+0.051 s3 MiB3.05 MiB+ 42.73 KiB
/wp-admin/edit-comments.php0.228 s0.201 s-0.027 s3.04 MiB3.08 MiB+ 41.92 KiB
/0.269 s0.248 s-0.021 s2.96 MiB2.93 MiB- 26.16 KiB
Average 0.414 s0.388 s-0.026 s3.44 MiB3.48 MiB+ 42.41 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.

JavaScript
PHP
CSS
Language % Lines of code Comment lines Files
JavaScript43.9%1,4892245
PHP41.1%1,39655116
CSS14.9%506113
SVG0.1%202
Total 3,393 786 26

PHP Code Analysis | More results »

Lines of code 993
Total complexity 220
Median class complexity 26.0
Median method complexity 2.0
Most complex class WpCallButton\Plugin\WpCallButtonAdmin
Most complex function WpCallButton\Plugin\WpCallButtonAdmin::hide_unrelated_notices()
Classes 7
Methods 49
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.

Options wp_options 2

Sidebar Widgets 1

ID Name
wp-call-button-widget-main-aWP Call Button

PHP Error Log 1 lines

[21-Jul-2021 11:32:40 UTC] PHP Notice:  wp_enqueue_script() was called <strong>incorrectly</strong>. "wp-editor" script should not be enqueued together with the new widgets editor (wp-edit-widgets or wp-customize-widgets). 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.8.0.) in /wp-includes/functions.php on line 5535
See also: All tests for this plugin, How to Hide the "WP Call Button" Admin Menu