Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Installer ran successfully
Server metrics [RAM: ▲0.14MB] [CPU: ▼5.60ms] Passed 4 tests
Analyzing server-side resources used by eHive Search
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.60 ▲0.14 | 41.10 ▼9.18 |
| Dashboard /wp-admin | 3.44 ▲0.14 | 44.99 ▼3.66 |
| Posts /wp-admin/edit.php | 3.55 ▲0.20 | 46.62 ▼0.80 |
| Add New Post /wp-admin/post-new.php | 6.02 ▲0.14 | 88.01 ▼8.76 |
| Media Library /wp-admin/upload.php | 3.36 ▲0.14 | 35.91 ▲0.87 |
Server storage [IO: ▲0.09MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 16 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for eHive Search
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,825 ▲79 | 13.39 ▼0.85 | 1.88 ▼0.16 | 41.73 ▼3.46 |
| Dashboard /wp-admin | 2,206 ▲24 | 4.86 ▼0.95 | 104.16 ▲0.20 | 39.27 ▼3.50 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.02 ▲0.01 | 35.54 ▼2.33 | 36.67 ▼0.43 |
| Add New Post /wp-admin/post-new.php | 1,535 ▼7 | 23.55 ▲5.35 | 624.35 ▲22.60 | 48.26 ▼4.13 |
| Media Library /wp-admin/upload.php | 1,391 ▲3 | 4.20 ▲0.03 | 95.22 ▼14.31 | 41.83 ▼2.89 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
These items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following items
- 4× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/ehive-search/EHiveSearch.php:28
- > PHP Notice
Undefined variable: css_class in wp-content/plugins/ehive-search/templates/eHiveSearch.php on line 19
- > PHP Fatal error
Uncaught Error: Call to a member function getSearchPageLink() on null in wp-content/plugins/ehive-search/templates/eHiveSearch.php:29
- > PHP Notice
Undefined variable: eHiveAccess in wp-content/plugins/ehive-search/templates/eHiveSearch.php on line 29
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
These attributes need to be fixed:
- Screenshots: Please add images for these screenshots: #1 (screenshot_1.png), #2 (screenshot_2.png)
ehive-search/EHiveSearch.php 85% from 13 tests
The primary PHP file in "eHive Search" version 2.4.4 is used by WordPress to initiate all plugin functionality
Please take the time to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("ehive-search.php" instead of "EHiveSearch.php")
- Description: Keep the plugin description shorter than 140 characters (currently 168 characters long)
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 detected1,070 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 228 | 80 | 976 |
| CSS | 1 | 20 | 21 | 94 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.39 |
| Average class complexity | 99.00 |
| ▷ Minimum class complexity | 99.00 |
| ▷ Maximum class complexity | 99.00 |
| Average method complexity | 3.04 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 37.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 | 48 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 47 | 97.92% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 1 | 2.08% |
| Functions | 6 | |
| ▷ Named functions | 6 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 3 | |
| ▷ Global constants | 1 | 33.33% |
| ▷ Class constants | 2 | 66.67% |
| ▷ Public constants | 2 | 100.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
11 PNG files occupy 0.02MB with 0.01MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/search_item_lightbox.png | 2.93KB | 2.04KB | ▼ 30.42% |
| images/no_image_ts.png | 4.70KB | 2.33KB | ▼ 50.43% |
| images/catalogue_photography.png | 0.93KB | 0.63KB | ▼ 32.60% |
| images/catalogue_library.png | 0.60KB | 0.34KB | ▼ 44.34% |
| images/catalogue_archives.png | 0.42KB | 0.25KB | ▼ 42.07% |