Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.20MB] [CPU: ▼136.62ms] Passed 4 tests
Server-side resources used by FazaCrm Client
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.92 ▲0.20 | 36.46 ▲14.77 |
Dashboard /wp-admin | 3.30 ▲0.25 | 53.14 ▲10.78 |
Posts /wp-admin/edit.php | 3.35 ▲0.25 | 41.34 ▼4.66 |
Add New Post /wp-admin/post-new.php | 5.61 ▲0.17 | 95.11 ▼545.98 |
Media Library /wp-admin/upload.php | 3.18 ▲0.18 | 32.43 ▼6.61 |
Settings /wp-admin/admin.php?page=fazacrmclient | 3.19 | 32.15 |
Configuration test /wp-admin/admin.php?page=fazacrmclient_test_configuration | 3.19 | 30.40 |
Server storage [IO: ▲2.08MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 434 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
FazaCrm Client: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,739 ▲143 | 16.20 ▲0.57 | 10.02 ▼2.12 | 46.47 ▼6.28 |
Dashboard /wp-admin | 3,002 ▲71 | 5.91 ▼0.04 | 132.00 ▼10.91 | 137.85 ▲24.50 |
Posts /wp-admin/edit.php | 2,774 ▲38 | 2.59 ▼0.12 | 62.63 ▲0.78 | 97.32 ▲2.16 |
Add New Post /wp-admin/post-new.php | 1,709 ▲37 | 18.56 ▼0.38 | 378.30 ▲0.78 | 131.98 ▲23.81 |
Media Library /wp-admin/upload.php | 1,785 ▼22 | 5.02 ▼0.00 | 124.00 ▼35.90 | 139.72 ▲16.48 |
Settings /wp-admin/admin.php?page=fazacrmclient | 1,584 | 2.09 | 52.39 | 118.32 |
Configuration test /wp-admin/admin.php?page=fazacrmclient_test_configuration | 1,186 | 2.10 | 54.96 | 77.24 |
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
Uninstaller ran successfully
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
Even though everything seems fine, this is not an exhaustive test
SRP 50% 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 fix the following
- 232× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'Zend\\Validator\\Barcode\\AdapterInterface' not found in wp-content/plugins/fazacrm-client/vendor/zendframework/zend-validator/src/Barcode/AbstractAdapter.php:12
- > PHP Fatal error
Uncaught Error: Class 'Zend\\Validator\\AbstractValidator' not found in wp-content/plugins/fazacrm-client/vendor/zendframework/zend-validator/src/Hostname.php:24
- > PHP Fatal error
Uncaught Error: Interface 'Zend\\Http\\Exception\\ExceptionInterface' not found in wp-content/plugins/fazacrm-client/vendor/zendframework/zend-http/src/Exception/InvalidArgumentException.php:10
- > PHP Fatal error
Uncaught Error: Class 'Zend\\Validator\\Barcode\\AbstractAdapter' not found in wp-content/plugins/fazacrm-client/vendor/zendframework/zend-validator/src/Barcode/Leitcode.php:12
- > PHP Fatal error
Uncaught Error: Class 'Zend\\Http\\Header\\AbstractDate' not found in wp-content/plugins/fazacrm-client/vendor/zendframework/zend-http/src/Header/RetryAfter.php:15
- > PHP Fatal error
Uncaught Error: Interface 'Zend\\Validator\\Exception\\ExceptionInterface' not found in wp-content/plugins/fazacrm-client/vendor/zendframework/zend-validator/src/Exception/RuntimeException.php:12
- > PHP Fatal error
Uncaught Error: Class 'Zend\\Validator\\AbstractValidator' not found in wp-content/plugins/fazacrm-client/vendor/zendframework/zend-validator/src/GpsPoint.php:12
- > PHP Fatal error
Uncaught Error: Interface 'Zend\\Uri\\Exception\\ExceptionInterface' not found in wp-content/plugins/fazacrm-client/vendor/zendframework/zend-uri/src/Exception/InvalidArgumentException.php:10
- > PHP Fatal error
Uncaught Error: Class 'Zend\\Http\\Client\\Exception\\InvalidArgumentException' not found in wp-content/plugins/fazacrm-client/vendor/zendframework/zend-http/src/Client/Adapter/Exception/InvalidArgumentException.php:12
- > PHP Fatal error
Uncaught Error: Class 'Zend\\Validator\\AbstractValidator' not found in wp-content/plugins/fazacrm-client/vendor/zendframework/zend-validator/src/LessThan.php:15
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Attributes that need to be fixed:
- Donate link: Invalid url: ""
- Screenshots: Screenshot #3 (Documentation associée pour vous permettre d'intégrer le plugin aisément.) image required
fazacrm-client/Plugin.php 85% from 13 tests
The primary PHP file in "FazaCrm Client" version 1.0.4 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("fazacrm-client.php" instead of "Plugin.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 | A short check of programming languages and file extensions; no executable files are allowed
Good job! No executable or dangerous file extensions detected34,737 lines of code in 414 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 320 | 4,676 | 14,200 | 28,447 |
Markdown | 76 | 1,994 | 0 | 5,131 |
JSON | 10 | 0 | 0 | 819 |
CSS | 2 | 10 | 13 | 110 |
PO File | 1 | 38 | 0 | 89 |
JavaScript | 2 | 13 | 10 | 63 |
YAML | 1 | 0 | 0 | 63 |
HTML | 1 | 3 | 0 | 9 |
XML | 1 | 1 | 1 | 6 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.42 |
Average class complexity | 10.64 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 151.00 |
Average method complexity | 2.98 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 56.00 |
Code structure | ||
---|---|---|
Namespaces | 36 | |
Interfaces | 40 | |
Traits | 4 | |
Classes | 263 | |
▷ Abstract classes | 16 | 6.08% |
▷ Concrete classes | 247 | 93.92% |
▷ Final classes | 5 | 2.02% |
Methods | 1,581 | |
▷ Static methods | 169 | 10.69% |
▷ Public methods | 1,401 | 88.61% |
▷ Protected methods | 149 | 9.42% |
▷ Private methods | 31 | 1.96% |
Functions | 25 | |
▷ Named functions | 6 | 24.00% |
▷ Anonymous functions | 19 | 76.00% |
Constants | 377 | |
▷ Global constants | 4 | 1.06% |
▷ Class constants | 373 | 98.94% |
▷ Public constants | 373 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
4 PNG files occupy 0.06MB with 0.03MB in potential savings
Potential savings
Compression of 4 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
vendor/container-interop/container-interop/docs/images/interoperating_containers.png | 25.13KB | 12.83KB | ▼ 48.97% |
vendor/container-interop/container-interop/docs/images/side_by_side_containers.png | 15.88KB | 8.43KB | ▼ 46.90% |
vendor/container-interop/container-interop/docs/images/priority.png | 15.87KB | 8.86KB | ▼ 44.20% |
assets/images/icon.png | 1.28KB | 0.55KB | ▼ 57.02% |