Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Installer ran successfully
Server metrics [RAM: ▼0.95MB] [CPU: ▼39.11ms] Passed 4 tests
Analyzing server-side resources used by Payolee Website Payments for WP
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 38.34 ▼0.60 |
| Dashboard /wp-admin | 3.00 ▼0.34 | 24.39 ▼43.40 |
| Posts /wp-admin/edit.php | 3.00 ▼0.35 | 24.42 ▼27.92 |
| Add New Post /wp-admin/post-new.php | 3.00 ▼2.88 | 25.68 ▼77.15 |
| Media Library /wp-admin/upload.php | 3.00 ▼0.23 | 28.44 ▼7.98 |
| Payolee /wp-admin/tools.php?page=payolee-accept-website-payments-for-wp/payolee-wp-shortcode.php | 3.00 | 25.51 |
Server storage [IO: ▲0.25MB] [DB: ▲0.00MB] 67% from 3 tests
How much does this plugin use your filesystem and database?
Please try to fix the following items
- You have illegally modified 1 file (4.00KB) outside of "wp-content/plugins/payolee-accept-website-payments-for-wp/" and "wp-content/uploads/"
- (new file) wp-content/mgd_mirror/mgd_maximinodotpy-gitdown-test-repository
Filesystem: 9 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-posts |
| db_upgraded |
| widget_recent-comments |
Browser metrics Passed 4 tests
Payolee Website Payments for WP: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,819 ▲58 | 13.25 ▼1.33 | 4.75 ▲2.85 | 43.71 ▼1.71 |
| Dashboard /wp-admin | 2,225 ▲25 | 5.83 ▲0.94 | 107.22 ▲2.15 | 42.15 ▲2.04 |
| Posts /wp-admin/edit.php | 2,104 ▲4 | 2.04 ▲0.02 | 38.86 ▲0.75 | 35.87 ▲2.67 |
| Add New Post /wp-admin/post-new.php | 1,548 ▲17 | 23.19 ▼0.09 | 645.51 ▼49.58 | 55.62 ▼9.44 |
| Media Library /wp-admin/upload.php | 1,404 ▲4 | 4.27 ▲0.09 | 108.86 ▼4.02 | 46.43 ▲0.83 |
| Payolee /wp-admin/tools.php?page=payolee-accept-website-payments-for-wp/payolee-wp-shortcode.php | 885 | 2.01 | 23.79 | 28.20 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- The plugin did not uninstall gracefully
- > User notice in wp-includes/functions.php+5905
Function add_submenu_page was called incorrectly. The seventh parameter passed to add_submenu_page() should be numeric representing menu position. Please see Debugging in WordPress for more information. (This message was added in version 5.3.0.)
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Smoke test failed, please fix the following
- > GET request to /wp-admin/tools.php?page=payolee-accept-website-payments-for-wp/payolee-wp-shortcode.php
- > User notice in wp-includes/functions.php+5905
Function add_submenu_page was called incorrectly. The seventh parameter passed to add_submenu_page() should be numeric representing menu position. Please see Debugging in WordPress for more information. (This message was added in version 5.3.0.)
SRP 0% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please fix the following items
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/payolee-accept-website-payments-for-wp/payolee-wp-shortcode.php
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_url() in wp-content/plugins/payolee-accept-website-payments-for-wp/page.php:15
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/payolee-accept-website-payments-for-wp/shortcodes.php:45
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
These attributes need your attention:
- Tags: Too many tags (30 tag instead of maximum 10); only the first 5 tags are used in your directory listing
- Screenshots: Add images for these screenshots: #1 (Copy the shortcode for the payment form from your Payolee account.), #2 (Paste the shortcode into the Text or Visual editor area of your Wordpress admin.), #3 (The form will embed in that page or post.), #4 (The Button example on that page or post.)
payolee-accept-website-payments-for-wp/payolee-wp-shortcode.php 92% from 13 tests
The entry point to "Payolee Website Payments for WP" version 1.0 is a PHP file that has certain tags in its header comment area
Please make the necessary changes and fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("payolee-accept-website-payments-for-wp.php" instead of "payolee-wp-shortcode.php")
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 detected88 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 35 | 39 | 88 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.33 |
| 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 | 3 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 3 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 1 | |
| ▷ Named functions | 1 | 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
4 PNG files occupy 0.21MB with 0.14MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-4.png | 60.70KB | 20.55KB | ▼ 66.15% |
| screenshot-3.png | 69.21KB | 22.77KB | ▼ 67.10% |
| screenshot-2.png | 50.25KB | 15.99KB | ▼ 68.19% |
| screenshot-1.png | 29.96KB | 10.24KB | ▼ 65.82% |