Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼0.52ms] Passed 4 tests
Server-side resources used by CityPay Paylink WooCommerce
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 41.41 ▲0.95 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 48.58 ▼5.59 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 50.31 ▲2.72 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 100.06 ▲3.70 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.00 | 36.82 ▼0.15 |
Server storage [IO: ▲0.16MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 22 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| can_compress_scripts |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-comments |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for CityPay Paylink WooCommerce
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,792 ▲6 | 14.40 ▲0.11 | 1.83 ▼0.13 | 43.91 ▲2.02 |
| Dashboard /wp-admin | 2,198 ▲20 | 5.58 ▼0.09 | 95.59 ▼7.31 | 43.47 ▼5.81 |
| Posts /wp-admin/edit.php | 2,103 ▲6 | 2.00 ▲0.01 | 42.00 ▲4.61 | 36.78 ▼3.41 |
| Add New Post /wp-admin/post-new.php | 1,538 ▲3 | 18.35 ▼0.20 | 631.69 ▼13.49 | 66.24 ▲1.51 |
| Media Library /wp-admin/upload.php | 1,406 ▲6 | 4.14 ▲0.04 | 97.81 ▼21.25 | 44.41 ▼3.51 |
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
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- widget_recent-comments
- widget_recent-posts
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
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
Please take a closer look at the following
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/citypay-payments/not_available.php:3
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/citypay-payments/admin_options.php:8
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 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
4 plugin tags: payment gateway, e-commerce, woocommerce, ecommerce
citypay-payments/wc-payment-gateway-citypay.php 92% from 13 tests
The main PHP file in "CityPay Paylink WooCommerce" ver. 2.1.2 adds more information about the plugin and also serves as the entry point for this plugin
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("citypay-payments.php" instead of "wc-payment-gateway-citypay.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Success! There were no dangerous files found in this plugin873 lines of code in 10 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 9 | 188 | 185 | 835 |
| Markdown | 1 | 13 | 0 | 38 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.19 |
| Average class complexity | 8.33 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 23.00 |
| Average method complexity | 2.10 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 13.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 2 | |
| Classes | 4 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 4 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 40 | |
| ▷ Static methods | 1 | 2.50% |
| ▷ Public methods | 39 | 97.50% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 1 | 2.50% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 3 | |
| ▷ Global constants | 1 | 33.33% |
| ▷ Class constants | 2 | 66.67% |
| ▷ Public constants | 2 | 100.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
11 PNG files occupy 0.10MB with 0.05MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/logo-x500-greyscale.png | 11.20KB | 6.59KB | ▼ 41.18% |
| assets/logo-x250-inverse.png | 7.50KB | 3.45KB | ▼ 54.02% |
| assets/icon-256x256.png | 11.28KB | 4.71KB | ▼ 58.25% |
| assets/logo-x500-block.png | 10.33KB | 6.64KB | ▼ 35.72% |
| assets/logo-x500-white.png | 15.00KB | 6.43KB | ▼ 57.16% |