Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼4.25ms] Passed 4 tests
Analyzing server-side resources used by DiamondPay payment gateway for WooCommerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.01 | 38.87 ▼7.08 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 52.98 ▲3.40 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 52.53 ▲2.77 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 86.42 ▼13.41 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 37.72 ▲0.71 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-comments |
| db_upgraded |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for DiamondPay payment gateway for WooCommerce
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 13.17 ▼1.56 | 1.77 ▼0.21 | 45.39 ▲2.73 |
| Dashboard /wp-admin | 2,203 ▲15 | 5.77 ▼0.11 | 102.05 ▼1.84 | 39.96 ▼2.08 |
| Posts /wp-admin/edit.php | 2,089 ▼3 | 1.99 ▼0.04 | 36.31 ▼5.51 | 34.61 ▼1.80 |
| Add New Post /wp-admin/post-new.php | 1,514 ▼5 | 17.68 ▼5.61 | 679.05 ▲70.75 | 57.75 ▲6.76 |
| Media Library /wp-admin/upload.php | 1,391 ▲6 | 4.26 ▲0.06 | 95.55 ▼7.58 | 42.86 ▼3.07 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
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
Even though no errors were found, 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 take a closer look at the following
- 1× 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/woo-diamondpay/woo-diamondpay.php:96
- > 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 97% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Attributes that need to be fixed:
- Screenshots: Please describe screenshot #1 in woo-diamondpay/assets to your readme.txt
woo-diamondpay/woo-diamondpay.php Passed 13 tests
The main file in "DiamondPay payment gateway for WooCommerce" v. 1.0.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
45 characters long description:
Add Diamond Payment Gateways for WooCommerce.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Good job! No executable or dangerous file extensions detected79 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 9 | 8 | 79 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.04 |
| Average class complexity | 1.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 1.00 |
| Average method complexity | 1.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 1.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 | 2 | |
| ▷ Named functions | 2 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 1 | |
| ▷ Global constants | 1 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 PNG file occupies 0.02MB with 0.02MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| (invalid) images/diamondlogo.png | 23.50KB | 0.00KB | ▼ 100.00% |