Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▼0.00MB] [CPU: ▼164.75ms] Passed 4 tests
Analyzing server-side resources used by Checkout Field Editor - Checkoutify
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.84 ▲0.00 | 31.22 ▲1.57 |
| Dashboard /wp-admin | 3.06 ▼0.00 | 33.21 ▼9.96 |
| Posts /wp-admin/edit.php | 3.11 ▲0.00 | 37.43 ▼2.79 |
| Add New Post /wp-admin/post-new.php | 5.42 ▼0.02 | 75.66 ▼647.81 |
| Media Library /wp-admin/upload.php | 3.00 ▲0.00 | 31.33 ▲7.52 |
Server storage [IO: ▲0.45MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 62 new files
Database: no new tables, 1 new option
| New WordPress options |
|---|
| cfe_do_activation_redirect |
Browser metrics Passed 4 tests
Checking browser requirements for Checkout Field Editor - Checkoutify
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,666 ▲65 | 15.80 ▼0.10 | 4.93 ▼0.68 | 77.17 ▲3.73 |
| Dashboard /wp-admin | 2,929 ▲33 | 6.04 ▼0.24 | 115.08 ▼17.89 | 167.49 ▼8.54 |
| Posts /wp-admin/edit.php | 2,740 ▼0 | 3.24 ▲0.14 | 65.50 ▼1.81 | 136.91 ▼8.41 |
| Add New Post /wp-admin/post-new.php | 3,917 ▲187 | 19.11 ▲0.54 | 406.58 ▼42.57 | 168.91 ▼3.57 |
| Media Library /wp-admin/upload.php | 1,755 ▲3 | 5.50 ▼0.05 | 151.07 ▼0.60 | 183.96 ▲0.18 |
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 1 option in the database
- cfe_do_activation_redirect
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
The smoke test was a success, however most plugin functionality was not tested
SRP 0% 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
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/checkout-field-editor-checkoutify/public/partials/checkout-field-editor-public-display.php
- 11× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/checkout-field-editor-checkoutify/admin/partials/confirmation-alert-restore.php:16
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/checkout-field-editor-checkoutify/admin/partials/checkout-field-editor-admin-display.php:41
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/checkout-field-editor-checkoutify/admin/partials/confirmation-alert-restore.php:16
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/checkout-field-editor-checkoutify/admin/partials/confirmation-alert-restore.php:16
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/checkout-field-editor-checkoutify/admin/partials/confirmation-alert-restore.php:16
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/checkout-field-editor-checkoutify/admin/partials/confirmation-alert.php:16
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/checkout-field-editor-checkoutify/admin/partials/edit-checkout-field-drawer.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/checkout-field-editor-checkoutify/admin/partials/edit-field-billing-tab.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/checkout-field-editor-checkoutify/admin/partials/add-checkout-field-drawer.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/checkout-field-editor-checkoutify/admin/partials/edit-field-additional-tab.php:11
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 86% 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
These attributes need your attention:
- Tags: Please reduce the number of tags, currently 11 tag instead of maximum 10
checkout-field-editor-checkoutify/checkout-fields-editor.php 77% from 13 tests
The entry point to "Checkout Field Editor - Checkoutify" version 1.0.1 is a PHP file that has certain tags in its header comment area
The following require your attention:
- Description: Please don't use more than 140 characters for the plugin description (currently 148 characters long)
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
- Main file name: It is recommended to name the main PHP file as the plugin slug ("checkout-field-editor-checkoutify.php" instead of "checkout-fields-editor.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Good job! No executable or dangerous file extensions detected9,482 lines of code in 53 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 37 | 984 | 1,843 | 4,529 |
| CSS | 3 | 30 | 15 | 3,106 |
| Sass | 6 | 141 | 21 | 951 |
| JavaScript | 3 | 163 | 141 | 622 |
| Markdown | 2 | 67 | 0 | 188 |
| JSON | 1 | 0 | 0 | 55 |
| XML | 1 | 4 | 12 | 31 |
PHP code Passed 2 tests
This is a very shot review 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.41 |
| Average class complexity | 32.56 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 115.00 |
| Average method complexity | 3.67 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 47.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 3 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 16 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 16 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 190 | |
| ▷ Static methods | 23 | 12.11% |
| ▷ Public methods | 142 | 74.74% |
| ▷ Protected methods | 6 | 3.16% |
| ▷ Private methods | 42 | 22.11% |
| Functions | 6 | |
| ▷ Named functions | 5 | 83.33% |
| ▷ Anonymous functions | 1 | 16.67% |
| Constants | 5 | |
| ▷ Global constants | 5 | 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
No PNG images were found in this plugin