Mobile Menu 2.8.2.5

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
No resource errors
Performance

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

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

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=c5bed51402
Aspect after-activation
HTTP status 200
Load time 1.649 s
Memory usage 5.9 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.764 s
Memory usage 4.05 MiB
JS errors None
Resource errors None

Mobile Menu Options → General OptionsGetting startedVisibility optionsFont OptionsAlertsAdvanced optionsImport and Export

Page screenshot: Mobile Menu Options → General OptionsGetting startedVisibility optionsFont OptionsAlertsAdvanced optionsImport and Export
URL /wp-admin/admin.php?page=mobile-menu-options
Aspect menu-item-tab
HTTP status 200
Load time 0.611 s
Memory usage 4.05 MiB
JS errors None
Resource errors None

Mobile Menu Options → HeaderMain OptionsLogo

Page screenshot: Mobile Menu Options → HeaderMain OptionsLogo
URL /wp-admin/admin.php?page=mobile-menu-options
Aspect menu-item-tab
HTTP status 200
Load time 0.624 s
Memory usage 4.05 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
Aspect menu-item-tab
HTTP status 200
Load time 0.650 s
Memory usage 4.05 MiB
JS errors None
Resource errors None

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.559 s
Memory usage 4.05 MiB
JS errors None
Resource errors None

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.606 s
Memory usage 4.05 MiB
JS errors None
Resource errors None

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.604 s
Memory usage 4.05 MiB
JS errors None
Resource errors None

Mobile Menu Options → ColorsGeneralHeaderLeft MenuRight Menu

Page screenshot: Mobile Menu Options → ColorsGeneralHeaderLeft MenuRight Menu
URL /wp-admin/admin.php?page=mobile-menu-options
Aspect menu-item-tab
HTTP status 200
Load time 0.524 s
Memory usage 4.05 MiB
JS errors None
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 1.089 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.75 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.259 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.144 s
Memory usage 4.04 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.272 s
Memory usage 3.86 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.332 s0.447 s+0.115 s3.08 MiB3.77 MiB+ 705.98 KiB
/wp-admin/edit.php0.179 s0.197 s+0.018 s3.11 MiB3.8 MiB+ 707.52 KiB
/wp-admin/post-new.php0.914 s1.565 s+0.651 s5.27 MiB5.9 MiB+ 644.75 KiB
/wp-admin/upload.php0.560 s0.302 s-0.258 s3.03 MiB3.72 MiB+ 707.16 KiB
/wp-admin/options-writing.php0.154 s0.147 s-0.007 s3.02 MiB3.69 MiB+ 687.4 KiB
/wp-admin/media-new.php0.413 s0.228 s-0.185 s3.01 MiB3.7 MiB+ 707.96 KiB
/wp-admin/edit-tags.php?taxonomy=category0.178 s0.192 s+0.014 s3.04 MiB3.73 MiB+ 704.47 KiB
/wp-admin/post-new.php?post_type=page0.880 s0.682 s-0.198 s5.26 MiB5.88 MiB+ 640.75 KiB
/wp-admin/options-discussion.php0.218 s0.600 s+0.382 s3 MiB3.69 MiB+ 708.27 KiB
/wp-admin/edit-comments.php0.198 s0.224 s+0.026 s3.04 MiB3.73 MiB+ 705.91 KiB
/0.252 s0.239 s-0.013 s2.96 MiB3.86 MiB+ 926.05 KiB
Average 0.389 s0.438 s+0.050 s3.44 MiB4.13 MiB+ 713.29 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
PHP87.5%42,37718,253159
CSS5.0%2,41712020
JavaScript4.2%2,0313619
PO File2.1%1,0236291
Markdown1.1%55602
JSON0.1%2801
SVG0.1%2502
Total 48,457 19,363 194

PHP Code Analysis | More results »

Lines of code 32,486
Total complexity 7,381
Median class complexity 12.5
Median method complexity 2.0
Most complex class Freemius
Most complex function FS_Plugin_Info_Dialog::install_plugin_information()
Classes 96
Methods 1,578
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-Dec-2021 12:48:07 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-Dec-2021 12:48:07 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-Dec-2021 12:48:09 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-Dec-2021 12:48:09 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-Dec-2021 12:48: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-Dec-2021 12:48: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-Dec-2021 12:48:14 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-Dec-2021 12:48:14 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-Dec-2021 12:48: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-Dec-2021 12:48: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-Dec-2021 12:48:19 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-Dec-2021 12:48:19 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-Dec-2021 12:48:22 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-Dec-2021 12:48:22 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-Dec-2021 12:48:24 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-Dec-2021 12:48:24 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-Dec-2021 12:48:27 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-Dec-2021 12:48:27 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-Dec-2021 12:48: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 5663
[10-Dec-2021 12:48: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 5663
See also: All tests for this plugin, How to Hide Mobile Menu Admin Menus