Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.04MB] [CPU: ▼12.59ms] Passed 4 tests
Server-side resources used by Cargo Tracking for WooCommerce
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.52 ▲0.05 | 36.21 ▼8.35 |
Dashboard /wp-admin | 3.36 ▲0.02 | 44.88 ▼15.17 |
Posts /wp-admin/edit.php | 3.48 ▲0.12 | 50.37 ▼0.18 |
Add New Post /wp-admin/post-new.php | 5.94 ▲0.05 | 78.98 ▼22.21 |
Media Library /wp-admin/upload.php | 3.29 ▲0.05 | 32.86 ▼4.61 |
Server storage [IO: ▲0.67MB] [DB: ▲0.07MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 53 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
can_compress_scripts |
db_upgraded |
widget_recent-comments |
theysaidso_admin_options |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Cargo Tracking for WooCommerce
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲29 | 13.23 ▼1.16 | 1.71 ▼0.75 | 39.23 ▼7.79 |
Dashboard /wp-admin | 2,206 ▲20 | 4.85 ▼0.09 | 107.61 ▲2.11 | 39.15 ▼4.86 |
Posts /wp-admin/edit.php | 2,089 ▼3 | 2.18 ▲0.18 | 40.25 ▼1.77 | 33.95 ▼3.70 |
Add New Post /wp-admin/post-new.php | 1,542 ▼0 | 18.37 ▲0.29 | 604.10 ▼8.19 | 58.98 ▲13.51 |
Media Library /wp-admin/upload.php | 1,385 ▼3 | 4.24 ▲0.04 | 97.95 ▼2.79 | 39.76 ▼2.36 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
Smoke tests 75% 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 50% 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
Almost there! Just fix the following items
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Class 'WP_List_Table' not found in wp-content/plugins/cargo-tracking-for-woocommerce/app/Table/Table.php:5
- > PHP Fatal error
Uncaught Error: Class 'WC_Settings_Page' not found in wp-content/plugins/cargo-tracking-for-woocommerce/app/Woocommerce/WCSettings.php:7
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 90% 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
9 plugin tags: woocommerce cargo tracking, cargo, cargo tracking, woocommerce kargo takip, shipping...
cargo-tracking-for-woocommerce/CargoTrackingForWooCommerce.php 77% from 13 tests
The principal PHP file in "Cargo Tracking for WooCommerce" v. 1.0.5 is loaded by WordPress automatically on each request
The following require your attention:
- Description: Please keep the plugin description shorter than 140 characters (currently 188 characters long)
- Text Domain: The text domain should only use lowercase characters and dashes
- Main file name: The principal plugin file should be the same as the plugin slug ("cargo-tracking-for-woocommerce.php" instead of "CargoTrackingForWooCommerce.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected1,913 lines of code in 31 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 26 | 304 | 433 | 1,626 |
PO File | 1 | 58 | 67 | 136 |
CSS | 1 | 10 | 0 | 70 |
JavaScript | 1 | 3 | 0 | 45 |
Markdown | 1 | 21 | 0 | 31 |
JSON | 1 | 0 | 0 | 5 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.41 |
Average class complexity | 9.60 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 47.00 |
Average method complexity | 2.66 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.00 |
Code structure | ||
---|---|---|
Namespaces | 7 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 20 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 20 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 94 | |
▷ Static methods | 22 | 23.40% |
▷ Public methods | 90 | 95.74% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 4 | 4.26% |
Functions | 3 | |
▷ Named functions | 1 | 33.33% |
▷ Anonymous functions | 2 | 66.67% |
Constants | 0 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
17 PNG files occupy 0.53MB with 0.13MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/img/ptt.png | 12.76KB | 13.34KB | 0.00% |
assets/img/ups.png | 3.84KB | 4.08KB | 0.00% |
assets/img/surat.png | 81.96KB | 86.62KB | 0.00% |
screenshots/screenshot-3.png | 61.30KB | 24.88KB | ▼ 59.41% |
screenshots/screenshot-5.png | 20.77KB | 7.95KB | ▼ 61.73% |