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: ▼5.01ms] Passed 4 tests
This is a short check of server-side resources used by AggrePay for WooCommerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 40.13 ▼2.36 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 49.01 ▲0.41 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 50.22 ▲1.17 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 85.79 ▼18.12 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 37.63 ▲0.04 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 4 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for AggrePay for WooCommerce
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.24 ▲0.04 | 1.56 ▼0.21 | 43.85 ▼0.69 |
| Dashboard /wp-admin | 2,198 ▲21 | 5.62 ▲0.02 | 90.09 ▲2.88 | 41.20 ▼0.77 |
| Posts /wp-admin/edit.php | 2,103 ▲3 | 2.03 ▲0.02 | 38.82 ▲3.40 | 35.81 ▼4.50 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.21 ▲0.15 | 595.98 ▼57.34 | 53.70 ▲3.03 |
| Media Library /wp-admin/upload.php | 1,400 ▼3 | 4.18 ▼0.09 | 100.80 ▼4.65 | 43.93 ▲1.25 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however this is by no means an exhaustive test
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 take a closer look at the following
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/woo-aggrepay/index.php on line 14
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_basename() in wp-content/plugins/woo-aggrepay/index.php:14
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
6 plugin tags: aggrepay, paymentgateway, payments, woocommerce, ecommerce...
woo-aggrepay/index.php 92% from 13 tests
The main PHP script in "AggrePay for WooCommerce" version 1.0.9 is automatically included on every request by WordPress
Please make the necessary changes and fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("woo-aggrepay.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
No dangerous file extensions were detected308 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 51 | 51 | 308 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.24 |
| Average class complexity | 29.00 |
| ▷ Minimum class complexity | 29.00 |
| ▷ Maximum class complexity | 29.00 |
| Average method complexity | 4.11 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 15.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 | 9 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 9 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 3 | |
| ▷ Named functions | 3 | 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
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.04MB with 0.03MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/aggrepay.png | 43.72KB | 14.30KB | ▼ 67.29% |