Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▼0.13MB] [CPU: ▼9.10ms] Passed 4 tests
Server-side resources used by WP Events Manager WooCommerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▼0.03 | 38.83 ▼16.44 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 48.72 ▼8.06 |
| Posts /wp-admin/edit.php | 3.36 ▼0.49 | 62.62 ▲15.06 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 86.94 ▼13.54 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 36.50 ▲1.63 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 11 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-posts |
| db_upgraded |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for WP Events Manager WooCommerce
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,811 ▲40 | 14.47 ▲0.38 | 1.70 ▼0.68 | 40.93 ▼6.10 |
| Dashboard /wp-admin | 2,217 ▲29 | 4.85 ▼0.03 | 116.50 ▲16.08 | 43.26 ▲1.28 |
| Posts /wp-admin/edit.php | 2,100 ▲11 | 2.06 ▲0.08 | 50.51 ▲16.10 | 49.52 ▲15.37 |
| Add New Post /wp-admin/post-new.php | 1,550 ▲22 | 23.27 ▲5.18 | 662.92 ▲33.05 | 61.32 ▲9.06 |
| Media Library /wp-admin/upload.php | 1,393 ▲5 | 4.27 ▲0.06 | 103.41 ▼1.88 | 45.38 ▲2.27 |
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
- Zombie WordPress options were found after uninstall: 6 options
- db_upgraded
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Everything seems fine, however this is by no means an exhaustive test
SRP Passed 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The SRP test was a success
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
These attributes need to be fixed:
- Screenshots: Add descriptions for screenshots #1, #2, #3, #4, #5, #6, #7 in wp-events-manager-woocommerce-payment-methods-integration/assets to your readme.txt
wp-events-manager-woocommerce-payment-methods-integration/wp-events-manager-woocommerce.php 77% from 13 tests
The main PHP script in "WP Events Manager WooCommerce" version 2.0.6 is automatically included on every request by WordPress
The following require your attention:
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
- Main file name: It is recommended to name the main PHP file as the plugin slug ("wp-events-manager-woocommerce-payment-methods-integration.php" instead of "wp-events-manager-woocommerce.php")
- Requires at least: Required version must match the one declared in readme.txt ("4.2" instead of "3.5")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Success! There were no dangerous files found in this plugin377 lines of code in 7 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 114 | 293 | 374 |
| CSS | 1 | 1 | 0 | 3 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.41 |
| Average class complexity | 8.83 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 26.00 |
| Average method complexity | 2.15 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 11.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 | 41 | |
| ▷ Static methods | 3 | 7.32% |
| ▷ Public methods | 41 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 7 | |
| ▷ Global constants | 7 | 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
1 PNG file occupies 0.01MB with 0.01MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/woo_payment.png | 12.30KB | 4.41KB | ▼ 64.12% |