Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▼0.00MB] [CPU: ▼11.39ms] Passed 4 tests
A check of server-side resources used by Customize Event Google Calendar for WooCommerce Booking
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 39.82 ▼0.47 |
| Dashboard /wp-admin | 3.31 ▼0.03 | 46.27 ▼15.08 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 46.32 ▼5.94 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 83.79 ▼24.06 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 36.67 ▲0.28 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 2 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-posts |
| widget_recent-comments |
| db_upgraded |
Browser metrics Passed 4 tests
Customize Event Google Calendar for WooCommerce Booking: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 13.34 ▼1.03 | 4.35 ▲2.60 | 43.69 ▲4.99 |
| Dashboard /wp-admin | 2,209 ▲27 | 5.91 ▲0.06 | 95.88 ▼7.35 | 39.31 ▼2.12 |
| Posts /wp-admin/edit.php | 2,089 ▼3 | 2.12 ▲0.09 | 33.84 ▼7.80 | 33.83 ▼2.33 |
| Add New Post /wp-admin/post-new.php | 1,535 ▲16 | 23.27 ▲0.25 | 687.33 ▲30.33 | 56.26 ▼2.55 |
| Media Library /wp-admin/upload.php | 1,385 ▼3 | 4.15 ▼0.00 | 94.02 ▼15.04 | 42.80 ▼3.67 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
You still need to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- db_upgraded
- widget_theysaidso_widget
Smoke tests 75% 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)
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Almost there! Just fix the following items
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/customize-event-google-calendar-for-woocommerce-booking/buzz-393-gcalendar-sync.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
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
8 plugin tags: woo, woo commerce, event, woocommerce bookings, woocommerce...
customize-event-google-calendar-for-woocommerce-booking/buzz-393-gcalendar-sync.php 85% from 13 tests
"Customize Event Google Calendar for WooCommerce Booking" version 1.0.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- 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
- Main file name: It is recommended to name the main PHP file as the plugin slug ("customize-event-google-calendar-for-woocommerce-booking.php" instead of "buzz-393-gcalendar-sync.php")
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
No dangerous file extensions were detected22 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 29 | 13 | 22 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.18 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 0.00 |
| ▷ Minimum method complexity | 0.00 |
| ▷ Maximum method complexity | 0.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 0 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 0 | 0.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 0 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 0 | 0.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
There are no PNG files in this plugin