Mobile Menu 2.8.1.8.1

Does Mobile Menu work with WordPress 5.7.1 and PHP 7.4.8? A smoke test was performed on .

Summary

Errors
22PHP notices
1JavaScript exceptions
All test pages loaded successfully
2Resource errors (CSS, JS, images, fonts and so on.)
  • 2 net::ERR_NAME_NOT_RESOLVED
Performance

Memory usage: 764.58 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

Page speed impact: 0.031 seconds
The average page load time increased by this amount after activating the plugin.

Environment
WordPress version5.7.1
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs 100,000+
WordPress.org page https://wordpress.org/plugins/mobile-menu/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 17

Mobile Menu Options ‹ Test site — WordPress

Page screenshot: Mobile Menu Options ‹ Test site — WordPress
URL /wp-admin/admin.php?page=mobile-menu-options
Requested URL /wp-admin/plugins.php?action=activate&plugin=mobile-menu%2Fmobmenu.php&plugin_status=all&paged=1&s&_wpnonce=72245b72cb
Aspect after-activation
HTTP status 200
Load time 1.742 s
Memory usage 5.77 MiB
JS errors None
Resource errors None

Mobile Menu Options

Page screenshot: Mobile Menu Options
URL /wp-admin/admin.php?page=mobile-menu-options
Aspect menu-item
HTTP status 200
Load time 0.348 s
Memory usage 3.83 MiB
JS errors None
Resource errors None

Mobile Menu Options → HeaderHeader OptionsLogo

Page screenshot: Mobile Menu Options → HeaderHeader OptionsLogo
URL /wp-admin/admin.php?page=mobile-menu-options&tab=header
Aspect menu-item-tab
HTTP status 200
Load time 0.314 s
Memory usage 3.83 MiB
JS errors None
Resource errors None

Mobile Menu Options → Footer

Page screenshot: Mobile Menu Options → Footer
URL /wp-admin/admin.php?page=mobile-menu-options&tab=footer
Aspect menu-item-tab
HTTP status 200
Load time 0.292 s
Memory usage 3.83 MiB
JS errors None
Resource errors None

Mobile Menu Options → Left MenuMenu IconLeft Panel

Page screenshot: Mobile Menu Options → Left MenuMenu IconLeft Panel
URL /wp-admin/admin.php?page=mobile-menu-options&tab=left-menu
Aspect menu-item-tab
HTTP status 200
Load time 0.433 s
Memory usage 3.83 MiB
JS errors None
Resource errors
[
    {
        "status": null,
        "statusText": null,
        "url": "http://menu/",
        "errorString": "net::ERR_NAME_NOT_RESOLVED"
    }
]

Mobile Menu Options → Right MenuMenu IconRight Panel

Page screenshot: Mobile Menu Options → Right MenuMenu IconRight Panel
URL /wp-admin/admin.php?page=mobile-menu-options&tab=right-menu
Aspect menu-item-tab
HTTP status 200
Load time 0.381 s
Memory usage 3.83 MiB
JS errors None
Resource errors
[
    {
        "status": null,
        "statusText": null,
        "url": "http://menu/",
        "errorString": "net::ERR_NAME_NOT_RESOLVED"
    }
]

Mobile Menu Options → Woocommerce

Page screenshot: Mobile Menu Options → Woocommerce
URL /wp-admin/admin.php?page=mobile-menu-options&tab=woocommerce
Aspect menu-item-tab
HTTP status 200
Load time 0.296 s
Memory usage 3.83 MiB
JS errors None
Resource errors None

Mobile Menu Options → ColorsGeneralHeaderLeft MenuRight Menu3rd Level Menu

Page screenshot: Mobile Menu Options → ColorsGeneralHeaderLeft MenuRight Menu3rd Level Menu
URL /wp-admin/admin.php?page=mobile-menu-options&tab=colors
Aspect menu-item-tab
HTTP status 200
Load time 0.638 s
Memory usage 3.83 MiB
JS errors None
Resource errors None

Mobile Menu Options → Fonts

Page screenshot: Mobile Menu Options → Fonts
URL /wp-admin/admin.php?page=mobile-menu-options&tab=fonts
Aspect menu-item-tab
HTTP status 200
Load time 0.573 s
Memory usage 3.83 MiB
JS errors None
Resource errors None

Mobile Menu Options → Documentation

Page screenshot: Mobile Menu Options → Documentation
URL /wp-admin/admin.php?page=mobile-menu-options&tab=documentation
Aspect menu-item-tab
HTTP status 200
Load time 5.000 s
Memory usage 3.83 MiB
JS errors
[
    {
        "message": "Error: Bootstrap's JavaScript requires jQuery version 1.9.1 or higher, but lower than version 3\n    at https://www.wpmobilemenu.com/wp-content/themes/uplift/js/lib/bootstrap.min.js:11:216\n    at https://www.wpmobilemenu.com/wp-content/themes/uplift/js/lib/bootstrap.min.js:11:318",
        "trace": null,
        "code": null
    }
]
Resource errors None

