Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼6.20ms] Passed 4 tests
A check of server-side resources used by Sagenda - Scheduling Calendar
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 44.19 ▲1.95 |
| Dashboard /wp-admin | 3.32 ▼0.02 | 43.49 ▼12.30 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 44.02 ▼4.58 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 88.81 ▼7.92 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 33.76 ▲0.01 |
Server storage [IO: ▲13.42MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 638 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_recent-comments |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Checking browser requirements for Sagenda - Scheduling Calendar
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,810 ▲64 | 14.78 ▲0.42 | 1.94 ▲0.25 | 47.80 ▼0.30 |
| Dashboard /wp-admin | 2,210 ▲19 | 4.84 ▼0.24 | 101.12 ▼3.90 | 40.68 ▲0.72 |
| Posts /wp-admin/edit.php | 2,096 ▲10 | 1.99 ▼0.01 | 39.50 ▲4.15 | 34.59 ▲1.29 |
| Add New Post /wp-admin/post-new.php | 1,545 ▲9 | 18.64 ▼4.51 | 633.67 ▼9.46 | 52.27 ▼1.73 |
| Media Library /wp-admin/upload.php | 1,392 ▲7 | 4.21 ▼0.03 | 94.36 ▼8.58 | 43.83 ▼1.04 |
| Sagenda Calendar /wp-admin/options-general.php?page=Sagenda Calendar | 882 | 2.02 | 23.12 | 30.46 |
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
Please fix the following items
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
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
Everything seems fine, however this is by no means an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following
- 4× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/sagenda-calendar/initializer.php
- > /wp-content/plugins/sagenda-calendar/controllers/AdminTokenController.php
- > /wp-content/plugins/sagenda-calendar/plugin.php
- > /wp-content/plugins/sagenda-calendar/controllers/CalendarController.php
- 221× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Twig_Node_Expression_Binary' not found in wp-content/plugins/sagenda-calendar/assets/vendor/twig/lib/Twig/Node/Expression/Binary/Less.php:11
- > PHP Fatal error
Uncaught Error: Class 'Twig_BaseNodeVisitor' not found in wp-content/plugins/sagenda-calendar/assets/vendor/twig/lib/Twig/NodeVisitor/SafeAnalysis.php:12
- > PHP Fatal error
Uncaught Error: Class 'Twig_TokenParser' not found in wp-content/plugins/sagenda-calendar/assets/vendor/twig/lib/Twig/TokenParser/Sandbox.php:23
- > PHP Fatal error
Uncaught Error: Interface 'Twig_LoaderInterface' not found in wp-content/plugins/sagenda-calendar/assets/vendor/twig/lib/Twig/Loader/String.php:30
- > PHP Fatal error
Uncaught Error: Class 'Twig_Node_Expression_Binary' not found in wp-content/plugins/sagenda-calendar/assets/vendor/twig/lib/Twig/Node/Expression/Binary/Mul.php:12
- > PHP Fatal error
Uncaught Error: Class 'Twig_Node' not found in wp-content/plugins/sagenda-calendar/assets/vendor/twig/lib/Twig/Node/BlockReference.php:18
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/sagenda-calendar/assets/vendor/symfony/debug/Tests/FatalErrorHandler/UndefinedFunctionFatalErrorHandlerTest.php:18
- > PHP Fatal error
Uncaught Error: Class 'Twig_TokenParser' not found in wp-content/plugins/sagenda-calendar/assets/vendor/twig/lib/Twig/TokenParser/Set.php:29
- > PHP Fatal error
Uncaught Error: Class 'Twig_TokenParser' not found in wp-content/plugins/sagenda-calendar/assets/vendor/twig/lib/Twig/TokenParser/For.php:24
- > PHP Fatal error
Uncaught Error: Class 'Twig_Node_Expression_Binary' not found in wp-content/plugins/sagenda-calendar/assets/vendor/twig/lib/Twig/Node/Expression/Binary/BitwiseAnd.php:12
- > PHP Fatal error
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 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
9 plugin tags: reservation, booking form, scheduling, accommodation, booking...
sagenda-calendar/plugin.php 85% from 13 tests
The primary PHP file in "Sagenda - Scheduling Calendar" version 2.11.2 is used by WordPress to initiate all plugin functionality
The following require your attention:
- Main file name: Name the main plugin file the same as the plugin slug ("sagenda-calendar.php" instead of "plugin.php")
- Description: Keep the plugin description shorter than 140 characters (currently 186 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
No dangerous file extensions were detected81,113 lines of code in 537 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| XML | 5 | 13 | 6 | 42,643 |
| PHP | 318 | 36,982 | 59,748 | 16,476 |
| JSON | 53 | 0 | 0 | 11,724 |
| PO File | 41 | 2,275 | 1,643 | 5,030 |
| reStructuredText | 95 | 2,454 | 2,148 | 3,396 |
| C | 2 | 213 | 182 | 1,015 |
| Markdown | 6 | 202 | 0 | 497 |
| CSS | 4 | 10 | 19 | 85 |
| Twig | 3 | 3 | 0 | 85 |
| YAML | 2 | 14 | 0 | 57 |
| C/C++ Header | 2 | 19 | 21 | 55 |
| m4 | 2 | 13 | 12 | 46 |
| JavaScript | 4 | 1 | 7 | 4 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.39 |
| Average class complexity | 7.26 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 158.00 |
| Average method complexity | 2.55 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 53.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 24 | |
| Interfaces | 29 | |
| Traits | 2 | |
| Classes | 268 | |
| ▷ Abstract classes | 17 | 6.34% |
| ▷ Concrete classes | 251 | 93.66% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 1,260 | |
| ▷ Static methods | 78 | 6.19% |
| ▷ Public methods | 1,103 | 87.54% |
| ▷ Protected methods | 128 | 10.16% |
| ▷ Private methods | 29 | 2.30% |
| Functions | 103 | |
| ▷ Named functions | 71 | 68.93% |
| ▷ Anonymous functions | 32 | 31.07% |
| Constants | 94 | |
| ▷ Global constants | 3 | 3.19% |
| ▷ Class constants | 91 | 96.81% |
| ▷ Public constants | 91 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
There are no PNG files in this plugin