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
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼5.90ms] Passed 4 tests
Analyzing server-side resources used by Woocommerce Booster - Search order by custom number (FIX)
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.01 | 42.47 ▼1.09 |
Dashboard /wp-admin | 3.32 ▲0.02 | 51.40 ▼3.25 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 47.49 ▼2.08 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 94.57 ▼17.11 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 36.73 ▼1.15 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 4 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_theysaidso_widget |
theysaidso_admin_options |
widget_recent-comments |
can_compress_scripts |
widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for Woocommerce Booster - Search order by custom number (FIX)
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲28 | 14.42 ▼0.11 | 1.98 ▼0.49 | 42.69 ▼6.29 |
Dashboard /wp-admin | 2,198 ▲18 | 5.64 ▼0.02 | 84.14 ▼9.63 | 39.95 ▼3.41 |
Posts /wp-admin/edit.php | 2,103 ▲3 | 2.09 ▲0.14 | 37.39 ▲0.17 | 33.26 ▼2.59 |
Add New Post /wp-admin/post-new.php | 1,534 ▲7 | 18.64 ▼4.45 | 625.32 ▼71.94 | 77.59 ▲18.24 |
Media Library /wp-admin/upload.php | 1,397 ▼0 | 4.16 ▼0.00 | 102.73 ▼0.54 | 46.63 ▲1.33 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_theysaidso_widget
- widget_recent-comments
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 2× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WCSON\\Design_Pattern\\Autoload' not found in wp-content/plugins/wc-booster-search-order-by-custom-number-fix/Order.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function WCSON\\plugin_dir_path() in wp-content/plugins/wc-booster-search-order-by-custom-number-fix/plugin.php:19
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
7 plugin tags: fix, woocommerce jetpack, order, search, booster for woocommerce...
wc-booster-search-order-by-custom-number-fix/plugin.php 85% from 13 tests
The entry point to "Woocommerce Booster - Search order by custom number (FIX)" version 1.0.0 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("wc-booster-search-order-by-custom-number-fix.php" instead of "plugin.php")
- 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
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
There were no executable files found in this plugin82 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 12 | 16 | 65 |
Markdown | 1 | 7 | 0 | 17 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.42 |
Average class complexity | 4.50 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 7.00 |
Average method complexity | 2.75 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 7.00 |
Code structure | ||
---|---|---|
Namespaces | 2 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 4 | |
▷ Static methods | 1 | 25.00% |
▷ Public methods | 2 | 50.00% |
▷ Protected methods | 2 | 50.00% |
▷ Private methods | 0 | 0.00% |
Functions | 1 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 1 | 100.00% |
Constants | 0 | |
▷ Global constants | 0 | 0.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
There were not PNG files found in your plugin