Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.18MB] [CPU: ▼11.24ms] Passed 4 tests
A check of server-side resources used by VR Calendar
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.62 ▲0.16 | 39.53 ▲0.80 |
| Dashboard /wp-admin | 3.53 ▲0.19 | 41.78 ▼12.92 |
| Posts /wp-admin/edit.php | 3.57 ▲0.21 | 44.71 ▼2.39 |
| Add New Post /wp-admin/post-new.php | 6.18 ▲0.29 | 72.64 ▼29.16 |
| Media Library /wp-admin/upload.php | 3.41 ▲0.18 | 32.02 ▼0.50 |
| Add Calendar /wp-admin/admin.php?page=vr-calendar-add-calendar | 3.39 | 30.00 |
| Information /wp-admin/admin.php?page=vr-calendar-information | 3.35 | 30.33 |
| Dashboard /wp-admin/admin.php?page=vr-calendar-dashboard | 3.39 | 31.21 |
| Settings /wp-admin/admin.php?page=vr-calendar-settings | 3.37 | 26.04 |
Server storage [IO: ▲1.67MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 94 new files
Database: 2 new tables, 6 new options
| New tables |
|---|
| wp_vrcalandar_bookings |
| wp_vrcalandar |
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-posts |
| can_compress_scripts |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for VR Calendar
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,003 ▲257 | 14.21 ▼0.39 | 10.00 ▲8.28 | 40.66 ▼0.76 |
| Dashboard /wp-admin | 2,270 ▲79 | 5.12 ▼0.93 | 111.19 ▲11.95 | 38.03 ▼1.62 |
| Posts /wp-admin/edit.php | 2,161 ▲72 | 2.39 ▲0.38 | 37.81 ▲0.39 | 34.58 ▲2.14 |
| Add New Post /wp-admin/post-new.php | 1,567 ▲48 | 17.85 ▼5.22 | 676.43 ▲14.53 | 37.17 ▼14.87 |
| Media Library /wp-admin/upload.php | 1,455 ▲67 | 4.52 ▲0.34 | 96.60 ▼3.84 | 43.21 ▲0.85 |
| Add Calendar /wp-admin/admin.php?page=vr-calendar-add-calendar | 2,272 | 3.12 | 75.02 | 24.81 |
| Information /wp-admin/admin.php?page=vr-calendar-information | 850 | 2.13 | 26.57 | 22.38 |
| Dashboard /wp-admin/admin.php?page=vr-calendar-dashboard | 1,012 | 2.11 | 27.17 | 31.54 |
| Settings /wp-admin/admin.php?page=vr-calendar-settings | 973 | 2.12 | 25.61 | 22.69 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- Zombie tables detected upon uninstall: 2 tables
- wp_vrcalandar
- wp_vrcalandar_bookings
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- 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 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please take a closer look at the following
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/vr-calendar-sync/Public/Views/Shortcodes/Payment.view.php
- 44× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/vr-calendar-sync/Admin/Views/Part/Settings/General.php:32
- > PHP Fatal error
Uncaught Error: Class 'VRCSingleton' not found in wp-content/plugins/vr-calendar-sync/Admin/Classes/VRCalendarAdmin.class.php:27
- > PHP Notice
Undefined variable: data in wp-content/plugins/vr-calendar-sync/Public/Views/Shortcodes/Booking.view.php on line 13
- > PHP Fatal error
Uncaught Error: Class 'VRCalendarEntity' not found in wp-content/plugins/vr-calendar-sync/Admin/Views/AddCalendar.php:27
- > PHP Notice
Trying to get property 'calendar_layout_options' of non-object in wp-content/plugins/vr-calendar-sync/Public/Views/Shortcodes/Booking.view.php on line 13
- > PHP Fatal error
Uncaught Error: Class 'VRCSingleton' not found in wp-content/plugins/vr-calendar-sync/Includes/Classes/Email/VRCEmail.class.php:27
- > PHP Notice
Trying to access array offset on value of type null in wp-content/plugins/vr-calendar-sync/Public/Views/Shortcodes/Booking.view.php on line 19
- > PHP Notice
Trying to get property 'calendar_payment_method' of non-object in wp-content/plugins/vr-calendar-sync/Public/Views/Shortcodes/Payment.view.php on line 14
- > PHP Fatal error
Uncaught Error: Class 'VRCalendarSettings' not found in wp-content/plugins/vr-calendar-sync/Admin/Views/Settings.php:27
- > PHP Fatal error
require_once(): Failed opening required '../vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/vr-calendar-sync/Includes/Vendor/ics-parser/examples/index.php on line 4
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Attributes that require attention:
- Screenshots: Please add images for these screenshots: #1 (screenshot-1.png), #2 (screenshot-2.png), #3 (screenshot-4.png)
- Tags: Too many tags (15 tag instead of maximum 10); only the first 5 tags are used in your directory listing
vr-calendar-sync/vrcalendar.php 77% from 13 tests
Analyzing the main PHP file in "VR Calendar" version 2.4.0
Please take the time to fix the following:
- Domain Path: The domain path follows the same naming rules as the domain name, using only dashes and lowercase characters ("/Languages")
- Main file name: It is recommended to name the main PHP file as the plugin slug ("vr-calendar-sync.php" instead of "vrcalendar.php")
- 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 Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Success! There were no dangerous files found in this plugin10,137 lines of code in 63 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 37 | 1,011 | 2,434 | 6,670 |
| JavaScript | 5 | 212 | 39 | 1,468 |
| CSS | 8 | 80 | 117 | 889 |
| SVG | 1 | 0 | 0 | 288 |
| HTML | 1 | 45 | 13 | 250 |
| Markdown | 4 | 56 | 0 | 239 |
| PO File | 1 | 65 | 67 | 159 |
| YAML | 4 | 15 | 0 | 118 |
| JSON | 1 | 0 | 0 | 49 |
| XML | 1 | 0 | 0 | 7 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.30 |
| Average class complexity | 30.33 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 312.00 |
| Average method complexity | 2.87 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 44.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 18 | |
| ▷ Abstract classes | 1 | 5.56% |
| ▷ Concrete classes | 17 | 94.44% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 241 | |
| ▷ Static methods | 5 | 2.07% |
| ▷ Public methods | 202 | 83.82% |
| ▷ Protected methods | 38 | 15.77% |
| ▷ Private methods | 1 | 0.41% |
| Functions | 11 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 11 | 100.00% |
| Constants | 18 | |
| ▷ Global constants | 6 | 33.33% |
| ▷ Class constants | 12 | 66.67% |
| ▷ Public constants | 12 | 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
9 PNG files occupy 0.42MB with 0.15MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/icon-close.png | 0.91KB | 0.69KB | ▼ 23.60% |
| screenshot-4.png | 61.14KB | 16.14KB | ▼ 73.59% |
| assets/images/arrow_left.png | 0.70KB | 0.65KB | ▼ 7.91% |
| screenshot-1.png | 144.43KB | 48.02KB | ▼ 66.75% |
| assets/images/arrow_right.png | 0.71KB | 0.64KB | ▼ 8.71% |