Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.02MB] [CPU: ▼11.08ms] Passed 4 tests
Server-side resources used by eHive Access
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 34.37 ▼8.87 |
| Dashboard /wp-admin | 3.33 ▲0.03 | 48.36 ▼14.45 |
| Posts /wp-admin/edit.php | 3.45 ▲0.09 | 52.89 ▲4.43 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 87.43 ▼22.29 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 38.32 ▲1.28 |
| Api Access /wp-admin/admin.php?page=EHive | 3.23 | 31.92 |
Server storage [IO: ▲0.17MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 53 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_theysaidso_widget |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-posts |
| ehive_access_options |
| can_compress_scripts |
Browser metrics Passed 4 tests
eHive Access: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,808 ▲47 | 14.39 ▲0.02 | 1.69 ▲0.07 | 40.17 ▲0.33 |
| Dashboard /wp-admin | 2,217 ▲40 | 5.59 ▲0.03 | 91.64 ▼10.52 | 72.14 ▲25.87 |
| Posts /wp-admin/edit.php | 2,119 ▲19 | 2.01 ▼0.01 | 41.25 ▼3.73 | 37.07 ▼2.80 |
| Add New Post /wp-admin/post-new.php | 1,550 ▲24 | 23.54 ▼0.01 | 718.39 ▲42.62 | 53.28 ▲0.29 |
| Media Library /wp-admin/upload.php | 1,422 ▲22 | 4.19 ▼0.02 | 103.87 ▼5.54 | 72.16 ▲22.89 |
| Api Access /wp-admin/admin.php?page=EHive | 1,014 | 1.66 | 24.88 | 35.15 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Smoke test failed, please fix the following
- > GET request to /wp-admin/admin.php?page=EHive
- > Notice in wp-content/plugins/ehive-access/EHiveAccess.php+244
Undefined index: account_details_page
- > GET request to /wp-admin/admin.php?page=EHive
- > Notice in wp-content/plugins/ehive-access/EHiveAccess.php+255
Undefined index: object_details_page
- > GET request to /wp-admin/admin.php?page=EHive
- > Notice in wp-content/plugins/ehive-access/EHiveAccess.php+266
Undefined index: search_page
SRP 0% 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 perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/ehive-access/ehive_api_client-php/domain/objectrecordtags/ObjectRecordTagsCollection.php
- 49× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Warning
require_once(EHIVE_API_ROOT_DIR/domain/objectrecords/ObjectRecord.php): failed to open stream: No such file or directory in wp-content/plugins/ehive-access/ehive_api_client-php/domain/objectrecords/ObjectRecordsCollection.php on line 16
- > PHP Warning
require_once(EHIVE_API_ROOT_DIR/domain/objectrecords/MediaSet.php): failed to open stream: No such file or directory in wp-content/plugins/ehive-access/ehive_api_client-php/domain/accounts/Account.php on line 17
- > PHP Fatal error
require_once(): Failed opening required 'EHIVE_API_ROOT_DIR/domain/objectrecords/MediaSet.php' (include_path='.:/usr/share/php') in wp-content/plugins/ehive-access/ehive_api_client-php/domain/accounts/Account.php on line 17
- > PHP Warning
require_once(EHIVE_API_ROOT_DIR/domain/objectrecords/Attribute.php): failed to open stream: No such file or directory in wp-content/plugins/ehive-access/ehive_api_client-php/domain/objectrecords/Media.php on line 16
- > PHP Fatal error
require_once(): Failed opening required 'EHIVE_API_ROOT_DIR/domain/objectrecords/FieldSet.php' (include_path='.:/usr/share/php') in wp-content/plugins/ehive-access/ehive_api_client-php/domain/objectrecords/ObjectRecord.php on line 16
- > PHP Warning
Use of undefined constant EHIVE_API_ROOT_DIR - assumed 'EHIVE_API_ROOT_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/ehive-access/ehive_api_client-php/domain/communities/CommunitiesCollection.php on line 16
- > PHP Warning
require_once(EHIVE_API_ROOT_DIR/domain/objectrecordfiles/FileV3.php): failed to open stream: No such file or directory in wp-content/plugins/ehive-access/ehive_api_client-php/domain/objectrecordfiles/ObjectRecordFilesCollectionV3.php on line 16
- > PHP Warning
require_once(EHIVE_API_ROOT_DIR/domain/objectrecords/Media.php): failed to open stream: No such file or directory in wp-content/plugins/ehive-access/ehive_api_client-php/domain/objectrecords/MediaRow.php on line 16
- > PHP Warning
require_once(EHIVE_API_ROOT_DIR/domain/objectrecords/Attribute.php): failed to open stream: No such file or directory in wp-content/plugins/ehive-access/ehive_api_client-php/domain/objectrecords/Field.php on line 16
- > PHP Warning
require_once(EHIVE_API_ROOT_DIR/domain/objectrecords/MediaRow.php): failed to open stream: No such file or directory in wp-content/plugins/ehive-access/ehive_api_client-php/domain/objectrecords/MediaSet.php on line 16
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
5 plugin tags: ehive, museum, archive, collection, history
ehive-access/EHiveAccess.php 92% from 13 tests
"eHive Access" version 2.4.2's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("ehive-access.php" instead of "EHiveAccess.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Everything looks great! No dangerous files found in this plugin2,497 lines of code in 48 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 46 | 825 | 564 | 2,367 |
| CSS | 1 | 23 | 14 | 93 |
| JavaScript | 1 | 8 | 0 | 37 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.27 |
| Average class complexity | 8.87 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 85.00 |
| Average method complexity | 2.90 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 33.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 45 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 45 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 185 | |
| ▷ Static methods | 4 | 2.16% |
| ▷ Public methods | 180 | 97.30% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 5 | 2.70% |
| Functions | 1 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 1 | 100.00% |
| Constants | 22 | |
| ▷ Global constants | 3 | 13.64% |
| ▷ Class constants | 19 | 86.36% |
| ▷ Public constants | 19 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
There are no PNG files in this plugin