Mobile Menu 2.8.2

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

Summary

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

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

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=75a5b2cde6
Aspect after-activation
HTTP status 200
Load time 2.945 s
Memory usage 5.68 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.664 s
Memory usage 3.75 MiB
JS errors None
Resource errors
[
    {
        "status": null,
        "statusText": null,
        "url": "http://menu/",
        "errorString": "net::ERR_NAME_NOT_RESOLVED"
    },
    {
        "status": null,
        "statusText": null,
        "url": "http://menu/",
        "errorString": "net::ERR_NAME_NOT_RESOLVED"
    }
]

Mobile Menu Options → General OptionsGetting startedVisibility optionsHide Theme MenuMiscelaneous OptionsAdvanced OptionsFont OptionsImport and ExportAlerts

Page screenshot: Mobile Menu Options → General OptionsGetting startedVisibility optionsHide Theme MenuMiscelaneous OptionsAdvanced OptionsFont OptionsImport and ExportAlerts
URL /wp-admin/admin.php?page=mobile-menu-options
Aspect menu-item-tab
HTTP status 200
Load time 0.611 s
Memory usage 3.75 MiB
JS errors None
Resource errors
[
    {
        "status": null,
        "statusText": null,
        "url": "http://menu/",
        "errorString": "net::ERR_NAME_NOT_RESOLVED"
    },
    {
        "status": null,
        "statusText": null,
        "url": "http://menu/",
        "errorString": "net::ERR_NAME_NOT_RESOLVED"
    }
]

Mobile Menu Options → HeaderHeader OptionsLogo

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

Mobile Menu Options → Footer

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

Mobile Menu Options → Left MenuMain OptionsMenu IconLeft Panel

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

Mobile Menu Options → Right MenuMain OptionsMenu IconRight Panel

Page screenshot: Mobile Menu Options → Right MenuMain OptionsMenu IconRight Panel
URL /wp-admin/admin.php?page=mobile-menu-options
Aspect menu-item-tab
HTTP status 200
Load time 0.490 s
Memory usage 3.75 MiB
JS errors None
Resource errors
[
    {
        "status": null,
        "statusText": null,
        "url": "http://menu/",
        "errorString": "net::ERR_NAME_NOT_RESOLVED"
    },
    {
        "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
Aspect menu-item-tab
HTTP status 200
Load time 0.489 s
Memory usage 3.75 MiB
JS errors None
Resource errors
[
    {
        "status": null,
        "statusText": null,
        "url": "http://menu/",
        "errorString": "net::ERR_NAME_NOT_RESOLVED"
    },
    {
        "status": null,
        "statusText": null,
        "url": "http://menu/",
        "errorString": "net::ERR_NAME_NOT_RESOLVED"
    }
]

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
Aspect menu-item-tab
HTTP status 200
Load time 0.570 s
Memory usage 3.75 MiB
JS errors None
Resource errors
[
    {
        "status": null,
        "statusText": null,
        "url": "http://menu/",
        "errorString": "net::ERR_NAME_NOT_RESOLVED"
    },
    {
        "status": null,
        "statusText": null,
        "url": "http://menu/",
        "errorString": "net::ERR_NAME_NOT_RESOLVED"
    }
]

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 1.165 s
Memory usage 3.62 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 0.154 s
Memory usage 3.44 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.263 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.435 s
Memory usage 3.73 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.291 s
Memory usage 3.55 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.262 s0.446 s+0.184 s2.82 MiB3.45 MiB+ 645.69 KiB
/wp-admin/edit.php0.176 s0.227 s+0.051 s2.86 MiB3.5 MiB+ 650.02 KiB
/wp-admin/post-new.php0.902 s1.072 s+0.170 s5.03 MiB5.67 MiB+ 658.95 KiB
/wp-admin/upload.php0.487 s0.290 s-0.197 s2.7 MiB3.4 MiB+ 716.41 KiB
/wp-admin/options-writing.php0.257 s0.155 s-0.102 s2.71 MiB3.37 MiB+ 675.14 KiB
/wp-admin/media-new.php0.198 s0.171 s-0.027 s2.67 MiB3.37 MiB+ 717.2 KiB
/wp-admin/edit-tags.php?taxonomy=category0.180 s0.273 s+0.093 s2.77 MiB3.41 MiB+ 649.71 KiB
/wp-admin/post-new.php?post_type=page1.211 s1.095 s-0.116 s5.01 MiB5.65 MiB+ 654.95 KiB
/wp-admin/options-discussion.php0.305 s0.264 s-0.041 s2.68 MiB3.37 MiB+ 712.02 KiB
/wp-admin/edit-comments.php0.240 s0.266 s+0.026 s2.78 MiB3.41 MiB+ 651.16 KiB
/0.262 s0.240 s-0.022 s2.65 MiB3.55 MiB+ 921.88 KiB
Average 0.407 s0.409 s+0.002 s3.15 MiB3.83 MiB+ 695.74 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.4%42,53318,611159
CSS4.7%2,28212120
JavaScript3.5%1,6903689
PO File2.1%1,0236291
Markdown1.2%55602
JSON0.1%2801
Total 48,112 19,729 192

PHP Code Analysis | More results »

Lines of code 32,731
Total complexity 7,445
Median class complexity 12.0
Median method complexity 2.0
Most complex class Freemius
Most complex function FS_Plugin_Info_Dialog::install_plugin_information()
Classes 98
Methods 1,591
Functions 102

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

PHP Error Log 20 lines

[03-May-2021 09:26:52 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
[03-May-2021 09:26:52 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
[03-May-2021 09:26:53 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
[03-May-2021 09:26:53 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
[03-May-2021 09:26:55 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
[03-May-2021 09:26:55 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
[03-May-2021 09:26:58 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
[03-May-2021 09:26:58 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
[03-May-2021 09:27:00 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
[03-May-2021 09:27:00 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
[03-May-2021 09:27:03 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
[03-May-2021 09:27:03 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
[03-May-2021 09:27:05 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
[03-May-2021 09:27:05 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
[03-May-2021 09:27:08 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
[03-May-2021 09:27:08 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
[03-May-2021 09:27:10 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
[03-May-2021 09:27:10 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
[03-May-2021 09:27:12 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
[03-May-2021 09:27:12 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