Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.05MB] [CPU: ▼8.87ms] Passed 4 tests
Server-side resources used by payabl. Payments Gateway
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.95 ▼0.52 | 17.13 ▼28.70 |
Dashboard /wp-admin | 3.41 ▲0.11 | 46.38 ▼0.90 |
Posts /wp-admin/edit.php | 3.46 ▲0.11 | 49.07 ▲1.37 |
Add New Post /wp-admin/post-new.php | 5.99 ▲0.11 | 89.57 ▼6.21 |
Media Library /wp-admin/upload.php | 3.33 ▲0.11 | 34.18 ▲0.33 |
Server storage [IO: ▲0.26MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 34 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
theysaidso_admin_options |
db_upgraded |
widget_recent-posts |
widget_theysaidso_widget |
widget_recent-comments |
Browser metrics Passed 4 tests
payabl. Payments Gateway: an overview of browser usage
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,449 ▼297 | 13.94 ▼0.42 | 0.53 ▼0.98 | 19.73 ▼19.71 |
Dashboard /wp-admin | 2,199 ▲27 | 5.64 ▼0.01 | 89.15 ▼15.36 | 43.89 ▲1.31 |
Posts /wp-admin/edit.php | 2,104 ▲7 | 1.97 ▼0.06 | 40.43 ▲5.40 | 36.45 ▼2.13 |
Add New Post /wp-admin/post-new.php | 1,539 ▲10 | 18.04 ▼5.08 | 604.76 ▼56.82 | 83.41 ▲26.00 |
Media Library /wp-admin/upload.php | 1,404 ▲10 | 4.28 ▲0.11 | 95.67 ▼13.12 | 44.85 ▼3.58 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The following items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Almost there! Just fix the following items
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/powercash21-payments-gateway/includes/payment-methods/class-wc-gateway-amex.php:11
- > PHP Fatal error
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 83% from 29 tests
readme.txt 94% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
These attributes need your attention:
- Tags: Please reduce the number of tags, currently 12 tag instead of maximum 10
powercash21-payments-gateway/class-wc-gateway-payabl.php 69% from 13 tests
The main PHP script in "payabl. Payments Gateway" version 2.0.4 is automatically included on every request by WordPress
It is important to fix the following:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Main file name: The principal plugin file should be the same as the plugin slug ("powercash21-payments-gateway.php" instead of "class-wc-gateway-payabl.php")
- Domain Path: The domain path folder does not exist ("/languages")
- Requires at least: The required version number must match the one declared in readme.txt ("5.0" instead of "3.9.3")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Success! There were no dangerous files found in this plugin3,500 lines of code in 17 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 17 | 661 | 885 | 3,500 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.28 |
Average class complexity | 19.69 |
▷ Minimum class complexity | 5.00 |
▷ Maximum class complexity | 128.00 |
Average method complexity | 3.96 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 44.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 16 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 16 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 101 | |
▷ Static methods | 15 | 14.85% |
▷ Public methods | 85 | 84.16% |
▷ Protected methods | 16 | 15.84% |
▷ Private methods | 0 | 0.00% |
Functions | 11 | |
▷ Named functions | 11 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 30 | |
▷ Global constants | 30 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
5 PNG files occupy 0.01MB with 0.00MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/payabl_instant_bank_transfer.png | 0.76KB | 0.75KB | ▼ 1.54% |
assets/payabl_paypal.png | 2.40KB | 1.69KB | ▼ 29.54% |
assets/payabl_applepay.png | 2.11KB | 1.38KB | ▼ 34.43% |
assets/payabl_amex.png | 3.18KB | 1.81KB | ▼ 42.91% |
assets/payabl_trustly_80.png | 1.73KB | 1.96KB | 0.00% |