Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼8.05ms] Passed 4 tests
Server-side resources used by ApcoPay for WooCommerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.01 | 38.35 ▼3.42 |
| Dashboard /wp-admin | 3.32 ▼0.03 | 47.64 ▼19.52 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 50.00 ▲1.29 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 93.51 ▼10.53 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 37.81 ▲2.95 |
Server storage [IO: ▲0.23MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 13 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-comments |
| widget_recent-posts |
| can_compress_scripts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
A check of browser resources used by ApcoPay for WooCommerce
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.72 ▲0.12 | 1.55 ▼0.20 | 43.12 ▼1.04 |
| Dashboard /wp-admin | 2,195 ▲30 | 5.61 ▲0.03 | 89.83 ▼4.19 | 42.72 ▼7.52 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.02 ▼0.01 | 40.40 ▲0.93 | 35.58 ▼3.69 |
| Add New Post /wp-admin/post-new.php | 1,537 ▲9 | 18.34 ▼4.71 | 637.31 ▼36.07 | 77.90 ▲10.23 |
| Media Library /wp-admin/upload.php | 1,400 ▼3 | 4.19 ▲0.02 | 98.20 ▼0.83 | 40.32 ▼4.46 |
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
- The uninstall procedure has failed, leaving 6 options in the database
- theysaidso_admin_options
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- widget_recent-posts
Smoke tests 75% from 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 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
Please take a closer look at the following
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function apply_filters() in wp-content/plugins/apcopay-for-woocommerce/apcopay-for-woocommerce.php:19
- > PHP Fatal error
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 Passed 29 tests
readme.txt Passed 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
7 plugin tags: payment gateway, pay, woocommerce, apcopay, credit card...
apcopay-for-woocommerce/apcopay-for-woocommerce.php Passed 13 tests
The entry point to "ApcoPay for WooCommerce" version 1.6.4 is a PHP file that has certain tags in its header comment area
57 characters long description:
Adds the functionality to pay with ApcoPay to WooCommerce
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
No dangerous file extensions were detected1,985 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 234 | 186 | 1,652 |
| JavaScript | 2 | 24 | 28 | 261 |
| Markdown | 1 | 28 | 0 | 72 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.22 |
| Average class complexity | 165.00 |
| ▷ Minimum class complexity | 165.00 |
| ▷ Maximum class complexity | 165.00 |
| Average method complexity | 8.45 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 31.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 | 22 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 15 | 68.18% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 7 | 31.82% |
| Functions | 7 | |
| ▷ Named functions | 7 | 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
7 PNG files occupy 0.11MB with 0.06MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/banner-1544x500.png | 20.08KB | 8.14KB | ▼ 59.47% |
| assets/icon-128x128.png | 4.11KB | 2.44KB | ▼ 40.69% |
| assets/screenshot-2.png | 15.83KB | 6.61KB | ▼ 58.22% |
| assets/banner-772x250.png | 9.43KB | 4.30KB | ▼ 54.43% |
| assets/icon-256x256.png | 9.62KB | 4.64KB | ▼ 51.78% |