Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▲0.26MB] [CPU: ▲2.54ms] Passed 4 tests
A check of server-side resources used by WordPress to SugarCRM Lead
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.74 ▲0.27 | 43.17 ▲4.04 |
| Dashboard /wp-admin | 3.56 ▲0.25 | 50.61 ▲1.82 |
| Posts /wp-admin/edit.php | 3.67 ▲0.31 | 52.99 ▲4.84 |
| Add New Post /wp-admin/post-new.php | 6.14 ▲0.25 | 94.53 ▼0.55 |
| Media Library /wp-admin/upload.php | 3.48 ▲0.25 | 47.67 ▲10.00 |
| Your SugarCRM /wp-admin/admin.php?page=SugarSetting | 3.59 | 37.47 |
| Lead Module /wp-admin/admin.php?page=mapping_table | 3.57 | 33.96 |
Server storage [IO: ▲1.19MB] [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: 34 new files
Database: 1 new table, 13 new options
| New tables |
|---|
| oepl_crm_map_fields |
| New WordPress options |
|---|
| widget_theysaidso_widget |
| OEPL_SugarCRMSuccessMessage |
| theysaidso_admin_options |
| OEPL_SugarCRMReqFieldsMessage |
| widget_oepl_lead_widget |
| db_upgraded |
| OEPL_SugarCRMFailureMessage |
| OEPL_PLUGIN_VERSION |
| can_compress_scripts |
| widget_recent-comments |
| ... |
Browser metrics Passed 4 tests
An overview of browser requirements for WordPress to SugarCRM Lead
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,066 ▲320 | 13.96 ▼0.39 | 8.31 ▲6.77 | 40.60 ▲0.25 |
| Dashboard /wp-admin | 2,334 ▲153 | 4.96 ▼0.62 | 84.16 ▼22.71 | 84.95 ▲39.19 |
| Posts /wp-admin/edit.php | 2,255 ▲152 | 2.39 ▲0.44 | 39.31 ▲2.79 | 34.28 ▼1.19 |
| Add New Post /wp-admin/post-new.php | 1,829 ▲296 | 22.63 ▼0.84 | 588.53 ▼109.18 | 30.36 ▼29.86 |
| Media Library /wp-admin/upload.php | 1,549 ▲146 | 4.60 ▲0.37 | 105.68 ▼3.29 | 44.99 ▼3.10 |
| Your SugarCRM /wp-admin/admin.php?page=SugarSetting | 1,147 | 1.90 | 28.75 | 38.31 |
| Lead Module /wp-admin/admin.php?page=mapping_table | 1,256 | 1.97 | 28.13 | 29.82 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- The uninstall procedure has failed, leaving 9 options in the database
- widget_theysaidso_widget
- OEPL_Captcha_status
- theysaidso_admin_options
- widget_recent-comments
- OEPL_PLUGIN_VERSION
- db_upgraded
- widget_recent-posts
- can_compress_scripts
- widget_oepl_lead_widget
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 0% 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
The following issues need your attention
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/wp-widget-sugarcrm-lead-module/captcha.php
- 9× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html__() in wp-content/plugins/wp-widget-sugarcrm-lead-module/Common-functions.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html__() in wp-content/plugins/wp-widget-sugarcrm-lead-module/Fields_map_table.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html__() in wp-content/plugins/wp-widget-sugarcrm-lead-module/OEPL-Widget.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_url() in wp-content/plugins/wp-widget-sugarcrm-lead-module/oepl.conf.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html__() in wp-content/plugins/wp-widget-sugarcrm-lead-module/oepl.crm.cls.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html__() in wp-content/plugins/wp-widget-sugarcrm-lead-module/admin-functions.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_die() in wp-content/plugins/wp-widget-sugarcrm-lead-module/uninstall.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html__() in wp-content/plugins/wp-widget-sugarcrm-lead-module/oepl.conf.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html__() in wp-content/plugins/wp-widget-sugarcrm-lead-module/SugarSettings.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Attributes that need to be fixed:
- Tags: There are too many tags (14 tag instead of maximum 10)
- Donate link: Invalid URI found ("")
wp-widget-sugarcrm-lead-module/oepl.php 92% from 13 tests
This is the main PHP file of "WordPress to SugarCRM Lead" version 5.5, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("wp-widget-sugarcrm-lead-module.php" instead of "oepl.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
Everything looks great! No dangerous files found in this plugin5,150 lines of code in 19 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 3 | 242 | 42 | 2,268 |
| PHP | 10 | 211 | 119 | 1,794 |
| CSS | 3 | 138 | 1 | 997 |
| SVG | 2 | 0 | 1 | 83 |
| XML | 1 | 0 | 0 | 8 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.35 |
| Average class complexity | 45.00 |
| ▷ Minimum class complexity | 24.00 |
| ▷ Maximum class complexity | 71.00 |
| Average method complexity | 6.74 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 43.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 23 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 23 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 28 | |
| ▷ Named functions | 28 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 10 | |
| ▷ Global constants | 10 | 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
12 PNG files occupy 0.21MB with 0.09MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot/screenshot-4.png | 19.49KB | 9.86KB | ▼ 49.42% |
| image/NA_icon.png | 2.26KB | 1.36KB | ▼ 39.82% |
| screenshot/screenshot-1.PNG | 35.21KB | 16.06KB | ▼ 54.40% |
| screenshot/screenshot-2.png | 76.66KB | 38.75KB | ▼ 49.46% |
| image/minus-icon.png | 0.96KB | 0.80KB | ▼ 16.73% |