Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.06MB] [CPU: ▼6.19ms] Passed 4 tests
This is a short check of server-side resources used by OrderBee
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.52 ▲0.06 | 45.90 ▲1.32 |
Dashboard /wp-admin | 3.36 ▲0.06 | 45.81 ▼2.41 |
Posts /wp-admin/edit.php | 3.41 ▲0.06 | 47.50 ▼3.17 |
Add New Post /wp-admin/post-new.php | 5.96 ▲0.08 | 86.97 ▼18.75 |
Media Library /wp-admin/upload.php | 3.28 ▲0.06 | 36.12 ▼0.41 |
Settings /wp-admin/admin.php?page=obfrwc_page_settings | 3.30 | 174.53 |
Pickup Locator /wp-admin/admin.php?page=obfrwc_pickup_locator | 3.28 | 31.34 |
Change Log /wp-admin/admin.php?page=obfrwc_change_log | 3.30 | 32.32 |
Server storage [IO: ▲0.11MB] [DB: ▲0.00MB] 67% from 3 tests
A short overview of filesystem and database impact
Just a few items left to fix
- You have illegally modified 1 file (0.61KB) outside of "wp-content/plugins/orderbee/" and "wp-content/uploads/"
- (modified) .htaccess
Filesystem: 33 new files
Database: 1 new table, 6 new options
New tables |
---|
wp_obfrwc_pushjobs |
New WordPress options |
---|
theysaidso_admin_options |
widget_theysaidso_widget |
widget_recent-comments |
can_compress_scripts |
db_upgraded |
widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for OrderBee
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,859 ▲102 | 14.47 ▲0.09 | 1.85 ▼0.05 | 41.22 ▼5.14 |
Dashboard /wp-admin | 2,240 ▲49 | 5.79 ▲0.92 | 103.73 ▼0.76 | 75.24 ▲34.36 |
Posts /wp-admin/edit.php | 2,120 ▲31 | 1.99 ▼0.03 | 35.91 ▼5.78 | 34.11 ▼0.88 |
Add New Post /wp-admin/post-new.php | 1,552 ▲32 | 23.17 ▲0.02 | 746.52 ▲77.72 | 52.99 ▼10.61 |
Media Library /wp-admin/upload.php | 1,425 ▲37 | 4.16 ▼0.02 | 102.57 ▼5.96 | 71.09 ▲24.63 |
Settings /wp-admin/admin.php?page=obfrwc_page_settings | 854 | 2.01 | 23.47 | 28.04 |
Pickup Locator /wp-admin/admin.php?page=obfrwc_pickup_locator | 804 | 2.07 | 29.01 | 24.42 |
Change Log /wp-admin/admin.php?page=obfrwc_change_log | 816 | 2.06 | 24.20 | 25.98 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- can_compress_scripts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Everything seems fine, however 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
- 4× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function current_user_can() in wp-content/plugins/orderbee/admin/partials/orderbee-pickuplocator.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function current_user_can() in wp-content/plugins/orderbee/admin/partials/orderbee-settings.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/orderbee/common/admin-bar.php:55
- > PHP Fatal error
Uncaught Error: Call to undefined function current_user_can() in wp-content/plugins/orderbee/admin/partials/orderbee-product-changlog.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 88% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Please fix the following attributes:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== orderbee ===
) - Contributors: Plugin contributors not specified
orderbee/orderbee.php Passed 13 tests
The entry point to "OrderBee" version 1.3.3 is a PHP file that has certain tags in its header comment area
83 characters long description:
This plugin makes a fast and safe connection between your Woocommerce and OrderBee.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
No dangerous file extensions were detected1,395 lines of code in 23 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 18 | 384 | 472 | 1,087 |
PO File | 3 | 96 | 141 | 294 |
CSS | 1 | 1 | 1 | 11 |
JavaScript | 1 | 2 | 27 | 3 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.27 |
Average class complexity | 7.82 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 20.00 |
Average method complexity | 2.97 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 20.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 11 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 11 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 38 | |
▷ Static methods | 2 | 5.26% |
▷ Public methods | 31 | 81.58% |
▷ Protected methods | 3 | 7.89% |
▷ Private methods | 4 | 10.53% |
Functions | 14 | |
▷ Named functions | 14 | 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
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
favicon.png | 0.87KB | 0.57KB | ▼ 33.97% |