Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.06MB] [CPU: ▼4.64ms] Passed 4 tests
Server-side resources used by Planfy Online Booking
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.06 | 41.16 ▼3.40 |
Dashboard /wp-admin | 3.36 ▲0.06 | 48.82 ▼5.45 |
Posts /wp-admin/edit.php | 3.48 ▲0.12 | 53.51 ▲1.30 |
Add New Post /wp-admin/post-new.php | 5.96 ▲0.07 | 95.93 ▼9.72 |
Media Library /wp-admin/upload.php | 3.29 ▲0.05 | 38.24 ▼0.00 |
Server storage [IO: ▲0.90MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 39 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
db_upgraded |
widget_recent-comments |
widget_recent-posts |
theysaidso_admin_options |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
Planfy Online Booking: an overview of browser usage
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,913 ▲152 | 13.87 ▼0.28 | 8.91 ▲7.25 | 41.52 ▼4.99 |
Dashboard /wp-admin | 2,208 ▲28 | 5.55 ▼0.06 | 89.00 ▼3.21 | 39.12 ▼4.76 |
Posts /wp-admin/edit.php | 2,116 ▲16 | 1.98 ▼0.05 | 38.87 ▲0.82 | 36.17 ▲2.12 |
Add New Post /wp-admin/post-new.php | 1,540 ▲9 | 22.97 ▼0.21 | 670.44 ▲6.47 | 52.79 ▲3.26 |
Media Library /wp-admin/upload.php | 1,419 ▲25 | 4.15 ▼0.05 | 94.58 ▼11.24 | 43.31 ▼0.41 |
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
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_theysaidso_widget
- widget_recent-posts
- db_upgraded
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)
Everything seems fine, however this is by no means an exhaustive test
SRP 50% 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
The following issues need your attention
- 3× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/planfy-online-booking/admin/partials/installed.php:30
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/planfy-online-booking/public/partials/widget.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/planfy-online-booking/admin/partials/install.php:41
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
Please fix the following attributes:
- Contributors: Contributors not specified
planfy-online-booking/planfy.php 85% from 13 tests
This is the main PHP file of "Planfy Online Booking" version 0.1.5, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
Please take the time to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("planfy-online-booking.php" instead of "planfy.php")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
No dangerous file extensions were detected350 lines of code in 20 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 13 | 140 | 524 | 231 |
PO File | 3 | 15 | 15 | 84 |
JavaScript | 2 | 10 | 54 | 25 |
CSS | 2 | 3 | 8 | 10 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.06 |
Average class complexity | 1.43 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 3.00 |
Average method complexity | 1.10 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 3.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 7 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 7 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 29 | |
▷ Static methods | 2 | 6.90% |
▷ Public methods | 24 | 82.76% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 17.24% |
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 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
4 PNG files occupy 0.72MB with 0.35MB in potential savings
Potential savings
Compression of 4 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/banner-772x250.png | 161.57KB | 84.27KB | ▼ 47.84% |
assets/banner-1544x500.png | 549.64KB | 314.78KB | ▼ 42.73% |
assets/icon-256x256.png | 17.88KB | 7.88KB | ▼ 55.92% |
assets/icon-128x128.png | 7.69KB | 4.14KB | ▼ 46.17% |