Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Install script ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼7.18ms] Passed 4 tests
Analyzing server-side resources used by WooCommerce Postcode Validator
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 38.58 ▼5.00 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 47.04 ▼6.14 |
| Posts /wp-admin/edit.php | 3.38 ▲0.02 | 50.80 ▼2.58 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 85.69 ▼14.98 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.01 | 35.13 ▼2.58 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 16 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| widget_recent-comments |
| widget_recent-posts |
Browser metrics Passed 4 tests
A check of browser resources used by WooCommerce Postcode Validator
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,795 ▲34 | 14.38 ▲0.03 | 1.60 ▼0.16 | 43.06 ▼0.22 |
| Dashboard /wp-admin | 2,195 ▲18 | 5.63 ▲0.06 | 91.78 ▲6.69 | 43.46 ▲3.13 |
| Posts /wp-admin/edit.php | 2,106 ▲3 | 2.04 ▲0.08 | 40.56 ▲4.04 | 38.06 ▼0.10 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲7 | 23.12 ▲0.17 | 629.94 ▼57.19 | 48.53 ▼16.83 |
| Media Library /wp-admin/upload.php | 1,406 ▲6 | 4.22 ▼0.07 | 95.59 ▼12.44 | 40.76 ▼2.35 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
You still need to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
- widget_theysaidso_widget
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
Everything seems fine, however this is by no means an exhaustive test
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
- 1× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/woo-postcode-validator/public/partials/woocommerce-postcode-validator-public-display.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 81% 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
Attributes that need to be fixed:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== woo-postcode-validator ===) - Requires at least: Invalid plugin version format
- Tested up to: Invalid plugin version format
woo-postcode-validator/woocommerce-postcode-validator.php 85% from 13 tests
The primary PHP file in "WooCommerce Postcode Validator" version 1.0.1 is used by WordPress to initiate all plugin functionality
The following require your attention:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Main file name: The principal plugin file should be the same as the plugin slug ("woo-postcode-validator.php" instead of "woocommerce-postcode-validator.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Success! There were no dangerous files found in this plugin263 lines of code in 10 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 7 | 60 | 356 | 186 |
| JavaScript | 1 | 5 | 8 | 49 |
| Markdown | 1 | 13 | 0 | 21 |
| CSS | 1 | 1 | 4 | 7 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.27 |
| Average class complexity | 6.33 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 14.00 |
| Average method complexity | 1.19 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 3.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 17 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 14 | 82.35% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 3 | 17.65% |
| Functions | 3 | |
| ▷ Named functions | 2 | 66.67% |
| ▷ Anonymous functions | 1 | 33.33% |
| Constants | 5 | |
| ▷ Global constants | 1 | 20.00% |
| ▷ Class constants | 4 | 80.00% |
| ▷ Public constants | 4 | 100.00% |
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