Mobile Menu 2.8.2.4

Does Mobile Menu work with WordPress 5.8.2 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: 723.05 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.2
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=d47dc9f290
Aspect after-activation
HTTP status 200
Load time 1.790 s
Memory usage 5.99 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.920 s
Memory usage 4.06 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 MenuMiscellaneous OptionsAdvanced OptionsFont OptionsImport and ExportAlerts

Page screenshot: Mobile Menu Options → General OptionsGetting startedVisibility optionsHide Theme MenuMiscellaneous OptionsAdvanced OptionsFont OptionsImport and ExportAlerts
URL /wp-admin/admin.php?page=mobile-menu-options
Aspect menu-item-tab
HTTP status 200
Load time 0.715 s
Memory usage 4.06 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.704 s
Memory usage 4.06 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.640 s
Memory usage 4.06 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.679 s
Memory usage 4.06 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.605 s
Memory usage 4.06 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.632 s
Memory usage 4.06 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.679 s
Memory usage 4.06 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.038 s
Memory usage 3.93 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.76 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.504 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.152 s
Memory usage 4.05 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.371 s
Memory usage 3.87 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.320 s0.442 s+0.122 s3.08 MiB3.78 MiB+ 713.7 KiB
/wp-admin/edit.php0.175 s0.203 s+0.028 s3.11 MiB3.81 MiB+ 715.23 KiB
/wp-admin/post-new.php0.925 s1.239 s+0.314 s5.27 MiB5.9 MiB+ 652.46 KiB
/wp-admin/upload.php0.618 s0.332 s-0.286 s3.03 MiB3.73 MiB+ 720.38 KiB
/wp-admin/options-writing.php0.144 s0.145 s+0.001 s3.02 MiB3.7 MiB+ 695.11 KiB
/wp-admin/media-new.php0.309 s0.202 s-0.107 s3.01 MiB3.71 MiB+ 721.17 KiB
/wp-admin/edit-tags.php?taxonomy=category0.180 s0.241 s+0.061 s3.04 MiB3.74 MiB+ 717.68 KiB
/wp-admin/post-new.php?post_type=page0.883 s0.877 s-0.006 s5.26 MiB5.89 MiB+ 648.46 KiB
/wp-admin/options-discussion.php0.225 s0.414 s+0.189 s3 MiB3.7 MiB+ 715.98 KiB
/wp-admin/edit-comments.php0.213 s0.283 s+0.070 s3.04 MiB3.74 MiB+ 719.13 KiB
/0.726 s0.267 s-0.459 s2.96 MiB3.87 MiB+ 934.31 KiB
Average 0.429 s0.422 s-0.007 s3.44 MiB4.14 MiB+ 723.05 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%42,54818,594159
CSS4.8%2,31512120
JavaScript3.5%1,7043689
PO File2.1%1,0236291
Markdown1.2%55602
JSON0.1%2801
Total 48,174 19,712 192

PHP Code Analysis | More results »

Lines of code 32,746
Total complexity 7,446
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

[10-Nov-2021 21:56: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 5663
[10-Nov-2021 21:56: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 5663
[10-Nov-2021 21:56:56 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 5663
[10-Nov-2021 21:56:56 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 5663
[10-Nov-2021 21:56: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 5663
[10-Nov-2021 21:56:59 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 5663
[10-Nov-2021 21:57:01 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 5663
[10-Nov-2021 21:57:01 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 5663
[10-Nov-2021 21:57: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 5663
[10-Nov-2021 21:57: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 5663
[10-Nov-2021 21:57:06 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 5663
[10-Nov-2021 21:57:06 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 5663
[10-Nov-2021 21:57: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 5663
[10-Nov-2021 21:57: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 5663
[10-Nov-2021 21:57:11 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 5663
[10-Nov-2021 21:57:11 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 5663
[10-Nov-2021 21:57:13 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 5663
[10-Nov-2021 21:57:13 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 5663
[10-Nov-2021 21:57:16 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 5663
[10-Nov-2021 21:57:16 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 5663
See also: All tests for this plugin, How to Hide Mobile Menu Admin Menus