Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼4.86ms] Passed 4 tests
Analyzing server-side resources used by Paywong Payments
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 37.05 ▼10.05 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 47.65 ▼4.01 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 52.56 ▼0.71 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 96.25 ▼4.68 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 36.54 ▲2.51 |
Server storage [IO: ▲17.49MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 1,060 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| db_upgraded |
| widget_recent-posts |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for Paywong Payments
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲65 | 13.71 ▼0.93 | 1.73 ▼0.59 | 40.46 ▼2.05 |
| Dashboard /wp-admin | 2,209 ▲18 | 4.87 ▼0.04 | 109.41 ▲5.01 | 41.47 ▼3.39 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.06 ▲0.01 | 40.10 ▼0.83 | 34.48 ▼2.38 |
| Add New Post /wp-admin/post-new.php | 1,519 ▲5 | 23.13 ▲5.61 | 622.32 ▲17.53 | 49.06 ▼3.90 |
| Media Library /wp-admin/upload.php | 1,382 ▼9 | 4.18 ▲0.05 | 98.51 ▼1.70 | 42.25 ▲1.21 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
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
Almost there! Just fix the following items
- 77× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'ActionScheduler_UnitTestCase' not found in wp-content/plugins/paywong-payments/libraries/action-scheduler/tests/phpunit/jobs/ActionScheduler_Action_Test.php:7
- > PHP Fatal error
Uncaught Error: Class 'ActionScheduler_Abstract_RecurringSchedule' not found in wp-content/plugins/paywong-payments/libraries/action-scheduler/classes/schedules/ActionScheduler_IntervalSchedule.php:6
- > PHP Fatal error
Uncaught Error: Class 'ActionScheduler_DBStore' not found in wp-content/plugins/paywong-payments/libraries/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php:10
- > PHP Fatal error
Uncaught Error: Class 'ActionScheduler_Store_Deprecated' not found in wp-content/plugins/paywong-payments/libraries/action-scheduler/classes/abstracts/ActionScheduler_Store.php:7
- > PHP Fatal error
Uncaught Error: Class 'ActionScheduler_UnitTestCase' not found in wp-content/plugins/paywong-payments/libraries/action-scheduler/tests/phpunit/versioning/ActionScheduler_Versions_Test.php:6
- > PHP Fatal error
Uncaught Error: Class 'ActionScheduler_UnitTestCase' not found in wp-content/plugins/paywong-payments/libraries/action-scheduler/tests/phpunit/migration/Config_Test.php:9
- > PHP Fatal error
Uncaught Error: Class 'ActionScheduler_UnitTestCase' not found in wp-content/plugins/paywong-payments/libraries/action-scheduler/tests/phpunit/migration/LogMigrator_Test.php:9
- > PHP Fatal error
Uncaught Error: Class 'ActionScheduler_UnitTestCase' not found in wp-content/plugins/paywong-payments/libraries/action-scheduler/tests/phpunit/helpers/ActionScheduler_TimezoneHelper_Test.php:6
- > PHP Fatal error
Uncaught Error: Class 'ActionScheduler_UnitTestCase' not found in wp-content/plugins/paywong-payments/libraries/action-scheduler/tests/phpunit/schedules/ActionScheduler_SimpleSchedule_Test.php:7
- > PHP Fatal error
Uncaught Error: Class 'ActionScheduler_UnitTestCase' not found in wp-content/plugins/paywong-payments/libraries/action-scheduler/tests/phpunit/migration/Scheduler_Test.php:10
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
2 plugin tags: crypto, payments
paywong-payments/paywong-for-woocommerce.php 92% from 13 tests
The entry point to "Paywong Payments" version 2.0.6 is a PHP file that has certain tags in its header comment area
Please take the time to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("paywong-payments.php" instead of "paywong-for-woocommerce.php")
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
Success! There were no dangerous files found in this plugin105,561 lines of code in 1,028 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 195 | 3,858 | 11,835 | 79,386 |
| JSON | 669 | 0 | 0 | 13,086 |
| PHP | 128 | 2,523 | 5,768 | 9,787 |
| TypeScript | 5 | 40 | 933 | 1,419 |
| Markdown | 19 | 694 | 0 | 1,395 |
| Bourne Shell | 1 | 23 | 11 | 147 |
| YAML | 4 | 15 | 6 | 111 |
| XML | 3 | 8 | 3 | 91 |
| HTML | 2 | 8 | 0 | 52 |
| Sass | 1 | 10 | 0 | 47 |
| SVG | 1 | 0 | 0 | 40 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.21 |
| Average class complexity | 8.99 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 85.00 |
| Average method complexity | 2.15 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 40.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 5 | |
| Interfaces | 3 | |
| Traits | 0 | |
| Classes | 113 | |
| ▷ Abstract classes | 16 | 14.16% |
| ▷ Concrete classes | 97 | 85.84% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 835 | |
| ▷ Static methods | 85 | 10.18% |
| ▷ Public methods | 662 | 79.28% |
| ▷ Protected methods | 142 | 17.01% |
| ▷ Private methods | 31 | 3.71% |
| Functions | 40 | |
| ▷ Named functions | 23 | 57.50% |
| ▷ Anonymous functions | 17 | 42.50% |
| Constants | 36 | |
| ▷ Global constants | 2 | 5.56% |
| ▷ Class constants | 34 | 94.44% |
| ▷ Public constants | 34 | 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
7 PNG files occupy 0.02MB with 0.01MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| libraries/action-scheduler/docs/android-chrome-256x256.png | 2.93KB | 3.03KB | 0.00% |
| includes/assets/icon.png | 0.70KB | 0.63KB | ▼ 10.45% |
| libraries/action-scheduler/docs/favicon-32x32.png | 1.16KB | 0.71KB | ▼ 39.02% |
| libraries/action-scheduler/docs/android-chrome-192x192.png | 6.77KB | 2.46KB | ▼ 63.68% |
| libraries/action-scheduler/docs/mstile-150x150.png | 4.15KB | 3.67KB | ▼ 11.47% |