Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.26MB] [CPU: ▼293.64ms] Passed 4 tests
An overview of server-side resources used by Gro CRM Contact to Leads
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.86 ▲0.35 | 57.50 ▲5.30 |
Dashboard /wp-admin | 3.70 ▲0.29 | 35.44 ▲0.92 |
Posts /wp-admin/edit.php | 3.92 ▲0.28 | 39.14 ▲1.09 |
Add New Post /wp-admin/post-new.php | 7.16 ▲0.19 | 93.08 ▼1,176.38 |
Media Library /wp-admin/upload.php | 3.58 ▲0.28 | 25.75 ▼0.19 |
Gro CRM /wp-admin/options-general.php?page=grocrm | 3.60 | 25.01 |
Server storage [IO: ▲0.20MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 29 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
This is an overview of browser requirements for Gro CRM Contact to Leads
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,802 ▲58 | 15.88 ▲0.00 | 8.06 ▲1.49 | 2.45 ▲0.31 |
Dashboard /wp-admin | 2,897 ▲42 | 6.13 ▼0.06 | 134.60 ▼18.83 | 159.37 ▼7.13 |
Posts /wp-admin/edit.php | 2,696 ▲2 | 2.99 ▼0.24 | 60.33 ▼4.09 | 144.25 ▲0.13 |
Add New Post /wp-admin/post-new.php | 1,671 ▼81 | 17.79 ▼3.91 | 391.07 ▼74.12 | 155.10 ▼8.65 |
Media Library /wp-admin/upload.php | 1,703 ▲5 | 5.50 ▼0.01 | 138.79 ▼10.45 | 172.72 ▼22.61 |
Gro CRM /wp-admin/options-general.php?page=grocrm | 1,063 | 2.37 | 54.59 | 114.87 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The plugin uninstalled successfully, without leaving any zombie files or tables
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 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Almost there! Just fix the following items
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/gro-crm/public/partials/grocrm-public-display.php:17
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/gro-crm/admin/partials/grocrm-admin-display.php:17
- > PHP Fatal error
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)
There were no browser issues found
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
These attributes need your attention:
- Tags: Too many tags (19 tag instead of maximum 10); only the first 5 tags are used in your directory listing
gro-crm/grocrm.php 77% from 13 tests
The main file in "Gro CRM Contact to Leads" v. 1.0.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
It is important to fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 149 characters long)
- Main file name: It is recommended to name the main PHP file as the plugin slug ("gro-crm.php" instead of "grocrm.php")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
Success! There were no dangerous files found in this plugin3,103 lines of code in 20 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 14 | 286 | 509 | 1,477 |
PO File | 1 | 677 | 689 | 1,372 |
CSS | 2 | 47 | 4 | 235 |
Markdown | 1 | 6 | 0 | 13 |
JavaScript | 2 | 2 | 0 | 6 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.25 |
Average class complexity | 6.88 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 21.00 |
Average method complexity | 2.02 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 11.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 8 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 8 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 46 | |
▷ Static methods | 2 | 4.35% |
▷ Public methods | 33 | 71.74% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 13 | 28.26% |
Functions | 5 | |
▷ Named functions | 5 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 1 | 100.00% |
▷ Public constants | 1 | 100.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
2 compressed PNG files occupy 0.01MB
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
admin/images/gro_crm_logo.png | 1.14KB | 1.21KB | 0.00% |
admin/images/gro_crm_background_wave.png | 6.67KB | 6.80KB | 0.00% |