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.29MB] [CPU: ▼0.23ms] Passed 4 tests
A check of server-side resources used by Parcel Tracker eCourier
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.78 ▲0.32 | 43.14 ▼0.16 |
Dashboard /wp-admin | 3.63 ▲0.32 | 50.88 ▼3.50 |
Posts /wp-admin/edit.php | 3.68 ▲0.32 | 55.02 ▲1.97 |
Add New Post /wp-admin/post-new.php | 6.15 ▲0.26 | 90.91 ▲0.78 |
Media Library /wp-admin/upload.php | 3.49 ▲0.26 | 42.50 ▲4.94 |
Server storage [IO: ▲0.88MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 47 new files
Database: 1 new table, 8 new options
New tables |
---|
ept_settings |
New WordPress options |
---|
can_compress_scripts |
ept_installed |
ept_version |
widget_recent-posts |
db_upgraded |
widget_recent-comments |
theysaidso_admin_options |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for Parcel Tracker eCourier
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,828 ▲42 | 14.25 ▼0.10 | 1.64 ▼0.28 | 41.67 ▼4.42 |
Dashboard /wp-admin | 2,222 ▲42 | 5.57 ▼0.10 | 89.80 ▲1.40 | 87.70 ▲42.74 |
Posts /wp-admin/edit.php | 2,146 ▲46 | 2.10 ▲0.12 | 37.12 ▼0.75 | 33.48 ▼1.81 |
Add New Post /wp-admin/post-new.php | 1,578 ▲52 | 23.04 ▼0.35 | 720.75 ▲36.36 | 64.63 ▲4.94 |
Media Library /wp-admin/upload.php | 1,442 ▲42 | 4.20 ▼0.00 | 100.03 ▼13.33 | 64.21 ▲15.08 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 8 options in the database
- widget_recent-comments
- ept_version
- db_upgraded
- ept_installed
- widget_theysaidso_widget
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please take a closer look at the following
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/parcel-tracker-ecourier/includes/Admin/views/settings-view.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/parcel-tracker-ecourier/includes/Frontend/views/form-parcel-tracker.php:11
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
These attributes need to be fixed:
- Screenshots: These screenshots lack descriptions #1, #2, #3, #4 in parcel-tracker-ecourier/assets to your readme.txt
- Tags: There are too many tags (12 tag instead of maximum 10)
parcel-tracker-ecourier/parcel-tracker-ecourier.php 77% from 13 tests
The entry point to "Parcel Tracker eCourier" version 1.0.2 is a PHP file that has certain tags in its header comment area
Please make the necessary changes and fix the following:
- Domain Path: The domain path is invalid: folder "/languages" does not exist
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
- Git Repository: Please remove the Git repository from this plugin
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
Success! There were no dangerous files found in this plugin13,753 lines of code in 39 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 3 | 1,819 | 10,490 | 10,619 |
PHP | 30 | 720 | 1,069 | 2,502 |
CSS | 1 | 49 | 10 | 351 |
Markdown | 1 | 66 | 0 | 181 |
JSON | 3 | 0 | 0 | 99 |
SVG | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.38 |
Average class complexity | 15.50 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 68.00 |
Average method complexity | 2.76 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.00 |
Code structure | ||
---|---|---|
Namespaces | 6 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 18 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 18 | 100.00% |
▷ Final classes | 1 | 5.56% |
Methods | 149 | |
▷ Static methods | 16 | 10.74% |
▷ Public methods | 110 | 73.83% |
▷ Protected methods | 6 | 4.03% |
▷ Private methods | 33 | 22.15% |
Functions | 6 | |
▷ Named functions | 5 | 83.33% |
▷ Anonymous functions | 1 | 16.67% |
Constants | 11 | |
▷ Global constants | 9 | 81.82% |
▷ Class constants | 2 | 18.18% |
▷ Public constants | 2 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
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 |
assets/images/menu_icon.png | 2.13KB | 1.06KB | ▼ 50.18% |