Benchmarks
Plugin footprint 65% 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.05MB] [CPU: ▼3.56ms] Passed 4 tests
A check of server-side resources used by WP e-Payouts
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.05 | 37.36 ▼7.40 |
Dashboard /wp-admin | 3.35 ▲0.05 | 44.86 ▼7.25 |
Posts /wp-admin/edit.php | 3.40 ▲0.05 | 46.34 ▲0.79 |
Add New Post /wp-admin/post-new.php | 5.93 ▲0.05 | 93.11 ▲2.12 |
Media Library /wp-admin/upload.php | 3.28 ▲0.05 | 34.82 ▼0.36 |
Wp e-Payouts /wp-admin/options-general.php?page=Wp-Epayouts | 3.32 | 29.60 |
Server storage [IO: ▲0.90MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 26 new files
Database: 1 new table, 6 new options
New tables |
---|
wp_epayouts |
New WordPress options |
---|
widget_recent-posts |
theysaidso_admin_options |
can_compress_scripts |
widget_theysaidso_widget |
db_upgraded |
widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WP e-Payouts
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,804 ▲69 | 13.70 ▼0.69 | 1.75 ▼0.32 | 44.30 ▼0.20 |
Dashboard /wp-admin | 2,210 ▲18 | 4.85 ▼0.11 | 107.57 ▼1.66 | 42.72 ▼2.87 |
Posts /wp-admin/edit.php | 2,093 ▲4 | 1.97 ▼0.05 | 39.21 ▲3.30 | 40.32 ▲5.47 |
Add New Post /wp-admin/post-new.php | 1,545 ▲31 | 18.48 ▲0.93 | 581.45 ▼107.51 | 57.84 ▲0.16 |
Media Library /wp-admin/upload.php | 1,392 ▲4 | 4.20 ▼0.03 | 92.83 ▼20.65 | 40.39 ▼6.79 |
Wp e-Payouts /wp-admin/options-general.php?page=Wp-Epayouts | 1,120 | 2.06 | 29.21 | 27.65 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- Zombie tables detected upon uninstall: 1 table
- wp_epayouts
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Please fix the following server-side errors
- > GET request to /wp-admin/options-general.php?page=Wp-Epayouts
- > User notice in wp-includes/functions.php+5905
Function wpdb::prepare was called incorrectly. The query argument of wpdb::prepare() must have a placeholder. Please see Debugging in WordPress for more information. (This message was added in version 3.9.0.)
- > GET request to /wp-admin/options-general.php?page=Wp-Epayouts
- > User notice in wp-includes/functions.php+5905
Function wpdb::prepare was called incorrectly. The query does not contain the correct number of placeholders (0) for the number of arguments passed (1). Please see Debugging in WordPress for more information. (This message was added in version 4.8.3.)
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
The following issues need your attention
- 2× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to a member function flush() on null in wp-content/plugins/wp-e-payouts/wp-epayouts_admin.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/wp-e-payouts/wp-epayouts.php:22
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Please fix the following attributes:
- Tags: Please reduce the number of tags, currently 25 tag instead of maximum 10
- Screenshots: Please describe screenshot #2 in wp-e-payouts/assets to your readme.txt
wp-e-payouts/wp-epayouts.php 85% from 13 tests
"WP e-Payouts" version 1.1's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please take the time to fix the following:
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
- Main file name: The principal plugin file should be the same as the plugin slug ("wp-e-payouts.php" instead of "wp-epayouts.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Good job! No executable or dangerous file extensions detected457 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 38 | 16 | 453 |
SVG | 2 | 0 | 0 | 4 |
PHP code Passed 2 tests
A brief analysis 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.37 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 8 | |
▷ Named functions | 8 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 5 | |
▷ Global constants | 5 | 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
10 PNG files occupy 0.68MB with 0.43MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/screenshot-1.png | 60.57KB | 21.57KB | ▼ 64.38% |
assets/epayouts.png | 12.01KB | 4.25KB | ▼ 64.64% |
assets/epayouts_en_white.png | 12.57KB | 5.37KB | ▼ 57.27% |
assets/icon-128x128.png | 128.58KB | 47.54KB | ▼ 63.03% |
assets/icon.old.png | 128.58KB | 47.54KB | ▼ 63.03% |