Mobile Menu 2.8.2.2

Does Mobile Menu work with WordPress 5.8 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: 722.95 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

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

Environment
WordPress version5.8
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=fa555af74e
Aspect after-activation
HTTP status 200
Load time 3.053 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.548 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 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.656 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.582 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.620 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.656 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.575 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.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 → 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.668 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.081 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.158 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.238 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.207 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.315 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.365 s0.540 s+0.175 s3.08 MiB3.78 MiB+ 713.77 KiB
/wp-admin/edit.php0.223 s0.246 s+0.023 s3.11 MiB3.81 MiB+ 715.3 KiB
/wp-admin/post-new.php1.467 s1.915 s+0.448 s5.27 MiB5.9 MiB+ 652.53 KiB
/wp-admin/upload.php0.615 s0.507 s-0.108 s3.03 MiB3.73 MiB+ 720.45 KiB
/wp-admin/options-writing.php0.197 s0.298 s+0.101 s3.02 MiB3.7 MiB+ 695.18 KiB
/wp-admin/media-new.php0.293 s0.254 s-0.039 s3.01 MiB3.71 MiB+ 721.24 KiB
/wp-admin/edit-tags.php?taxonomy=category0.255 s0.217 s-0.038 s3.04 MiB3.74 MiB+ 717.75 KiB
/wp-admin/post-new.php?post_type=page1.544 s1.584 s+0.040 s5.26 MiB5.89 MiB+ 648.53 KiB
/wp-admin/options-discussion.php0.304 s0.310 s+0.006 s3 MiB3.7 MiB+ 716.05 KiB
/wp-admin/edit-comments.php0.227 s0.256 s+0.029 s3.04 MiB3.74 MiB+ 719.2 KiB
/0.338 s0.290 s-0.048 s2.96 MiB3.87 MiB+ 932.44 KiB
Average 0.530 s0.583 s+0.054 s3.44 MiB4.14 MiB+ 722.95 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,54218,611159
CSS4.7%2,28212120
JavaScript3.5%1,6903689
PO File2.1%1,0236291
Markdown1.2%55602
JSON0.1%2801
Total 48,121 19,729 192

PHP Code Analysis | More results »

Lines of code 32,740
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

[20-Jul-2021 21:57:28 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 5535
[20-Jul-2021 21:57:28 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 5535
[20-Jul-2021 21:57:29 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 5535
[20-Jul-2021 21:57:29 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 5535
[20-Jul-2021 21:57:32 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 5535
[20-Jul-2021 21:57:32 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 5535
[20-Jul-2021 21:57:34 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 5535
[20-Jul-2021 21:57:34 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 5535
[20-Jul-2021 21:57:37 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 5535
[20-Jul-2021 21:57:37 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 5535
[20-Jul-2021 21:57: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 5535
[20-Jul-2021 21:57: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 5535
[20-Jul-2021 21:57: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 5535
[20-Jul-2021 21:57: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 5535
[20-Jul-2021 21:57:45 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 5535
[20-Jul-2021 21:57:45 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 5535
[20-Jul-2021 21:57:47 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 5535
[20-Jul-2021 21:57:47 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 5535
[20-Jul-2021 21:57:50 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 5535
[20-Jul-2021 21:57:50 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 5535
See also: All tests for this plugin, How to Hide Mobile Menu Admin Menus