Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.09MB] [CPU: ▼4.85ms] Passed 4 tests
Analyzing server-side resources used by SVG Menu
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.55 ▲0.09 | 38.40 ▼3.68 |
Dashboard /wp-admin | 3.39 ▲0.08 | 45.60 ▼4.04 |
Posts /wp-admin/edit.php | 3.50 ▲0.14 | 46.29 ▼7.48 |
Add New Post /wp-admin/post-new.php | 5.98 ▲0.10 | 96.84 ▼4.18 |
Media Library /wp-admin/upload.php | 3.31 ▲0.08 | 39.03 ▲4.83 |
Server storage [IO: ▲0.12MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 31 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
theysaidso_admin_options |
can_compress_scripts |
widget_recent-comments |
db_upgraded |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
Checking browser requirements for SVG Menu
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,936 ▲201 | 13.58 ▼0.79 | 5.39 ▲3.41 | 40.33 ▼4.40 |
Dashboard /wp-admin | 2,226 ▲38 | 4.85 ▼0.96 | 100.14 ▼0.44 | 43.04 ▼1.62 |
Posts /wp-admin/edit.php | 2,112 ▲20 | 2.03 ▼0.01 | 36.17 ▼3.86 | 34.50 ▼1.89 |
Add New Post /wp-admin/post-new.php | 1,540 ▲7 | 18.47 ▼4.90 | 620.46 ▲1.98 | 50.05 ▼3.65 |
Media Library /wp-admin/upload.php | 1,405 ▲23 | 4.29 ▲0.01 | 97.71 ▼1.78 | 43.06 ▼0.23 |
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
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following
- 1× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/svg-menu/public/partials/svgmenu-public-display.php
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/svg-menu/admin/partials/svgmenu-admin-display.php:26
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 90% 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
These attributes need your attention:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== svg-menu ===
)
svg-menu/svgmenu.php 85% from 13 tests
"SVG Menu" version 1.0.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
You should first fix the following items:
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
- Main file name: The principal plugin file should be the same as the plugin slug ("svg-menu.php" instead of "svgmenu.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
There were no executable files found in this plugin1,622 lines of code in 22 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 4 | 149 | 18 | 924 |
JavaScript | 6 | 16 | 4 | 379 |
PHP | 12 | 168 | 536 | 319 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.18 |
Average class complexity | 3.86 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 12.00 |
Average method complexity | 1.62 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 7.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 7 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 7 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 32 | |
▷ Static methods | 2 | 6.25% |
▷ Public methods | 27 | 84.38% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 15.62% |
Functions | 3 | |
▷ Named functions | 3 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
3 PNG files occupy 0.04MB with 0.02MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
admin/images/menu1.png | 14.71KB | 5.39KB | ▼ 63.37% |
admin/images/menu2.png | 7.58KB | 2.64KB | ▼ 65.17% |
admin/images/menu3.png | 18.29KB | 7.55KB | ▼ 58.71% |