Benchmarks
Plugin footprint 65% 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: ▲5.37MB] [CPU: ▲30.22ms] 75% from 4 tests
Server-side resources used by Booking Weir
Please fix the following
- Extra RAM: The extra memory usage must be under 5MB (currently 5.37MB on /wp-admin/admin.php?page=freemius)
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 8.87 ▲5.14 | 88.83 ▲41.31 |
| Dashboard /wp-admin | 9.05 ▲5.42 | 88.44 ▲16.24 |
| Posts /wp-admin/edit.php | 9.10 ▲5.42 | 87.77 ▲35.47 |
| Add New Post /wp-admin/post-new.php | 11.78 ▲5.63 | 128.44 ▲27.86 |
| Media Library /wp-admin/upload.php | 9.00 ▲5.51 | 86.89 ▲50.23 |
| Freemius Debug [v.2.4.3] /wp-admin/admin.php?page=freemius | 9.14 | 74.48 |
Server storage [IO: ▲19.83MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 1,359 new files
Database: no new tables, 10 new options
| New WordPress options |
|---|
| fs_accounts |
| widget_recent-comments |
| widget_recent-posts |
| fs_debug_mode |
| widget_theysaidso_widget |
| fs_gdpr |
| theysaidso_admin_options |
| fs_active_plugins |
| db_upgraded |
| can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Booking Weir
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,851 ▲90 | 14.62 ▲0.25 | 1.84 ▲0.04 | 29.77 ▼9.10 |
| Dashboard /wp-admin | 2,254 ▲77 | 5.62 ▼0.05 | 87.06 ▼9.86 | 42.83 ▼1.02 |
| Posts /wp-admin/edit.php | 2,157 ▲57 | 2.03 ▼0.02 | 36.97 ▲1.11 | 34.97 ▼0.08 |
| Add New Post /wp-admin/post-new.php | 1,546 ▲6 | 23.30 ▲4.94 | 627.71 ▼35.96 | 74.30 ▲17.73 |
| Media Library /wp-admin/upload.php | 1,459 ▲56 | 4.25 ▲0.06 | 99.25 ▼3.67 | 48.14 ▲0.09 |
| Freemius Debug [v.2.4.3] /wp-admin/admin.php?page=freemius | 1,099 | 1.68 | 30.65 | 32.81 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- Uninstall procedure validation failed for this plugin
- > Notice in wp-content/plugins/booking-weir/vendor/freemius/wordpress-sdk/includes/class-freemius.php+8575
Undefined property: stdClass::$plugins
- This plugin does not fully uninstall, leaving 10 options in the database
- widget_theysaidso_widget
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-comments
- fs_active_plugins
- fs_gdpr
- fs_debug_mode
- db_upgraded
- fs_accounts
- widget_recent-posts
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
Even though everything seems fine, this is not an exhaustive test
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/booking-weir/vendor/stripe/stripe-php/update_certs.php
- > /wp-content/plugins/booking-weir/vendor/stripe/stripe-php/build.php
- 482× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'setasign\\Fpdi\\PdfParser\\Filter\\FilterInterface' not found in wp-content/plugins/booking-weir/vendor/setasign/fpdi/src/PdfParser/Filter/Lzw.php:16
- > PHP Fatal error
Uncaught Error: Interface 'Sabberworm\\CSS\\Renderable' not found in wp-content/plugins/booking-weir/vendor/sabberworm/php-css-parser/lib/Sabberworm/CSS/Rule/Rule.php:15
- > PHP Fatal error
Uncaught Error: Interface 'Stripe\\StripeClientInterface' not found in wp-content/plugins/booking-weir/vendor/stripe/stripe-php/lib/BaseStripeClient.php:5
- > PHP Fatal error
Uncaught Error: Class 'Mpdf\\Tag\\InlineTag' not found in wp-content/plugins/booking-weir/vendor/mpdf/mpdf/src/Tag/Samp.php:5
- > PHP Fatal error
Uncaught Error: Class 'Stripe\\ApiResource' not found in wp-content/plugins/booking-weir/vendor/stripe/stripe-php/lib/BitcoinReceiver.php:34
- > PHP Fatal error
Uncaught Error: Class 'Mpdf\\Tag\\SetHtmlPageFooter' not found in wp-content/plugins/booking-weir/vendor/mpdf/mpdf/src/Tag/SetPageHeader.php:5
- > PHP Fatal error
Uncaught Error: Class 'Stripe\\Service\\AbstractService' not found in wp-content/plugins/booking-weir/vendor/stripe/stripe-php/lib/Service/DisputeService.php:7
- > PHP Fatal error
Uncaught Error: Class 'Sabberworm\\CSS\\Value\\CSSFunction' not found in wp-content/plugins/booking-weir/vendor/sabberworm/php-css-parser/lib/Sabberworm/CSS/Value/Color.php:7
- > PHP Fatal error
Uncaught Error: Class 'Mpdf\\Tag\\Tag' not found in wp-content/plugins/booking-weir/vendor/mpdf/mpdf/src/Tag/Option.php:7
- > PHP Fatal error
Uncaught Error: Class 'Stripe\\Service\\AbstractService' not found in wp-content/plugins/booking-weir/vendor/stripe/stripe-php/lib/Service/AccountService.php:7
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 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
7 plugin tags: scheduling, appointment, events, booking, reservation...
booking-weir/booking-weir.php Passed 13 tests
The main file in "Booking Weir" v. 1.0.11 serves as a complement to information provided in readme.txt and as the entry point to the plugin
57 characters long description:
Display a calendar that allows to select and book a time.
Code Analysis 0% 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
It is important to fix the following items
- You should never include executable (binary) or otherwise dangerous files in your plugin
- .crt - Security Certificate in Firefox, IE, Chrome, Safari
- ☣ wp-content/plugins/booking-weir/vendor/stripe/stripe-php/data/ca-certificates.crt
- .crt - Security Certificate in Firefox, IE, Chrome, Safari
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 857 | 56,227 | 96,265 | 127,744 |
| JavaScript | 203 | 1,765 | 705 | 15,321 |
| Markdown | 15 | 1,264 | 0 | 3,089 |
| SVG | 3 | 0 | 12 | 2,880 |
| PO File | 1 | 922 | 1,028 | 2,338 |
| JSON | 17 | 32 | 0 | 875 |
| CSS | 16 | 65 | 18 | 422 |
| LESS | 5 | 7 | 37 | 224 |
| XML | 7 | 13 | 0 | 127 |
| YAML | 4 | 1 | 0 | 46 |
| make | 1 | 9 | 0 | 27 |
| Sass | 1 | 0 | 0 | 7 |
| Ruby | 1 | 0 | 0 | 2 |
PHP code 0% from 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Please tend to the following items
- Class cyclomatic complexity has to be reduced to less than 1000 (currently 7,009)
- Cyclomatic complexity of methods should be reduced to less than 100 (currently 460)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.51 |
| Average class complexity | 35.07 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 7,009.00 |
| Average method complexity | 6.61 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 460.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 92 | |
| Interfaces | 29 | |
| Traits | 13 | |
| Classes | 650 | |
| ▷ Abstract classes | 29 | 4.46% |
| ▷ Concrete classes | 621 | 95.54% |
| ▷ Final classes | 34 | 5.48% |
| Methods | 4,225 | |
| ▷ Static methods | 506 | 11.98% |
| ▷ Public methods | 3,525 | 83.43% |
| ▷ Protected methods | 169 | 4.00% |
| ▷ Private methods | 531 | 12.57% |
| Functions | 199 | |
| ▷ Named functions | 121 | 60.80% |
| ▷ Anonymous functions | 78 | 39.20% |
| Constants | 1,345 | |
| ▷ Global constants | 108 | 8.03% |
| ▷ Class constants | 1,237 | 91.97% |
| ▷ Public constants | 1,237 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
4 PNG files occupy 0.05MB with 0.01MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/img/icon.png | 8.45KB | 8.94KB | 0.00% |
| vendor/freemius/wordpress-sdk/assets/img/plugin-icon.png | 9.16KB | 5.26KB | ▼ 42.58% |
| vendor/freemius/wordpress-sdk/assets/img/theme-icon.png | 10.97KB | 5.78KB | ▼ 47.37% |
| sui/flags.png | 27.46KB | 29.21KB | 0.00% |