Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼12.96ms] Passed 4 tests
Analyzing server-side resources used by Australia Post WooCommerce Extension
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.52 ▲0.03 | 41.03 ▲0.18 |
| Dashboard /wp-admin | 3.36 ▼0.02 | 47.78 ▼14.75 |
| Posts /wp-admin/edit.php | 3.41 ▲0.02 | 49.14 ▼13.07 |
| Add New Post /wp-admin/post-new.php | 5.94 ▲0.02 | 83.95 ▼24.19 |
| Media Library /wp-admin/upload.php | 3.28 ▲0.02 | 39.27 ▲3.47 |
Server storage [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: no files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-posts |
| widget_recent-comments |
| widget_theysaidso_widget |
| db_upgraded |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
A check of browser resources used by Australia Post WooCommerce Extension
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,825 ▲79 | 14.74 ▲0.30 | 2.10 ▲0.49 | 44.11 ▲3.87 |
| Dashboard /wp-admin | 2,209 ▲18 | 5.86 ▲0.94 | 96.42 ▼9.20 | 40.78 ▲3.35 |
| Posts /wp-admin/edit.php | 2,086 ▼3 | 1.97 ▼0.04 | 35.59 ▼1.71 | 30.94 ▼8.58 |
| Add New Post /wp-admin/post-new.php | 1,537 ▲4 | 23.04 ▼0.17 | 683.99 ▲68.57 | 50.24 ▲2.29 |
| Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.24 ▲0.05 | 110.99 ▲8.90 | 47.23 ▲3.14 |
Uninstaller [IO: ✅] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
These items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
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)
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
- 61× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'WPRubyAustraliaPost\\Deps\\Psr\\Log\\LoggerAwareInterface' not found in wp-content/plugins/australian-post-woocommerce-extension/deps/dvdoug/boxpacker/VolumePacker.php:18
- > PHP Fatal error
Uncaught Error: Interface 'WPRubyAustraliaPost\\Deps\\DVDoug\\BoxPacker\\Box' not found in wp-content/plugins/australian-post-woocommerce-extension/deps/dvdoug/boxpacker/WorkingVolume.php:15
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/australian-post-woocommerce-extension/vendor/dvdoug/boxpacker/tests/BoxListTest.php:15
- > PHP Fatal error
Uncaught Error: Interface 'WPRubyAustraliaPost\\Deps\\DVDoug\\BoxPacker\\Item' not found in wp-content/plugins/australian-post-woocommerce-extension/deps/dvdoug/boxpacker/ConstrainedPlacementItem.php:16
- > PHP Fatal error
Uncaught Error: Interface 'WPRuby\\AustraliaPostLite\\DVDoug\\BoxPacker\\Item' not found in wp-content/plugins/australian-post-woocommerce-extension/vendor/dvdoug/boxpacker/src/ConstrainedPlacementItem.php:15
- > PHP Fatal error
Uncaught Error: Interface 'WPRuby\\AustraliaPostLite\\DVDoug\\BoxPacker\\Item' not found in wp-content/plugins/australian-post-woocommerce-extension/vendor/dvdoug/boxpacker/tests/Test/TestItem.php:14
- > PHP Fatal error
Uncaught Error: Interface 'WPRuby\\AustraliaPostLite\\DVDoug\\BoxPacker\\Box' not found in wp-content/plugins/australian-post-woocommerce-extension/vendor/dvdoug/boxpacker/tests/Test/TestBox.php:13
- > PHP Fatal error
Uncaught Error: Interface 'TypistTech\\Imposter\\ConfigCollectionInterface' not found in wp-content/plugins/australian-post-woocommerce-extension/vendor/typisttech/imposter/src/ConfigCollection.php:7
- > PHP Fatal error
Uncaught Error: Class 'WPRuby\\AustraliaPostLite\\PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/australian-post-woocommerce-extension/vendor/psr/log/Psr/Log/Test/LoggerInterfaceTest.php:15
- > PHP Fatal error
Uncaught Error: Class 'WPRubyAustraliaPost\\Deps\\PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/australian-post-woocommerce-extension/deps/psr/log/Test/LoggerInterfaceTest.php:14
- > 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 86% 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
6 plugin tags: shipping method, woocommerce, admin, woocommerce extension, australia post...
australian-post-woocommerce-extension/australian-post.php 69% from 13 tests
"Australia Post WooCommerce Extension" version 1.10.3's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("australian-post-woocommerce-extension.php" instead of "australian-post.php")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
- Requires at least: Required version must match the one declared in readme.txt ("4.0.0" instead of "3.0")
- Domain Path: The domain path is invalid: folder "/languages" does not exist
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
No dangerous file extensions were detected7,961 lines of code in 136 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 120 | 1,282 | 4,504 | 7,230 |
| JSON | 1 | 0 | 0 | 287 |
| Cucumber | 2 | 20 | 0 | 148 |
| reStructuredText | 7 | 88 | 183 | 136 |
| YAML | 3 | 9 | 1 | 102 |
| Python | 1 | 39 | 92 | 40 |
| XML | 1 | 3 | 0 | 16 |
| INI | 1 | 0 | 0 | 2 |
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.18 |
| Average class complexity | 5.62 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 59.00 |
| Average method complexity | 1.88 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 25.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 13 | |
| Interfaces | 18 | |
| Traits | 4 | |
| Classes | 90 | |
| ▷ Abstract classes | 4 | 4.44% |
| ▷ Concrete classes | 86 | 95.56% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 643 | |
| ▷ Static methods | 33 | 5.13% |
| ▷ Public methods | 573 | 89.11% |
| ▷ Protected methods | 12 | 1.87% |
| ▷ Private methods | 58 | 9.02% |
| Functions | 38 | |
| ▷ Named functions | 1 | 2.63% |
| ▷ Anonymous functions | 37 | 97.37% |
| Constants | 19 | |
| ▷ Global constants | 2 | 10.53% |
| ▷ Class constants | 17 | 89.47% |
| ▷ Public constants | 16 | 94.12% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
No PNG files were detected