Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.34MB] [CPU: ▼4.88ms] Passed 4 tests
An overview of server-side resources used by Pagaris para Woocommerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.84 ▲0.37 | 37.15 ▲0.40 |
| Dashboard /wp-admin | 3.68 ▲0.37 | 49.07 ▲2.47 |
| Posts /wp-admin/edit.php | 3.73 ▲0.37 | 50.99 ▼5.76 |
| Add New Post /wp-admin/post-new.php | 6.20 ▲0.31 | 83.63 ▼16.63 |
| Media Library /wp-admin/upload.php | 3.54 ▲0.31 | 38.78 ▲2.62 |
Server storage [IO: ▲1.00MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 170 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-posts |
| widget_recent-comments |
| widget_theysaidso_widget |
| db_upgraded |
| can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by Pagaris para Woocommerce
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 14.74 ▲0.28 | 1.76 ▼0.02 | 40.28 ▲0.36 |
| Dashboard /wp-admin | 2,206 ▲15 | 4.90 ▼0.01 | 111.67 ▲10.42 | 40.09 ▼5.42 |
| Posts /wp-admin/edit.php | 2,092 ▲6 | 2.15 ▲0.10 | 40.57 ▲0.39 | 35.65 ▲0.23 |
| Add New Post /wp-admin/post-new.php | 1,542 ▲23 | 23.36 ▲0.05 | 666.48 ▼14.55 | 59.79 ▼6.26 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.25 ▲0.07 | 107.97 ▲7.71 | 46.80 ▼0.88 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
The following issues need your attention
- 48× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Handler\\CurlFactoryInterface' not found in wp-content/plugins/pagaris-para-woocommerce/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:15
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Exception\\BadResponseException' not found in wp-content/plugins/pagaris-para-woocommerce/vendor/guzzlehttp/guzzle/src/Exception/ClientException.php:7
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Exception\\RequestException' not found in wp-content/plugins/pagaris-para-woocommerce/vendor/guzzlehttp/guzzle/src/Exception/ConnectException.php:11
- > PHP Fatal error
Uncaught Error: Class 'Pagaris\\TestCase' not found in wp-content/plugins/pagaris-para-woocommerce/vendor/pagaris/pagaris-php/tests/ClientTest.php:4
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Cookie\\CookieJarInterface' not found in wp-content/plugins/pagaris-para-woocommerce/vendor/guzzlehttp/guzzle/src/Cookie/CookieJar.php:10
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/pagaris-para-woocommerce/vendor/guzzlehttp/psr7/src/Stream.php:11
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/pagaris-para-woocommerce/vendor/guzzlehttp/psr7/src/FnStream.php:12
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\MessageInterface' not found in wp-content/plugins/pagaris-para-woocommerce/vendor/psr/http-message/src/RequestInterface.php:24
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\ClientInterface' not found in wp-content/plugins/pagaris-para-woocommerce/vendor/guzzlehttp/guzzle/src/Client.php:25
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Exception\\GuzzleException' not found in wp-content/plugins/pagaris-para-woocommerce/vendor/guzzlehttp/guzzle/src/Exception/TransferException.php:4
- > 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)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Please fix the following attributes:
- Tags: There are too many tags (52 tag instead of maximum 10)
pagaris-para-woocommerce/pagaris-gateway.php 92% from 13 tests
The principal PHP file in "Pagaris para Woocommerce" v. 1.1.6 is loaded by WordPress automatically on each request
You should first fix the following items:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("pagaris-para-woocommerce.php" instead of "pagaris-gateway.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 detected12,741 lines of code in 124 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 102 | 1,773 | 4,837 | 8,889 |
| Markdown | 12 | 1,037 | 0 | 3,269 |
| JSON | 8 | 0 | 0 | 566 |
| make | 1 | 4 | 0 | 9 |
| XML | 1 | 1 | 0 | 8 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.42 |
| Average class complexity | 12.97 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 81.00 |
| Average method complexity | 2.58 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 27.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 9 | |
| Interfaces | 14 | |
| Traits | 2 | |
| Classes | 73 | |
| ▷ Abstract classes | 2 | 2.74% |
| ▷ Concrete classes | 71 | 97.26% |
| ▷ Final classes | 8 | 11.27% |
| Methods | 697 | |
| ▷ Static methods | 80 | 11.48% |
| ▷ Public methods | 572 | 82.07% |
| ▷ Protected methods | 10 | 1.43% |
| ▷ Private methods | 115 | 16.50% |
| Functions | 146 | |
| ▷ Named functions | 59 | 40.41% |
| ▷ Anonymous functions | 87 | 59.59% |
| Constants | 57 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 57 | 100.00% |
| ▷ Public constants | 57 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
No PNG files were detected