Mobile Menu Options → Affiliation

Page screenshot: Mobile Menu Options → Affiliation
URL /wp-admin/admin.php?page=mobile-menu-options-affiliation
Aspect menu-item
HTTP status 200
Load time 0.737 s
Memory usage 3.7 MiB
JS errors None
Resource errors None

Mobile Menu Options → Contact Us

Page screenshot: Mobile Menu Options → Contact Us
URL /wp-admin/admin.php?page=mobile-menu-options-contact
Aspect menu-item
HTTP status 200
Load time 1.107 s
Memory usage 3.51 MiB
JS errors None
Resource errors None

Mobile Menu Options → Support Forum

Page screenshot: Mobile Menu Options → Support Forum
URL https://wordpress.org/support/plugin/mobile-menu/
Requested URL /wp-admin/admin.php?page=mobile-menu-options-wp-support-forum
Aspect menu-item
HTTP status 200
Load time 1.472 s
Memory usage N/A
JS errors None
Resource errors None

Mobile Menu Options → Upgrade  ➤

Page screenshot: Mobile Menu Options → Upgrade  ➤
URL /wp-admin/admin.php?page=mobile-menu-options-pricing
Aspect menu-item
HTTP status 200
Load time 1.410 s
Memory usage 3.81 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.298 s
Memory usage 3.63 MiB
JS errors None
Resource errors None

Add New Post ‹ Test site — WordPress

Page screenshot: Add New Post ‹ Test site — WordPress
URL /wp-admin/post-new.php
Aspect new-meta-boxes
HTTP status 200
Load time 0.759 s
Memory usage 5.73 MiB
JS errors None
Resource errors None

Add New Page ‹ Test site — WordPress

Page screenshot: Add New Page ‹ Test site — WordPress
URL /wp-admin/post-new.php?post_type=page
Aspect new-meta-boxes
HTTP status 200
Load time 0.669 s
Memory usage 5.71 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.269 s0.442 s+0.173 s2.82 MiB3.52 MiB+ 719.77 KiB
/wp-admin/edit.php0.187 s0.327 s+0.140 s2.86 MiB3.57 MiB+ 728.11 KiB
/wp-admin/post-new.php0.946 s0.940 s-0.006 s5.02 MiB5.73 MiB+ 723.63 KiB
/wp-admin/upload.php0.561 s0.287 s-0.274 s2.7 MiB3.45 MiB+ 768.6 KiB
/wp-admin/options-writing.php0.163 s0.234 s+0.071 s2.71 MiB3.45 MiB+ 757.25 KiB
/wp-admin/media-new.php0.216 s0.463 s+0.247 s2.67 MiB3.45 MiB+ 791.83 KiB
/wp-admin/edit-tags.php?taxonomy=category0.222 s0.349 s+0.127 s2.77 MiB3.48 MiB+ 726.29 KiB
/wp-admin/post-new.php?post_type=page0.944 s0.667 s-0.277 s5.01 MiB5.71 MiB+ 719.63 KiB
/wp-admin/options-discussion.php0.315 s0.402 s+0.087 s2.67 MiB3.45 MiB+ 794.13 KiB
/wp-admin/edit-comments.php0.247 s0.314 s+0.067 s2.78 MiB3.49 MiB+ 732.44 KiB
/0.279 s0.269 s-0.010 s2.71 MiB3.63 MiB+ 948.7 KiB
Average 0.395 s0.427 s+0.031 s3.16 MiB3.9 MiB+ 764.58 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.

PHP
Language % Lines of code Comment lines Files
PHP88.3%44,24919,332164
CSS5.0%2,48817926
JavaScript3.3%1,6363689
PO File2.0%1,0236291
Markdown1.1%55602
SVG0.2%8001
YAML0.1%3652
JSON0.1%2801
Total 50,096 20,513 206

PHP Code Analysis | More results »

Lines of code 34,476
Total complexity 7,737
Median class complexity 10.0
Median method complexity 2.0
Most complex class Freemius
Most complex function FS_Plugin_Info_Dialog::install_plugin_information()
Classes 121
Methods 1,669
Functions 123

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 6

Meta Boxes

{
    "post": {
        "wp-mobile-menu-meta-options": {
            "title": "WP Mobile Menu Meta options",
            "context": "normal"
        }
    },
    "page": {
        "wp-mobile-menu-meta-options": {
            "title": "WP Mobile Menu Meta options",
            "context": "normal"
        }
    }
}

PHP Error Log 22 lines

[15-Apr-2021 07:27:35 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:35 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:36 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:36 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:38 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:38 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:39 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:39 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:40 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:40 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:40 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:40 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:41 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:41 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:42 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:42 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:42 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:42 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:44 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:44 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:46 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
[15-Apr-2021 07:27:46 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5313
See also: All tests for this plugin, How to Hide Mobile Menu Admin Menus