Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.00MB] [CPU: ▼2.93ms] Passed 4 tests
A check of server-side resources used by Wiwi Websolutions Bookingsystem
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 47.00 ▲1.19 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 52.08 ▲2.22 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 51.40 ▲3.71 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 86.51 ▼18.85 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 38.91 ▲5.36 |
Server storage [IO: ▲10.20MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 562 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-comments |
| can_compress_scripts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for Wiwi Websolutions Bookingsystem
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲29 | 13.24 ▼1.14 | 1.55 ▼0.26 | 42.44 ▼1.13 |
| Dashboard /wp-admin | 2,206 ▲18 | 5.91 ▲1.03 | 108.85 ▲4.47 | 41.42 ▼0.78 |
| Posts /wp-admin/edit.php | 2,092 ▲3 | 2.01 ▲0.02 | 39.50 ▼1.67 | 34.38 ▼3.39 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲5 | 23.24 ▲4.70 | 668.71 ▲48.33 | 58.01 ▲0.83 |
| Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.21 ▼0.04 | 93.45 ▼7.82 | 40.44 ▼2.93 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
Smoke tests 50% from 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 0% 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
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/wiwi-websolutions-bookingsystem/vendor/htmlburger/carbon-fields/templates/Exception/incorrect-syntax.php
- 115× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Container\\Condition\\Comparer\\Comparer' not found in wp-content/plugins/wiwi-websolutions-bookingsystem/vendor/htmlburger/carbon-fields/core/Container/Condition/Comparer/Any_Contain_Comparer.php:7
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Container\\Condition\\Condition' not found in wp-content/plugins/wiwi-websolutions-bookingsystem/vendor/htmlburger/carbon-fields/core/Container/Condition/Post_ID_Condition.php:8
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Field\\Field' not found in wp-content/plugins/wiwi-websolutions-bookingsystem/vendor/htmlburger/carbon-fields/core/Field/Hidden_Field.php:8
- > PHP Fatal error
Uncaught Error: Interface 'Carbon_Fields\\Pimple\\ServiceProviderInterface' not found in wp-content/plugins/wiwi-websolutions-bookingsystem/vendor/htmlburger/carbon-fields/core/Provider/Container_Condition_Provider.php:10
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Container\\Container' not found in wp-content/plugins/wiwi-websolutions-bookingsystem/vendor/htmlburger/carbon-fields/core/Container/Broken_Container.php:9
- > PHP Fatal error
Uncaught Error: Interface 'Carbon_Fields\\Datastore\\Datastore_Holder_Interface' not found in wp-content/plugins/wiwi-websolutions-bookingsystem/vendor/htmlburger/carbon-fields/core/Container/Container.php:18
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/wiwi-websolutions-bookingsystem/vendor/htmlburger/carbon-fields/templates/Container/user_meta.php:1
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Datastore\\Meta_Datastore' not found in wp-content/plugins/wiwi-websolutions-bookingsystem/vendor/htmlburger/carbon-fields/core/Datastore/Comment_Meta_Datastore.php:10
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Container\\Condition\\Condition' not found in wp-content/plugins/wiwi-websolutions-bookingsystem/vendor/htmlburger/carbon-fields/core/Container/Condition/Post_Level_Condition.php:10
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Field\\Field' not found in wp-content/plugins/wiwi-websolutions-bookingsystem/vendor/htmlburger/carbon-fields/core/Field/Color_Field.php:8
- > 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 97% from 29 tests
readme.txt 94% from 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
Attributes that require attention:
- Screenshots: A description for screenshot #1 is required in wiwi-websolutions-bookingsystem/assets to your readme.txt
wiwi-websolutions-bookingsystem/wiwi-websolutions-bookingsystem.php Passed 13 tests
The primary PHP file in "Wiwi Websolutions Bookingsystem" version 1.1.0 is used by WordPress to initiate all plugin functionality
60 characters long description:
Plugin that connects to the Wiwi Websolutions Bookingsystem.
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
No dangerous file extensions were detected48,873 lines of code in 506 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 259 | 5,948 | 9,438 | 31,565 |
| PHP | 150 | 2,591 | 6,666 | 9,710 |
| CSS | 12 | 468 | 1,246 | 2,946 |
| PO File | 27 | 880 | 1,097 | 2,341 |
| Sass | 50 | 351 | 5 | 1,807 |
| JSON | 4 | 0 | 0 | 360 |
| Markdown | 4 | 41 | 0 | 144 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.27 |
| Average class complexity | 8.32 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 50.00 |
| Average method complexity | 2.04 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 18.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 25 | |
| Interfaces | 5 | |
| Traits | 0 | |
| Classes | 121 | |
| ▷ Abstract classes | 11 | 9.09% |
| ▷ Concrete classes | 110 | 90.91% |
| ▷ Final classes | 1 | 0.91% |
| Methods | 898 | |
| ▷ Static methods | 90 | 10.02% |
| ▷ Public methods | 729 | 81.18% |
| ▷ Protected methods | 165 | 18.37% |
| ▷ Private methods | 4 | 0.45% |
| Functions | 119 | |
| ▷ Named functions | 36 | 30.25% |
| ▷ Anonymous functions | 83 | 69.75% |
| Constants | 32 | |
| ▷ Global constants | 9 | 28.12% |
| ▷ Class constants | 23 | 71.88% |
| ▷ Public constants | 23 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
There were not PNG files found in your plugin