Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▼0.00MB] [CPU: ▼9.99ms] Passed 4 tests
Server-side resources used by eHive Search widget
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 40.36 ▼3.31 |
| Dashboard /wp-admin | 3.31 ▼0.03 | 50.57 ▼13.43 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 48.25 ▼1.92 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 95.02 ▼21.30 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 34.99 ▲1.87 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 4 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| theysaidso_admin_options |
| widget_recent-comments |
| widget_recent-posts |
| widget_ehivesearch_widget |
| can_compress_scripts |
| db_upgraded |
Browser metrics Passed 4 tests
Checking browser requirements for eHive Search widget
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲43 | 14.25 ▼0.02 | 1.84 ▲0.05 | 43.08 ▼1.60 |
| Dashboard /wp-admin | 2,195 ▲14 | 5.55 ▼0.16 | 87.20 ▼25.83 | 44.39 ▼3.46 |
| Posts /wp-admin/edit.php | 2,100 ▲3 | 1.97 ▲0.02 | 36.65 ▼1.45 | 37.07 ▲2.14 |
| Add New Post /wp-admin/post-new.php | 1,538 ▲3 | 18.11 ▼0.08 | 632.73 ▼47.62 | 64.19 ▲0.27 |
| Media Library /wp-admin/upload.php | 1,403 ▲3 | 4.17 ▼0.02 | 108.14 ▲12.36 | 47.34 ▲6.77 |
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
- This plugin did not uninstall successfully, leaving 7 options in the database
- widget_ehivesearch_widget
- db_upgraded
- can_compress_scripts
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Good news, no errors were detected
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
Please take a closer look at the following
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/ehive-search-widget/EHiveSearch_Widget.php:29
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Please fix the following attributes:
- Screenshots: Please add images for these screenshots: #1 (screenshot_1.png), #2 (screenshot_2.png)
ehive-search-widget/EHiveSearch_Widget.php 85% from 13 tests
Analyzing the main PHP file in "eHive Search widget" version 2.4.0
It is important to fix the following:
- Description: Please keep the plugin description shorter than 140 characters (currently 160 characters long)
- Main file name: Name the main plugin file the same as the plugin slug ("ehive-search-widget.php" instead of "EHiveSearch_Widget.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
No dangerous file extensions were detected99 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 26 | 23 | 79 |
| CSS | 1 | 6 | 14 | 20 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.08 |
| Average class complexity | 5.00 |
| ▷ Minimum class complexity | 5.00 |
| ▷ Maximum class complexity | 5.00 |
| Average method complexity | 2.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 4.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 4 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 4 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 1 | |
| ▷ Named functions | 1 | 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
PNG files should be compressed to save space and minimize bandwidth usage
1 compressed PNG file occupies 0.00MB
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| css/images/search.png | 0.43KB | 0.44KB | 0.00% |