Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.13MB] [CPU: ▼9.81ms] Passed 4 tests
This is a short check of server-side resources used by FareHarbor for WordPress
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.59 ▲0.13 | 36.77 ▼8.39 |
| Dashboard /wp-admin | 3.44 ▲0.14 | 45.99 ▼1.92 |
| Posts /wp-admin/edit.php | 3.56 ▲0.20 | 44.74 ▼7.25 |
| Add New Post /wp-admin/post-new.php | 6.02 ▲0.13 | 82.69 ▼21.66 |
| Media Library /wp-admin/upload.php | 3.37 ▲0.13 | 34.93 ▲2.87 |
| FareHarbor /wp-admin/options-general.php?page=fareharbor/fareharbor.php | 3.33 | 31.43 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 3 new files
Database: no new tables, 9 new options
| New WordPress options |
|---|
| fareharbor_settings |
| widget_recent-comments |
| theysaidso_admin_options |
| fareharbor_kit_version |
| widget_recent-posts |
| widget_theysaidso_widget |
| fareharbor_version |
| db_upgraded |
| can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for FareHarbor for WordPress
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 4,563 ▲1,806 | 21.14 ▲6.76 | 204.94 ▲203.00 | 54.46 ▲12.82 |
| Dashboard /wp-admin | 2,210 ▲25 | 5.81 ▼0.04 | 98.22 ▼10.12 | 39.48 ▼0.86 |
| Posts /wp-admin/edit.php | 2,093 ▲4 | 2.01 ▲0.01 | 34.08 ▼7.34 | 34.93 ▼3.28 |
| Add New Post /wp-admin/post-new.php | 1,551 ▲9 | 18.13 ▼0.35 | 608.51 ▼15.77 | 69.22 ▲12.97 |
| Media Library /wp-admin/upload.php | 1,395 ▲16 | 4.20 ▼0.11 | 96.03 ▼5.94 | 42.29 ▼2.65 |
| FareHarbor /wp-admin/options-general.php?page=fareharbor/fareharbor.php | 999 | 2.06 | 22.38 | 32.27 |
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
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% 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
Please fix the following items
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/fareharbor/fareharbor.php
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Attributes that require attention:
- Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line (
=== fareharbor ===)
fareharbor/fareharbor.php Passed 13 tests
The main PHP script in "FareHarbor for WordPress" version 3.6.7 is automatically included on every request by WordPress
68 characters long description:
Easily add FareHarbor reservation calendars and buttons to your site
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected716 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 363 | 122 | 716 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.45 |
| Average class complexity | 116.00 |
| ▷ Minimum class complexity | 116.00 |
| ▷ Maximum class complexity | 116.00 |
| Average method complexity | 3.88 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 17.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 1 | 100.00% |
| Methods | 40 | |
| ▷ Static methods | 39 | 97.50% |
| ▷ Public methods | 25 | 62.50% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 15 | 37.50% |
| 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
PNG images were not found in this plugin