Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.04MB] [CPU: ▼9.17ms] Passed 4 tests
A check of server-side resources used by Delivery rate for Yamato transport
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.05 | 45.13 ▲1.16 |
Dashboard /wp-admin | 3.35 ▲0.01 | 50.80 ▼16.46 |
Posts /wp-admin/edit.php | 3.40 ▲0.05 | 50.15 ▼1.86 |
Add New Post /wp-admin/post-new.php | 5.93 ▲0.05 | 88.18 ▼15.34 |
Media Library /wp-admin/upload.php | 3.27 ▲0.05 | 36.46 ▼3.01 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 6 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
db_upgraded |
theysaidso_admin_options |
widget_recent-posts |
widget_recent-comments |
can_compress_scripts |
Browser metrics Passed 4 tests
Delivery rate for Yamato transport: an overview of browser usage
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲28 | 14.37 ▼0.19 | 1.84 ▲0.11 | 42.56 ▼2.04 |
Dashboard /wp-admin | 2,198 ▲21 | 5.63 ▼0.09 | 86.74 ▼6.36 | 44.30 ▲5.05 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 2.01 ▲0.06 | 36.22 ▼4.14 | 35.41 ▼1.16 |
Add New Post /wp-admin/post-new.php | 1,526 ▼2 | 23.32 ▲0.18 | 651.33 ▼26.15 | 54.24 ▼3.35 |
Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.15 ▼0.11 | 97.22 ▼4.55 | 42.10 ▼1.76 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- 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
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please take a closer look at the following
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function apply_filters() in wp-content/plugins/delivery-rate-for-yamato-transport/delivery-rate-for-yamato.php:14
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
These attributes need your attention:
- Screenshots: These screenshots require images: #1 (Admin Panel Shipping.), #2 (The contents of the cart.)
delivery-rate-for-yamato-transport/delivery-rate-for-yamato.php 92% from 13 tests
The primary PHP file in "Delivery rate for Yamato transport" version 1.0.2 is used by WordPress to initiate all plugin functionality
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("delivery-rate-for-yamato-transport.php" instead of "delivery-rate-for-yamato.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected298 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 10 | 49 | 230 |
PO File | 1 | 29 | 34 | 68 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.77 |
Average class complexity | 49.00 |
▷ Minimum class complexity | 49.00 |
▷ Maximum class complexity | 49.00 |
Average method complexity | 10.60 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 49.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 | 5 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 5 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 3 | |
▷ Named functions | 3 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
2 PNG files occupy 0.04MB with 0.03MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-1.png | 36.71KB | 16.73KB | ▼ 54.43% |
screenshot-2.png | 9.22KB | 3.51KB | ▼ 61.94% |