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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼3.60ms] Passed 4 tests
An overview of server-side resources used by Paidy for WooCommerce
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.01 | 35.95 ▼9.76 |
Dashboard /wp-admin | 3.32 ▲0.02 | 49.47 ▼4.84 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 53.12 ▼0.31 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 106.79 ▲4.25 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 39.11 ▲0.50 |
Server storage [IO: ▲0.17MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 15 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
widget_recent-comments |
widget_theysaidso_widget |
theysaidso_admin_options |
can_compress_scripts |
db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Paidy for WooCommerce
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲39 | 14.23 ▼0.13 | 1.64 ▼0.17 | 40.94 ▼4.74 |
Dashboard /wp-admin | 2,206 ▲29 | 5.61 ▲0.04 | 91.59 ▲1.54 | 44.66 ▲1.25 |
Posts /wp-admin/edit.php | 2,115 ▲15 | 1.97 ▼0.02 | 52.20 ▲11.75 | 35.41 ▲2.20 |
Add New Post /wp-admin/post-new.php | 1,535 ▲7 | 23.07 ▼0.32 | 652.06 ▲1.03 | 55.62 ▲5.97 |
Media Library /wp-admin/upload.php | 1,414 ▲20 | 4.24 ▲0.08 | 100.40 ▲2.53 | 47.67 ▲3.92 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
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)
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
Please fix 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 add_action() in wp-content/plugins/paidy-wc/includes/gateways/paidy/class-wc-paidy-endpoint.php:9
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration Passed 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: japanese, woocommerce, paidy, payment, e-commerce...
paidy-wc/paidy-wc.php Passed 13 tests
"Paidy for WooCommerce" version 1.3.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
21 characters long description:
Paidy for WooCommerce
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
Good job! No executable or dangerous file extensions detected1,489 lines of code in 9 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 7 | 152 | 618 | 1,407 |
JavaScript | 1 | 18 | 7 | 71 |
CSS | 1 | 0 | 1 | 11 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.35 |
Average class complexity | 45.75 |
▷ Minimum class complexity | 3.00 |
▷ Maximum class complexity | 76.00 |
Average method complexity | 3.56 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 34.00 |
Code structure | ||
---|---|---|
Namespaces | 1 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 4 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 4 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 70 | |
▷ Static methods | 1 | 1.43% |
▷ Public methods | 65 | 92.86% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 7.14% |
Functions | 7 | |
▷ Named functions | 6 | 85.71% |
▷ Anonymous functions | 1 | 14.29% |
Constants | 5 | |
▷ Global constants | 5 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
4 PNG files occupy 0.07MB with 0.04MB in potential savings
Potential savings
Compression of 4 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/woo-logo.png | 19.97KB | 7.37KB | ▼ 63.08% |
assets/images/paidy_logo_100_2023.png | 4.02KB | 2.07KB | ▼ 48.56% |
assets/images/paidy_checkout_2023_320x100.png | 18.34KB | 7.69KB | ▼ 58.05% |
assets/images/checkout_banner_320x100.png | 25.86KB | 9.74KB | ▼ 62.33% |