Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼3.56ms] Passed 4 tests
Analyzing server-side resources used by Maakapay Checkout For Woocommerce
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 41.19 ▼0.88 |
Dashboard /wp-admin | 3.31 ▲0.00 | 47.31 ▼5.23 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 49.05 ▼1.40 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 86.45 ▼6.73 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 37.07 ▼0.70 |
Server storage [IO: ▲0.24MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 19 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
can_compress_scripts |
db_upgraded |
widget_theysaidso_widget |
widget_recent-posts |
widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Maakapay Checkout For Woocommerce
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,814 ▲53 | 14.34 ▲0.06 | 2.05 ▼0.30 | 46.51 ▲0.56 |
Dashboard /wp-admin | 2,192 ▲18 | 5.63 ▼0.02 | 83.77 ▼12.38 | 45.65 ▲6.86 |
Posts /wp-admin/edit.php | 2,100 ▼3 | 1.98 ▼0.06 | 36.54 ▼5.27 | 32.97 ▼2.13 |
Add New Post /wp-admin/post-new.php | 1,526 ▼2 | 23.24 ▲0.05 | 673.89 ▼37.02 | 61.17 ▲5.47 |
Media Library /wp-admin/upload.php | 1,403 ▲3 | 4.22 ▼0.03 | 100.48 ▼14.36 | 47.49 ▼2.11 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- db_upgraded
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 9× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Notice
Trying to get property 'prefix' of non-object in wp-content/plugins/maakapay-checkout-for-woocommerce/admin/partials/maakapay-for-woocommerce-checkout-admin-transaction-detail.php on line 18
- > PHP Fatal error
Uncaught Error: Call to undefined function get_header() in wp-content/plugins/maakapay-checkout-for-woocommerce/public/partials/maakapay-for-woocommerce-checkout-public-payment-cancel.php:15
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-admin/includes/class-wp-list-table.php' (include_path='.:/usr/share/php') in wp-content/plugins/maakapay-checkout-for-woocommerce/admin/partials/maakapay-for-woocommerce-checkout-admin-display.php on line 15
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/maakapay-checkout-for-woocommerce/includes/class-maakapay-for-woocommerce-checkout-payment-gateway.php:7
- > PHP Fatal error
Uncaught Error: Call to a member function get_results() on null in wp-content/plugins/maakapay-checkout-for-woocommerce/admin/partials/maakapay-for-woocommerce-checkout-admin-transaction-detail.php:20
- > PHP Fatal error
Uncaught Error: Call to undefined function get_header() in wp-content/plugins/maakapay-checkout-for-woocommerce/public/partials/maakapay-for-woocommerce-checkout-public-payment-success.php:16
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/maakapay-checkout-for-woocommerce/admin/partials/maakapay-for-woocommerce-checkout-admin-display.php on line 15
- > PHP Fatal error
Uncaught Error: Call to undefined function get_header() in wp-content/plugins/maakapay-checkout-for-woocommerce/public/partials/maakapay-for-woocommerce-checkout-public-payment-decline.php:15
- > PHP Warning
require_once(ABSPATHwp-admin/includes/class-wp-list-table.php): failed to open stream: No such file or directory in wp-content/plugins/maakapay-checkout-for-woocommerce/admin/partials/maakapay-for-woocommerce-checkout-admin-display.php on line 15
- > PHP Notice
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 90% 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 to be fixed:
- Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line (
=== maakapay-checkout-for-woocommerce ===
)
maakapay-checkout-for-woocommerce/maakapay-for-woocommerce-checkout.php 85% from 13 tests
The principal PHP file in "Maakapay Checkout For Woocommerce" v. 1.1.0 is loaded by WordPress automatically on each request
Please take the time to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("maakapay-checkout-for-woocommerce.php" instead of "maakapay-for-woocommerce-checkout.php")
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 154 characters long)
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
Everything looks great! No dangerous files found in this plugin1,048 lines of code in 14 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 13 | 341 | 223 | 1,047 |
CSS | 1 | 0 | 6 | 1 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.40 |
Average class complexity | 10.00 |
▷ Minimum class complexity | 4.00 |
▷ Maximum class complexity | 25.00 |
Average method complexity | 4.00 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 15.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 6 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 6 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 18 | |
▷ Static methods | 6 | 33.33% |
▷ Public methods | 18 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 8 | |
▷ Named functions | 8 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 2 | |
▷ Global constants | 2 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
There were not PNG files found in your plugin