Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.00MB] [CPU: ▼5.79ms] Passed 4 tests
Server-side resources used by Woo Events Manager
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 39.09 ▲0.02 |
Dashboard /wp-admin | 3.31 ▲0.00 | 43.24 ▼5.07 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 41.17 ▼6.80 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 84.84 ▼11.30 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 32.80 ▲0.57 |
Server storage [IO: ▲0.26MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 23 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_recent-posts |
widget_theysaidso_widget |
widget_recent-comments |
widget_ccw_widget |
theysaidso_admin_options |
db_upgraded |
can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for Woo Events Manager
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲65 | 13.26 ▼1.20 | 1.92 ▲0.18 | 43.39 ▲3.20 |
Dashboard /wp-admin | 2,209 ▲23 | 5.86 ▲0.92 | 96.27 ▼9.19 | 41.40 ▼5.44 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.15 ▲0.16 | 33.81 ▼2.92 | 31.68 ▼3.52 |
Add New Post /wp-admin/post-new.php | 1,517 ▼16 | 17.76 ▼5.31 | 657.34 ▼4.57 | 50.60 ▼1.75 |
Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.18 ▼0.03 | 95.26 ▼13.51 | 42.93 ▼0.79 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
Please fix the following items
- This plugin does not fully uninstall, leaving 7 options in the database
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_ccw_widget
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though no errors were found, 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
The following issues need your attention
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/woo-event-manager/includes/admin/class.admin.events-settings-tab.php:6
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/woo-event-manager/includes/widget/ccw_class.php:3
- > 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 90% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Please fix the following attributes:
- Screenshots: Please describe screenshot #6 in woo-event-manager/assets to your readme.txt
woo-event-manager/woocommerce-events-manager.php 85% from 13 tests
This is the main PHP file of "Woo Events Manager" version 1.4.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("woo-event-manager.php" instead of "woocommerce-events-manager.php")
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Success! There were no dangerous files found in this plugin4,889 lines of code in 16 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 4 | 492 | 429 | 3,379 |
PHP | 3 | 420 | 189 | 921 |
CSS | 8 | 203 | 39 | 483 |
PO File | 1 | 42 | 44 | 106 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.38 |
Average class complexity | 36.50 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 72.00 |
Average method complexity | 7.45 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 37.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 11 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 10 | 90.91% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 1 | 9.09% |
Functions | 31 | |
▷ Named functions | 31 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 6 | |
▷ Global constants | 6 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.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
2 PNG files occupy 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/css/widget/images/scanlines_dark.png | 0.93KB | 0.10KB | ▼ 88.92% |
assets/images/scanlines_dark.png | 0.93KB | 0.10KB | ▼ 88.92% |