Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.00MB] [CPU: ▼7.55ms] Passed 4 tests
Server-side resources used by Delivery Date and Time for WooCommerce
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 49.42 ▲11.93 |
Dashboard /wp-admin | 3.32 ▼0.03 | 45.82 ▼14.85 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 45.46 ▼3.94 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 91.33 ▼8.32 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 35.76 ▼3.08 |
Server storage [IO: ▲0.42MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 30 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
db_upgraded |
widget_recent-posts |
widget_theysaidso_widget |
widget_recent-comments |
theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Delivery Date and Time for WooCommerce
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,818 ▲47 | 13.19 ▼1.07 | 1.95 ▼0.03 | 43.62 ▲2.14 |
Dashboard /wp-admin | 2,224 ▲39 | 5.82 ▲0.93 | 99.02 ▼1.54 | 39.53 ▼4.71 |
Posts /wp-admin/edit.php | 2,107 ▲18 | 2.15 ▲0.15 | 36.58 ▼4.71 | 33.16 ▲1.93 |
Add New Post /wp-admin/post-new.php | 1,555 ▲41 | 18.22 ▲0.71 | 594.58 ▼82.44 | 66.85 ▲14.15 |
Media Library /wp-admin/upload.php | 1,406 ▲21 | 4.18 ▼0.01 | 94.26 ▼19.99 | 41.92 ▼4.14 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
These items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- widget_recent-comments
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP Passed 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
Everything seems fine, however this is by no means an exhaustive test
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
8 plugin tags: delivery-date, delevery-date, delivery-date-and-time, tmd, deleverydate...
tmd-wc-delivery-date-time/delivery-datetime.php 77% from 13 tests
The main PHP file in "Delivery Date and Time for WooCommerce" ver. 1.0.2 adds more information about the plugin and also serves as the entry point for this plugin
Please make the necessary changes and fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("tmd-wc-delivery-date-time.php" instead of "delivery-datetime.php")
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Domain Path: The domain path is invalid: folder "/i18n/languages/" does not exist
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
There were no executable files found in this plugin1,516 lines of code in 11 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 3 | 41 | 56 | 1,227 |
PHP | 6 | 166 | 108 | 287 |
JavaScript | 2 | 0 | 7 | 2 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.25 |
Average class complexity | 2.00 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 3.00 |
Average method complexity | 1.18 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 2.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 1 | 50.00% |
Methods | 12 | |
▷ Static methods | 2 | 16.67% |
▷ Public methods | 12 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 8 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 8 | 100.00% |
Constants | 2 | |
▷ Global constants | 2 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
17 compressed PNG files occupy 0.36MB
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/css/images/ui-icons_222222_256x240.png | 3.69KB | 4.18KB | 0.00% |
assets/css/images/ui-icons_cd0a0a_256x240.png | 3.69KB | 4.18KB | 0.00% |
assets/css/images/ui-bg_highlight-soft_75_cccccc_1x100.png | 0.08KB | 0.17KB | 0.00% |
assets/css/images/ui-bg_glass_75_e6e6e6_1x400.png | 0.09KB | 0.14KB | 0.00% |
screenshot-3.png | 59.29KB | 21.38KB | ▼ 63.94% |