Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.05MB] [CPU: ▼11.57ms] Passed 4 tests
This is a short check of server-side resources used by TargetPay for Woocommerce
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.06 | 35.56 ▼6.41 |
Dashboard /wp-admin | 3.38 ▲0.02 | 45.97 ▼17.72 |
Posts /wp-admin/edit.php | 3.49 ▲0.13 | 47.83 ▼1.89 |
Add New Post /wp-admin/post-new.php | 5.96 ▲0.06 | 91.62 ▼20.24 |
Media Library /wp-admin/upload.php | 3.30 ▲0.06 | 34.79 ▼1.35 |
Server storage [IO: ▲0.15MB] [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: 20 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
can_compress_scripts |
widget_recent-comments |
theysaidso_admin_options |
widget_theysaidso_widget |
widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for TargetPay for Woocommerce
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,790 ▲43 | 14.67 ▲0.33 | 1.75 ▲0.14 | 39.54 ▼2.69 |
Dashboard /wp-admin | 2,198 ▲21 | 5.64 ▼0.00 | 93.87 ▼0.23 | 40.08 ▼3.13 |
Posts /wp-admin/edit.php | 2,100 ▼3 | 1.99 ▼0.02 | 39.64 ▲3.35 | 38.87 ▲9.73 |
Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.57 ▲0.56 | 605.25 ▼69.62 | 47.49 ▼12.15 |
Media Library /wp-admin/upload.php | 1,400 ▲6 | 4.18 ▲0.05 | 93.73 ▼5.71 | 41.24 ▼0.84 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please fix the following
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function apply_filters() in wp-content/plugins/targetpay-by-idealpluginsnl/targetpay.php:21
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
There were no browser issues found
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% 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:
- Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line (
=== targetpay-by-idealpluginsnl ===
) - Screenshots: No descriptions were found for these screenshots #2, #3, #4 in targetpay-by-idealpluginsnl/assets to your readme.txt
targetpay-by-idealpluginsnl/targetpay.php 85% from 13 tests
Analyzing the main PHP file in "TargetPay for Woocommerce" version 2.2.1 - bugfixes...
It is important to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("targetpay-by-idealpluginsnl.php" instead of "targetpay.php")
- Version: Plugin version number should only contain digits separated by dots (ex. "1.0.3" instead of "2.2.1 - bugfixes...")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
Good job! No executable or dangerous file extensions detected723 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 166 | 168 | 706 |
Markdown | 1 | 11 | 0 | 17 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.21 |
Average class complexity | 8.33 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 41.00 |
Average method complexity | 2.43 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.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 | 46 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 44 | 95.65% |
▷ Protected methods | 1 | 2.17% |
▷ Private methods | 1 | 2.17% |
Functions | 1 | |
▷ Named functions | 1 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 12 | |
▷ Global constants | 1 | 8.33% |
▷ Class constants | 11 | 91.67% |
▷ Public constants | 11 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
13 PNG files occupy 0.06MB with 0.02MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/admin_header.png | 5.23KB | 2.52KB | ▼ 51.77% |
images/MRC_24.png | 2.18KB | 1.15KB | ▼ 47.06% |
images/MRC_60.png | 4.63KB | 1.95KB | ▼ 58.01% |
images/IDE_60.png | 3.61KB | 2.18KB | ▼ 39.72% |
images/AFT_24.png | 1.32KB | 1.43KB | 0.00% |