Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼4.49ms] Passed 4 tests
This is a short check of server-side resources used by Aramex Shipping WooCommerce
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 44.51 ▲6.65 |
Dashboard /wp-admin | 3.31 ▲0.00 | 49.01 ▼3.24 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 51.86 ▼2.28 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 94.89 ▼13.08 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 39.39 ▲0.65 |
Server storage [IO: ▲1.67MB] [DB: ▲0.00MB] 67% from 3 tests
Filesystem and database footprint
These are issues you should consider
- Illegal file modification found: 3 files (0.00KB) outside of "wp-content/plugins/aramex-shipping-woocommerce/" and "wp-content/uploads/"
- (new file) "wp-content/plugins/aramex-shipping-woocommerce/assets/icon-256\303\227256.png"
- (new file) "wp-content/plugins/aramex-shipping-woocommerce/assets/icon-128\303\203\342\200\224128.png"
- (new file) "wp-content/plugins/aramex-shipping-woocommerce/assets/icon-128\303\227128.png"
Filesystem: 65 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
theysaidso_admin_options |
widget_theysaidso_widget |
widget_recent-posts |
db_upgraded |
can_compress_scripts |
Browser metrics Passed 4 tests
Checking browser requirements for Aramex Shipping WooCommerce
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲28 | 14.35 ▼0.01 | 1.66 ▼0.21 | 41.04 ▼7.60 |
Dashboard /wp-admin | 2,192 ▲15 | 5.61 ▼0.06 | 92.91 ▲3.50 | 42.47 ▲1.60 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 1.97 ▼0.05 | 40.15 ▲3.54 | 35.27 ▼1.99 |
Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.03 ▼0.23 | 602.95 ▼54.45 | 47.69 ▼2.62 |
Media Library /wp-admin/upload.php | 1,397 ▼3 | 4.19 ▲0.05 | 101.45 ▼12.53 | 45.85 ▼4.00 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- widget_recent-comments
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
Please fix the following items
- 3× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/aramex-shipping-woocommerce/includes/shipping/data-aramex-settings.php:18
- > PHP Fatal error
Uncaught Error: Class 'Aramex_Shipping_Method' not found in wp-content/plugins/aramex-shipping-woocommerce/templates/adminhtml/block_button.php:27
- > PHP Fatal error
Uncaught Error: Class 'WC_Shipping_Method' not found in wp-content/plugins/aramex-shipping-woocommerce/includes/shipping/class-aramex-woocommerce-shipping.php:20
- > 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 83% from 29 tests
readme.txt 81% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Attributes that need to be fixed:
- Screenshots: Screenshot #7 ("Track Aramex Shipment"page.) image not found
- Donate link: Please fix this invalid URI: "aramex.com"
- Tags: Please delete some tags, you are using 19 tag instead of maximum 10
aramex-shipping-woocommerce/aramex-shipping.php 85% from 13 tests
The entry point to "Aramex Shipping WooCommerce" version 1.1.16 is a PHP file that has certain tags in its header comment area
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("aramex-shipping-woocommerce.php" instead of "aramex-shipping.php")
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
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
No dangerous file extensions were detected9,335 lines of code in 40 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 27 | 426 | 903 | 5,901 |
XML | 8 | 9 | 84 | 2,581 |
CSS | 2 | 129 | 64 | 764 |
JavaScript | 3 | 20 | 45 | 89 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.38 |
Average class complexity | 19.62 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 71.00 |
Average method complexity | 6.10 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 51.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 13 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 13 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 40 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 22 | 55.00% |
▷ Protected methods | 3 | 7.50% |
▷ Private methods | 15 | 37.50% |
Functions | 31 | |
▷ Named functions | 31 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
23 PNG files occupy 1.09MB with 0.44MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/screenshot-2.png | 39.65KB | 15.60KB | ▼ 60.66% |
assets/css/images/ui-bg_highlight-soft_75_cccccc_1x100.png | 0.10KB | 0.17KB | 0.00% |
assets/screenshot-5.png | 34.82KB | 13.73KB | ▼ 60.57% |
assets/css/images/ui-bg_glass_75_e6e6e6_1x400.png | 0.11KB | 0.14KB | 0.00% |
assets/icon-256×256.png | 23.65KB | 4.13KB | ▼ 82.55% |