Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.04MB] [CPU: ▼10.08ms] Passed 4 tests
Server-side resources used by Payment Gateway Payeezy for WooCommerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.52 ▲0.06 | 36.79 ▼2.83 |
| Dashboard /wp-admin | 3.35 ▲0.01 | 44.29 ▼15.18 |
| Posts /wp-admin/edit.php | 3.40 ▲0.05 | 46.86 ▼1.36 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.05 | 81.22 ▼20.96 |
| Media Library /wp-admin/upload.php | 3.28 ▲0.05 | 35.93 ▲0.06 |
Server storage [IO: ▲0.14MB] [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 |
|---|
| widget_recent-posts |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-comments |
| can_compress_scripts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for Payment Gateway Payeezy for WooCommerce
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,802 ▲56 | 13.23 ▼1.36 | 1.68 ▼0.01 | 41.08 ▼2.35 |
| Dashboard /wp-admin | 2,206 ▲15 | 4.84 ▼1.02 | 100.81 ▼6.02 | 42.49 ▲4.03 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.04 ▲0.03 | 35.38 ▼6.27 | 30.38 ▼7.17 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲14 | 23.34 ▲0.11 | 675.24 ▼13.30 | 64.58 ▲10.10 |
| Media Library /wp-admin/upload.php | 1,391 ▲3 | 4.21 ▲0.02 | 96.38 ▼7.18 | 43.72 ▼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 did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
Smoke tests Passed 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)
The smoke test was a success, however most plugin functionality was not tested
SRP Passed 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
Everything seems fine, however this is by no means an exhaustive test
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Attributes that require attention:
- Tags: There are too many tags (12 tag instead of maximum 10)
fd-payments-for-woo/woocommerce-payeezy.php 69% from 13 tests
"Payment Gateway Payeezy for WooCommerce" version 2.1.1's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
It is important to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("fd-payments-for-woo.php" instead of "woocommerce-payeezy.php")
- Requires at least: The required version number did not match the one declared in readme.txt ("4.0" instead of "2.2.0")
- Description: Keep the plugin description shorter than 140 characters (currently 169 characters long)
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
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 detected2,515 lines of code in 13 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 10 | 271 | 856 | 2,317 |
| JavaScript | 2 | 11 | 0 | 155 |
| CSS | 1 | 0 | 0 | 43 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.34 |
| Average class complexity | 34.62 |
| ▷ Minimum class complexity | 16.00 |
| ▷ Maximum class complexity | 51.00 |
| Average method complexity | 3.82 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 15.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 8 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 8 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 96 | |
| ▷ Static methods | 1 | 1.04% |
| ▷ Public methods | 82 | 85.42% |
| ▷ Protected methods | 10 | 10.42% |
| ▷ Private methods | 4 | 4.17% |
| Functions | 2 | |
| ▷ Named functions | 1 | 50.00% |
| ▷ Anonymous functions | 1 | 50.00% |
| Constants | 6 | |
| ▷ Global constants | 2 | 33.33% |
| ▷ Class constants | 4 | 66.67% |
| ▷ Public constants | 4 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
No PNG images were found in this plugin