Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Install script ran successfully
Server metrics [RAM: ▲0.05MB] [CPU: ▼5.29ms] Passed 4 tests
Analyzing server-side resources used by Payza Payments
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.04 | 41.77 ▲3.66 |
Dashboard /wp-admin | 3.36 ▲0.05 | 53.25 ▲1.84 |
Posts /wp-admin/edit.php | 3.41 ▲0.05 | 47.85 ▼4.84 |
Add New Post /wp-admin/post-new.php | 5.94 ▲0.05 | 85.85 ▼21.82 |
Media Library /wp-admin/upload.php | 3.28 ▲0.05 | 42.60 ▲7.59 |
Shortcode /wp-admin/admin.php?page=payza-payments-shortcode | 3.23 | 32.22 |
Help /wp-admin/admin.php?page=payza-payments-help | 3.23 | 27.82 |
Payments history /wp-admin/admin.php?page=payza-payments-history | 3.23 | 28.97 |
Configuration /wp-admin/admin.php?page=payza-payments-configuration | 3.23 | 33.22 |
Payza /wp-admin/admin.php?page=payza-payments | 3.23 | 29.89 |
Server storage [IO: ▲0.68MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 24 new files
Database: 1 new table, 6 new options
New tables |
---|
hccoder_payza |
New WordPress options |
---|
theysaidso_admin_options |
can_compress_scripts |
widget_recent-comments |
db_upgraded |
widget_theysaidso_widget |
widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for Payza Payments
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,827 ▲66 | 14.34 ▼0.01 | 1.67 ▲0.06 | 43.19 ▼0.39 |
Dashboard /wp-admin | 2,227 ▲50 | 5.52 ▼0.10 | 91.20 ▲1.24 | 75.40 ▲32.77 |
Posts /wp-admin/edit.php | 2,135 ▲32 | 2.00 ▲0.02 | 33.81 ▼10.39 | 36.84 ▲1.08 |
Add New Post /wp-admin/post-new.php | 1,710 ▲182 | 22.13 ▼1.01 | 768.49 ▲51.92 | 55.60 ▼3.88 |
Media Library /wp-admin/upload.php | 1,438 ▲38 | 4.07 ▼0.13 | 110.39 ▲1.24 | 84.15 ▲34.68 |
Shortcode /wp-admin/admin.php?page=payza-payments-shortcode | 811 | 2.01 | 29.84 | 26.40 |
Help /wp-admin/admin.php?page=payza-payments-help | 803 | 2.00 | 24.38 | 21.75 |
Payments history /wp-admin/admin.php?page=payza-payments-history | 826 | 2.00 | 24.79 | 27.10 |
Configuration /wp-admin/admin.php?page=payza-payments-configuration | 951 | 2.18 | 24.36 | 27.43 |
Payza /wp-admin/admin.php?page=payza-payments | 842 | 2.02 | 25.46 | 27.23 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- Zombie tables detected upon uninstall: 1 table
- hccoder_payza
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
These errors were triggered by the plugin
- > GET request to /wp-admin/admin.php?page=payza-payments-shortcode
- > Deprecated in wp-includes/class-wp-hook.php+310
Non-static method HCCoder_PayzaAdmin::adminShortcode() should not be called statically
- > GET request to /wp-admin/admin.php?page=payza-payments-help
- > Deprecated in wp-includes/class-wp-hook.php+310
Non-static method HCCoder_PayzaAdmin::adminHelp() should not be called statically
- > GET request to /wp-admin/admin.php?page=payza-payments-history
- > Deprecated in wp-includes/class-wp-hook.php+310
Non-static method HCCoder_PayzaAdmin::adminHistory() should not be called statically
- > GET request to /wp-admin/admin.php?page=payza-payments-configuration
- > Deprecated in wp-includes/class-wp-hook.php+310
Non-static method HCCoder_PayzaAdmin::adminConfiguration() should not be called statically
- > GET request to /wp-admin/admin.php?page=payza-payments
- > Deprecated in wp-includes/class-wp-hook.php+310
Non-static method HCCoder_PayzaAdmin::adminIndex() should not be called statically
SRP 0% 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 items
- 2× PHP files output text when accessed directly:
- > /wp-content/plugins/payza-payments/views/adminhistory.php
- > /wp-content/plugins/payza-payments/views/adminhelp.php
- 15× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Notice
Undefined variable: config in wp-content/plugins/payza-payments/views/adminconfiguration.php on line 5
- > PHP Warning
count(): Parameter must be an array or an object that implements Countable in wp-content/plugins/payza-payments/views/adminhistory.php on line 4
- > PHP Fatal error
Uncaught Error: Call to a member function getItem() on null in wp-content/plugins/payza-payments/views/adminhistoryedit.php:5
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/payza-payments/payza-payments.php on line 11
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/payza-payments/views/adminshortcode.php:4
- > PHP Fatal error
Uncaught Error: Call to a member function getItem() on null in wp-content/plugins/payza-payments/views/adminconfiguration.php:5
- > PHP Fatal error
require(): Failed opening required 'ABSPATHwp-content/plugins/payza-payments/classes/config.php' (include_path='.:/usr/share/php') in wp-content/plugins/payza-payments/payza-payments.php on line 11
- > PHP Notice
Undefined variable: rows in wp-content/plugins/payza-payments/views/adminhistory.php on line 4
- > PHP Fatal error
Uncaught Error: Call to a member function getItem() on null in wp-content/plugins/payza-payments/views/adminindex.php:16
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/payza-payments/views/frontendshortcode.php:1
- > PHP Notice
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 93% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
These attributes need your attention:
- Screenshots: These screenshots require images: #1 (The configuration screen of Payza Payments), #2 (Shortcode support), #3 (Payments history), #4 (Payment details)
- Donate link: Please fix this invalid URI: ""
payza-payments/payza-payments.php Passed 13 tests
"Payza Payments" version 1.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
54 characters long description:
Easy integration of Payza payments / AlertPay payments
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
No dangerous file extensions were detected564 lines of code in 14 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 14 | 112 | 86 | 564 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.30 |
Average class complexity | 10.00 |
▷ Minimum class complexity | 4.00 |
▷ Maximum class complexity | 19.00 |
Average method complexity | 3.45 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 15.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 3 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 3 | 100.00% |
▷ Final classes | 1 | 33.33% |
Methods | 11 | |
▷ Static methods | 2 | 18.18% |
▷ Public methods | 10 | 90.91% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 1 | 9.09% |
Functions | 2 | |
▷ Named functions | 2 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 compressed PNG file occupies 0.00MB
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
static/images/icon.png | 0.67KB | 0.60KB | ▼ 10.40% |