Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.06MB] [CPU: ▼2.23ms] Passed 4 tests
A check of server-side resources used by Pay4Fun for WooCommerce
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.50 ▲0.04 | 39.73 ▲2.17 |
| Dashboard /wp-admin | 3.36 ▲0.06 | 45.89 ▼1.90 |
| Posts /wp-admin/edit.php | 3.47 ▲0.12 | 49.79 ▲2.17 |
| Add New Post /wp-admin/post-new.php | 5.95 ▲0.07 | 90.44 ▼9.19 |
| Media Library /wp-admin/upload.php | 3.28 ▲0.06 | 34.46 ▼0.01 |
| Pay4Fun Donations /wp-admin/options-general.php?page=p4f-donations-page | 3.25 | 32.96 |
| Pay4Fun /wp-admin/options-general.php?page=p4f-settings-page | 3.27 | 32.60 |
Server storage [IO: ▲0.24MB] [DB: ▲0.07MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 39 new files
Database: 1 new table, 8 new options
| New tables |
|---|
| wp_p4f_donations |
| New WordPress options |
|---|
| p4f_db_version |
| widget_recent-comments |
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-posts |
| widget_wp_p4fdonationswidget |
| can_compress_scripts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Pay4Fun for WooCommerce
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,848 ▲113 | 13.60 ▼1.02 | 1.96 ▲0.34 | 42.84 ▲3.00 |
| Dashboard /wp-admin | 2,226 ▲38 | 5.81 ▼0.12 | 101.20 ▼9.23 | 40.07 ▼2.36 |
| Posts /wp-admin/edit.php | 2,111 ▲22 | 2.04 ▼0.12 | 35.42 ▼4.53 | 33.74 ▼2.22 |
| Add New Post /wp-admin/post-new.php | 1,555 ▲13 | 22.93 ▲4.79 | 674.19 ▲65.87 | 56.02 ▼2.00 |
| Media Library /wp-admin/upload.php | 1,411 ▲20 | 4.32 ▲0.09 | 99.05 ▼2.21 | 42.57 ▼1.88 |
| Pay4Fun Donations /wp-admin/options-general.php?page=p4f-donations-page | 837 | 2.03 | 22.65 | 27.96 |
| Pay4Fun /wp-admin/options-general.php?page=p4f-settings-page | 1,001 | 2.21 | 23.30 | 31.67 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- Zombie tables detected upon uninstall: 1 table
- wp_p4f_donations
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please take a closer look at the following
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/pay4fun-for-woocommerce/includes/class-wp-p4f-donations-widget.php:4
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 86% 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
Attributes that need to be fixed:
- Screenshots: Add descriptions for screenshots #1, #10, #11, #2, #3, #4, #5, #6, #7, #8, #9 in pay4fun-for-woocommerce/assets to your readme.txt
pay4fun-for-woocommerce/woocommerce-pay4fun.php 77% from 13 tests
This is the main PHP file of "Pay4Fun for WooCommerce" version 1.0.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
Please take the time to fix the following:
- Requires at least: The required version number must match the one declared in readme.txt ("4.7" instead of "4.0.0")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
- Main file name: The principal plugin file should be the same as the plugin slug ("pay4fun-for-woocommerce.php" instead of "woocommerce-pay4fun.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Everything looks great! No dangerous files found in this plugin2,770 lines of code in 27 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 22 | 383 | 375 | 1,927 |
| PO File | 2 | 266 | 317 | 733 |
| Markdown | 1 | 27 | 0 | 59 |
| JavaScript | 2 | 8 | 4 | 51 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.42 |
| Average class complexity | 30.89 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 95.00 |
| Average method complexity | 3.64 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 37.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 9 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 9 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 102 | |
| ▷ Static methods | 10 | 9.80% |
| ▷ Public methods | 88 | 86.27% |
| ▷ Protected methods | 3 | 2.94% |
| ▷ Private methods | 11 | 10.78% |
| Functions | 2 | |
| ▷ Named functions | 1 | 50.00% |
| ▷ Anonymous functions | 1 | 50.00% |
| Constants | 18 | |
| ▷ Global constants | 8 | 44.44% |
| ▷ Class constants | 10 | 55.56% |
| ▷ Public constants | 4 | 40.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
1 PNG file occupies 0.01MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/pay4fun.png | 7.29KB | 3.30KB | ▼ 54.70% |