Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.16MB] [CPU: ▼2.27ms] Passed 4 tests
Analyzing server-side resources used by Mobile Menu Builder for WordPress
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.62 ▲0.16 | 41.55 ▲0.63 |
Dashboard /wp-admin | 3.47 ▲0.16 | 49.42 ▼1.96 |
Posts /wp-admin/edit.php | 3.58 ▲0.23 | 50.32 ▼0.57 |
Add New Post /wp-admin/post-new.php | 6.05 ▲0.16 | 92.94 ▼5.19 |
Media Library /wp-admin/upload.php | 3.39 ▲0.16 | 38.25 ▼1.37 |
Mobile Menu Builder /wp-admin/index.php?page=mobile-menu-builder--welcome | 3.36 | 36.40 |
Server storage [IO: ▲2.64MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 374 new files
Database: no new tables, 8 new options
New WordPress options |
---|
theysaidso_admin_options |
can_compress_scripts |
mobile_menu_builder_customizer |
db_upgraded |
widget_theysaidso_widget |
MOBILE_MENU_BUILDER_INSTALLED |
widget_recent-comments |
widget_recent-posts |
Browser metrics Passed 4 tests
A check of browser resources used by Mobile Menu Builder for WordPress
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,966 ▲220 | 13.68 ▼0.75 | 8.53 ▲6.55 | 38.64 ▼7.83 |
Dashboard /wp-admin | 2,210 ▲28 | 5.87 ▼0.02 | 110.65 ▲3.50 | 44.49 ▼4.91 |
Posts /wp-admin/edit.php | 2,096 ▲7 | 2.06 ▲0.06 | 42.36 ▲4.39 | 35.10 ▼3.58 |
Add New Post /wp-admin/post-new.php | 1,540 ▲26 | 23.29 ▲5.78 | 644.88 ▼116.52 | 53.01 ▲1.95 |
Media Library /wp-admin/upload.php | 1,392 ▲10 | 4.29 ▲0.07 | 98.62 ▼12.12 | 43.33 ▼0.18 |
Mobile Menu Builder /wp-admin/index.php?page=mobile-menu-builder--welcome | 1,372 | 9.14 | 304.94 | 72.09 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 8 options
- theysaidso_admin_options
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
- MOBILE_MENU_BUILDER_INSTALLED
- mobile_menu_builder_customizer
- widget_recent-posts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Almost there! Just fix the following items
- 19× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Notice
Undefined variable: wp_customize in wp-content/plugins/mobile-menu-builder/includes/customizer/sections/menu-link-1.php on line 3
- > PHP Notice
Undefined variable: wp_customize in wp-content/plugins/mobile-menu-builder/includes/customizer/sections/menu-link-4.php on line 3
- > PHP Fatal error
Uncaught Error: Call to a member function add_setting() on null in wp-content/plugins/mobile-menu-builder/includes/customizer/sections/popup-widgets.php:3
- > PHP Fatal error
Uncaught Error: Call to a member function add_section() on null in wp-content/plugins/mobile-menu-builder/includes/customizer/sections/menu-link-3.php:3
- > PHP Fatal error
Uncaught Error: Call to a member function add_section() on null in wp-content/plugins/mobile-menu-builder/includes/customizer/sections/menu-link-4.php:3
- > PHP Fatal error
Uncaught Error: Call to a member function add_section() on null in wp-content/plugins/mobile-menu-builder/includes/customizer/sections/menu-container.php:3
- > PHP Notice
Undefined variable: wp_customize in wp-content/plugins/mobile-menu-builder/includes/customizer/sections/menu-link-3.php on line 3
- > PHP Notice
Undefined variable: wp_customize in wp-content/plugins/mobile-menu-builder/includes/customizer/sections/popup-widgets.php on line 3
- > PHP Fatal error
Uncaught Error: Call to a member function add_section() on null in wp-content/plugins/mobile-menu-builder/includes/customizer/sections/menu-link-1.php:3
- > PHP Notice
Undefined variable: wp_customize in wp-content/plugins/mobile-menu-builder/includes/customizer/sections/menu-templates.php on line 3
- > PHP Notice
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Attributes that require attention:
- Screenshots: Add images for these screenshots: #1 (WordPress Mobile Menu with Modal Popup), #2 (On User Scroll Animation), #3 (Menu Builder Settings), #4 (Pop-up Menu Builder Settings), #5 (Changing Icons and Label)
mobile-menu-builder/plugin.php 77% from 13 tests
"Mobile Menu Builder for WordPress" version 1.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Main file name: Name the main plugin file the same as the plugin slug ("mobile-menu-builder.php" instead of "plugin.php")
- Domain Path: The domain path should use only dashes and lowercase characters ("languages")
- Domain Path: Prefix the domain path with a forward slash character ("/languages")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Success! There were no dangerous files found in this plugin6,615 lines of code in 361 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
SVG | 318 | 0 | 3 | 2,404 |
PHP | 21 | 324 | 402 | 1,856 |
JavaScript | 10 | 92 | 62 | 1,762 |
Sass | 3 | 30 | 26 | 439 |
CSS | 9 | 23 | 21 | 154 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.37 |
Average class complexity | 12.15 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 111.00 |
Average method complexity | 4.62 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 98.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 13 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 13 | 100.00% |
▷ Final classes | 1 | 7.69% |
Methods | 40 | |
▷ Static methods | 4 | 10.00% |
▷ Public methods | 36 | 90.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 4 | 10.00% |
Functions | 2 | |
▷ Named functions | 2 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 5 | |
▷ Global constants | 5 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
4 PNG files occupy 0.46MB with 0.21MB in potential savings
Potential savings
Compression of 4 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-5.png | 92.31KB | 35.81KB | ▼ 61.21% |
assets/images/placeholder.png | 0.24KB | 0.25KB | 0.00% |
screenshot-3.png | 248.80KB | 99.45KB | ▼ 60.03% |
screenshot-4.png | 125.83KB | 48.82KB | ▼ 61.20% |