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.10MB] [CPU: ▼146.01ms] Passed 4 tests
This is a short check of server-side resources used by Brozzme Hover integration
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.92 ▲0.09 | 39.22 ▲5.67 |
| Dashboard /wp-admin | 3.16 ▲0.10 | 43.74 ▼4.48 |
| Posts /wp-admin/edit.php | 3.24 ▲0.13 | 40.63 ▼3.16 |
| Add New Post /wp-admin/post-new.php | 5.53 ▲0.10 | 89.11 ▼569.40 |
| Media Library /wp-admin/upload.php | 3.10 ▲0.09 | 33.57 ▼7.00 |
| Brozzme Hover Settings /wp-admin/options-general.php?page=brozzme-hover | 3.07 | 27.59 |
Server storage [IO: ▲0.18MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 19 new files
Database: no new tables, 1 new option
| New WordPress options |
|---|
| brozzme_hover_settings |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Brozzme Hover integration
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,766 ▲170 | 16.33 ▲0.37 | 9.25 ▲1.14 | 45.60 ▼2.98 |
| Dashboard /wp-admin | 3,021 ▲90 | 6.60 ▲0.48 | 134.69 ▼2.51 | 113.03 ▲2.54 |
| Posts /wp-admin/edit.php | 2,790 ▲51 | 3.03 ▲0.34 | 71.16 ▲7.84 | 102.20 ▲15.58 |
| Add New Post /wp-admin/post-new.php | 1,913 ▲237 | 18.07 ▼0.79 | 362.34 ▼8.66 | 127.35 ▲15.93 |
| Media Library /wp-admin/upload.php | 1,858 ▲48 | 5.49 ▲0.46 | 130.65 ▼36.76 | 116.52 ▼9.09 |
| Brozzme Hover Settings /wp-admin/options-general.php?page=brozzme-hover | 1,537 | 2.61 | 76.75 | 84.36 |
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
These items require your attention
- The uninstall procedure has failed, leaving 1 option in the database
- brozzme_hover_settings
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP Passed 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
Looking good! No server-side errors or output on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Attributes that need to be fixed:
- Screenshots: Add an image for screenshot #3 (The screenshot description corresponds to screenshot-3.(png|jpg|jpeg|gif).)
brozzme-hover-integration/brozzme-hover.php 85% from 13 tests
The primary PHP file in "Brozzme Hover integration" version 1.2.1 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("brozzme-hover-integration.php" instead of "brozzme-hover.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
Good job! No executable or dangerous file extensions detected5,297 lines of code in 15 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| CSS | 5 | 376 | 151 | 4,482 |
| PHP | 5 | 133 | 148 | 433 |
| JSON | 2 | 0 | 0 | 260 |
| JavaScript | 3 | 27 | 15 | 122 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.20 |
| 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 | 31 | |
| ▷ Named functions | 31 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 1 | |
| ▷ Global constants | 1 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
No PNG files were detected