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.01MB] [CPU: ▼5.92ms] Passed 4 tests
Analyzing server-side resources used by WooCommerce Bookings Extensions
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 37.92 ▼8.95 |
Dashboard /wp-admin | 3.31 ▼0.04 | 53.60 ▼11.13 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 48.13 ▼0.78 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 93.61 ▼2.81 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 39.07 ▲0.64 |
Server storage [IO: ▲3.24MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 401 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
can_compress_scripts |
widget_theysaidso_widget |
theysaidso_admin_options |
widget_recent-posts |
widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WooCommerce Bookings Extensions
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲28 | 14.76 ▲0.40 | 1.92 ▲0.11 | 45.38 ▲1.84 |
Dashboard /wp-admin | 2,198 ▲21 | 5.59 ▼0.06 | 84.57 ▼8.03 | 38.47 ▼4.25 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 1.98 ▲0.01 | 33.91 ▼8.05 | 35.57 ▼1.55 |
Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 22.89 ▼0.22 | 698.17 ▲32.09 | 71.10 ▲10.26 |
Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.17 ▼0.03 | 99.93 ▼15.60 | 45.23 ▼2.89 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Good news, no errors were detected
SRP 0% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Almost there! Just fix the following items
- 2× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/woo-bookings-extensions/vendor/symfony/translation/Resources/bin/translation-status.php
- > /wp-content/plugins/woo-bookings-extensions/admin/partials/woocommerce-bookings-extensions-admin-display.php
- 195× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/woo-bookings-extensions/vendor/johngrogg/ics-parser/tests/RecurrencesTest.php:6
- > PHP Fatal error
Uncaught Error: Interface 'Carbon\\Exceptions\\InvalidArgumentException' not found in wp-content/plugins/woo-bookings-extensions/vendor/nesbot/carbon/src/Carbon/Exceptions/InvalidDateException.php:17
- > PHP Fatal error
Uncaught Error: Class 'Symfony\\Component\\Translation\\Loader\\FileLoader' not found in wp-content/plugins/woo-bookings-extensions/vendor/symfony/translation/Loader/CsvFileLoader.php:21
- > PHP Fatal error
Uncaught Error: Interface 'Symfony\\Component\\Translation\\Provider\\ProviderInterface' not found in wp-content/plugins/woo-bookings-extensions/vendor/symfony/translation/Provider/NullProvider.php:20
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/woo-bookings-extensions/vendor/johngrogg/ics-parser/tests/KeyValueTest.php:6
- > PHP Fatal error
Uncaught Error: Interface 'Symfony\\Contracts\\Translation\\TranslatorInterface' not found in wp-content/plugins/woo-bookings-extensions/vendor/symfony/translation/PseudoLocalizationTranslator.php:19
- > PHP Fatal error
Uncaught Error: Interface 'Symfony\\Component\\Translation\\Loader\\LoaderInterface' not found in wp-content/plugins/woo-bookings-extensions/vendor/symfony/translation/Loader/ArrayLoader.php:21
- > PHP Fatal error
Uncaught Error: Interface 'Carbon\\CarbonInterface' not found in wp-content/plugins/woo-bookings-extensions/vendor/nesbot/carbon/src/Carbon/Carbon.php:510
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/woo-bookings-extensions/vendor/symfony/translation/Tests/Formatter/MessageFormatterTest.php:17
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/woo-bookings-extensions/vendor/symfony/translation/Tests/Loader/QtFileLoaderTest.php:18
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
Optimizations
Plugin configuration 90% 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
7 plugin tags: calendar, bookings, booking, woocommerce, accommodation...
woo-bookings-extensions/woocommerce-bookings-extensions.php 77% from 13 tests
The main file in "WooCommerce Bookings Extensions" v. 3.0.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Main file name: Name the main plugin file the same as the plugin slug ("woo-bookings-extensions.php" instead of "woocommerce-bookings-extensions.php")
- Requires PHP: Required version must match the one declared in readme.txt ("8.0.2" instead of "8.0")
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
Code Analysis 3% from 3 tests
File types 0% from 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Almost there! Just fix the following issues
- For security reasons, never distribute binary or executable files with your plugin
- .bat - Batch File in Windows
- ☣ wp-content/plugins/woo-bookings-extensions/vendor/nesbot/carbon/bin/carbon.bat
- ☣ wp-content/plugins/woo-bookings-extensions/vendor/nesbot/carbon/bin/upgrade-carbon.bat
- .bat - Batch File in Windows
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 935 | 9,042 | 28,613 | 46,376 |
JavaScript | 217 | 1,152 | 4,124 | 44,645 |
XSD | 4 | 99 | 76 | 4,991 |
TypeScript | 16 | 175 | 59 | 4,708 |
HTML | 36 | 450 | 0 | 4,009 |
CSS | 24 | 449 | 470 | 1,882 |
JSON | 33 | 0 | 0 | 1,720 |
Markdown | 32 | 349 | 0 | 883 |
XML | 17 | 3 | 0 | 328 |
PO File | 8 | 9 | 1 | 47 |
YAML | 6 | 0 | 0 | 17 |
Qt Linguist | 1 | 0 | 0 | 10 |
DOS Batch | 2 | 0 | 0 | 8 |
INI | 1 | 0 | 0 | 1 |
PHP code 50% from 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Please fix the following
- Cyclomatic complexity of methods has to be reduced to less than 100 (currently 157)
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.42 |
Average class complexity | 14.67 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 311.00 |
Average method complexity | 2.89 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 157.00 |
Code structure | ||
---|---|---|
Namespaces | 40 | |
Interfaces | 31 | |
Traits | 26 | |
Classes | 215 | |
▷ Abstract classes | 14 | 6.51% |
▷ Concrete classes | 201 | 93.49% |
▷ Final classes | 14 | 6.97% |
Methods | 2,201 | |
▷ Static methods | 412 | 18.72% |
▷ Public methods | 1,891 | 85.92% |
▷ Protected methods | 181 | 8.22% |
▷ Private methods | 129 | 5.86% |
Functions | 333 | |
▷ Named functions | 101 | 30.33% |
▷ Anonymous functions | 232 | 69.67% |
Constants | 122 | |
▷ Global constants | 8 | 6.56% |
▷ Class constants | 114 | 93.44% |
▷ Public constants | 111 | 97.37% |
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