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
Install script ran successfully
Server metrics [RAM: ▼0.10MB] [CPU: ▼11.34ms] Passed 4 tests
A check of server-side resources used by WooCommerce Fields for Japan
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.53 ▲0.07 | 37.78 ▼0.72 |
| Dashboard /wp-admin | 3.26 ▼0.04 | 30.55 ▼18.36 |
| Posts /wp-admin/edit.php | 3.33 ▼0.03 | 34.91 ▼12.26 |
| Add New Post /wp-admin/post-new.php | 5.50 ▼0.39 | 80.27 ▼12.40 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 30.32 ▼2.34 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 7 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| db_upgraded |
| widget_recent-comments |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Checking browser requirements for WooCommerce Fields for Japan
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.35 ▼0.00 | 1.66 ▼0.10 | 43.64 ▲1.65 |
| Dashboard /wp-admin | 2,192 ▲12 | 5.54 ▼0.07 | 86.22 ▼2.05 | 35.47 ▼3.43 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 1.97 ▼0.01 | 36.76 ▼3.55 | 33.08 ▼4.57 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.23 ▲0.22 | 596.14 ▼38.79 | 78.67 ▲25.24 |
| Media Library /wp-admin/upload.php | 1,400 ▲3 | 4.13 ▼0.06 | 98.06 ▼0.62 | 42.54 ▲1.43 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not 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
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woocommerce-fields-for-japan/wcfjp.php:536
- > PHP Fatal error
Uncaught Error: Call to undefined function status_header() in wp-content/plugins/woocommerce-fields-for-japan/uninstall.php:3
- > PHP Fatal error
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 90% from 29 tests
readme.txt 94% 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 your attention:
- Screenshots: Please add images for these screenshots: #1 (お客様チェックアウト時フォーム), #2 (管理画面受注管理ページでの表示)
woocommerce-fields-for-japan/wcfjp.php 85% from 13 tests
The principal PHP file in "WooCommerce Fields for Japan" v. 1... is loaded by WordPress automatically on each request
It is important to fix the following:
- Version: Plugin version number should only contain digits separated by dots (ex. "1.0.3" instead of "1...")
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("woocommerce-fields-for-japan.php" instead of "wcfjp.php")
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
Good job! No executable or dangerous file extensions detected442 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 77 | 113 | 361 |
| JavaScript | 1 | 19 | 2 | 67 |
| CSS | 1 | 2 | 0 | 14 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.13 |
| Average class complexity | 13.00 |
| ▷ Minimum class complexity | 13.00 |
| ▷ Maximum class complexity | 13.00 |
| Average method complexity | 2.09 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 7.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 11 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 11 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 1 | |
| ▷ Named functions | 1 | 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 Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
2 PNG files occupy 0.02MB with 0.01MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 18.38KB | 10.18KB | ▼ 44.61% |
| screenshot-2.png | 7.17KB | 3.97KB | ▼ 44.60% |