Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
It is recommended to fix the following installer errors
- The plugin cannot be installed
- > Notice in wp-content/plugins/ezdeebee-wp-connector/ezdeebeeconnector.php+30
Undefined index: HTTPS
Server metrics [RAM: ▼1.84MB] [CPU: ▼49.64ms] Passed 4 tests
Analyzing server-side resources used by Ezdeebee Connector WordPress Plugin
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.15 ▼1.31 | 4.93 ▼32.46 |
| Dashboard /wp-admin | 2.17 ▼1.17 | 7.36 ▼49.84 |
| Posts /wp-admin/edit.php | 2.17 ▼1.18 | 6.68 ▼36.40 |
| Add New Post /wp-admin/post-new.php | 2.17 ▼3.71 | 4.88 ▼79.84 |
| Media Library /wp-admin/upload.php | 2.17 ▼1.06 | 5.62 ▼31.34 |
| Ezdeebee Settings /wp-admin/options-general.php?page=ezdeebee | 2.17 | 6.48 |
Server storage [IO: ▲30.73MB] [DB: ▲0.31MB] 67% from 3 tests
A short overview of filesystem and database impact
Just a few items left to fix
- Total filesystem usage must be limited to 25MB (currently using 30.73MB)
Filesystem: 1,947 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-comments |
| widget_recent-posts |
| db_upgraded |
| theysaidso_admin_options |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Ezdeebee Connector WordPress Plugin: an overview of browser usage
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,845 ▲99 | 14.24 ▼0.13 | 2.31 ▲0.68 | 43.56 ▲2.46 |
| Dashboard /wp-admin | 2,211 ▲39 | 5.56 ▼0.04 | 82.48 ▼13.69 | 38.48 ▼3.99 |
| Posts /wp-admin/edit.php | 2,120 ▲20 | 2.02 ▲0.06 | 33.74 ▼5.58 | 31.96 ▼1.38 |
| Add New Post /wp-admin/post-new.php | 1,544 ▲16 | 23.28 ▼0.08 | 674.10 ▲7.26 | 63.62 ▲12.86 |
| Media Library /wp-admin/upload.php | 1,422 ▲22 | 4.16 ▼0.10 | 96.82 ▼11.21 | 44.97 ▼2.88 |
| Ezdeebee Settings /wp-admin/options-general.php?page=ezdeebee | 801 | 2.03 | 23.79 | 28.53 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.31MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
Please fix the following items
- The plugin did not uninstall gracefully
- > Notice in wp-content/plugins/ezdeebee-wp-connector/ezdeebeeconnector.php+30
Undefined index: HTTPS
- Zombie WordPress options were found after uninstall: 6 options
- db_upgraded
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
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)
These server-side errors were triggered
- > GET request to /wp-admin/options-general.php?page=ezdeebee
- > Notice in wp-content/plugins/ezdeebee-wp-connector/ezdeebeeconnector.php+30
Undefined index: HTTPS
- > GET request to /wp-admin/options-general.php?page=ezdeebee
- > Notice in wp-content/plugins/ezdeebee-wp-connector/ezdeebeeconnector.php+38
Undefined index: ezdb_initconnector
- > GET request to /wp-admin/options-general.php?page=ezdeebee
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the YUI3.11.0 handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 4 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=ezdeebee
- > Notice in wp-content/plugins/ezdeebee-wp-connector/ezdeebeeconnector.php+230
Trying to access array offset on value of type bool
- > GET request to /wp-admin/options-general.php?page=ezdeebee
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the ezdeebee_seedfile handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/options-general.php?page=ezdeebee
- > User deprecated in wp-includes/functions.php+5463
Function screen_icon is deprecated since version 3.8.0 with no alternative available.
- > GET request to /wp-admin/options-general.php?page=ezdeebee
- > User deprecated in wp-includes/functions.php+5463
Function get_screen_icon is deprecated since version 3.8.0 with no alternative available.
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please take a closer look at the following
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Notice
Undefined index: HTTPS in wp-content/plugins/ezdeebee-wp-connector/ezdeebeeconnector.php on line 30
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/ezdeebee-wp-connector/ezdeebeeconnector.php:36
- > PHP Notice
User-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There are user-side issues you should fix
- > GET request to /wp-admin/options-general.php?page=ezdeebee
- > Network (severe)
wp-content/plugins/ezdeebee_wpconnector/yui/yui/yui-min.js?ver=6.3.1 - Failed to load resource: the server responded with a status of 404 (Not Found)
- > GET request to /wp-admin/options-general.php?page=ezdeebee
- > Network (severe)
https://ezdeebee.com/app/dbmanager//seedfile/856?ver=6.3.1 - Failed to load resource: net::ERR_NAME_NOT_RESOLVED
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
Attributes that require attention:
- Screenshots: Please a description for screenshot #2 in ezdeebee-wp-connector/assets to your readme.txt
ezdeebee-wp-connector/ezdeebeeconnector.php 92% from 13 tests
The main file in "Ezdeebee Connector WordPress Plugin" v. 1.1.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("ezdeebee-wp-connector.php" instead of "ezdeebeeconnector.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
There were no executable files found in this plugin176,805 lines of code in 1,460 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 1,292 | 43,852 | 131,741 | 168,172 |
| CSS | 166 | 1,784 | 2,241 | 8,402 |
| PHP | 1 | 48 | 31 | 214 |
| Markdown | 1 | 11 | 0 | 17 |
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.21 |
| 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 | 11 | |
| ▷ Named functions | 11 | 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 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
160 PNG files occupy 0.58MB with 0.43MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| yui/assets/skins/night/rail-y-lines.png | 0.26KB | 0.20KB | ▼ 22.14% |
| yui/assets/skins/sam/thumb-x.png | 3.78KB | 0.48KB | ▼ 87.27% |
| yui/slider-base/assets/skins/capsule/rail-y-lines.png | 3.56KB | 0.14KB | ▼ 96.02% |
| yui/slider-base/assets/skins/capsule-dark/rail-y.png | 3.59KB | 0.21KB | ▼ 94.20% |
| yui/slider-base/assets/skins/round-dark/thumb-x-grip.png | 4.26KB | 1.27KB | ▼ 70.10% |