Benchmarks
Plugin footprint 83% from 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: ▼4.04ms] Passed 4 tests
Analyzing server-side resources used by Flamix: Bitrix24 and WooCommerce Orders integration
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.99 ▲0.52 | 43.60 ▲8.03 |
Dashboard /wp-admin | 3.49 ▲0.14 | 45.35 ▼14.64 |
Posts /wp-admin/edit.php | 3.96 ▲0.60 | 56.73 ▲10.34 |
Add New Post /wp-admin/post-new.php | 6.07 ▲0.18 | 82.39 ▼13.68 |
Media Library /wp-admin/upload.php | 3.41 ▲0.18 | 36.67 ▲4.14 |
Bitrix24 ← WooCommerce /wp-admin/options-general.php?page=flamix-bitrix24-and-woo-integrations/settings/Settings.php | 3.43 | 32.91 |
Server storage [IO: ▲1.95MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 329 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
can_compress_scripts |
theysaidso_admin_options |
db_upgraded |
widget_recent-posts |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for Flamix: Bitrix24 and WooCommerce Orders integration
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,793 ▲32 | 14.51 ▲0.15 | 1.86 ▲0.21 | 38.25 ▼3.77 |
Dashboard /wp-admin | 2,199 ▲18 | 5.52 ▼0.15 | 86.18 ▼11.67 | 39.36 ▼3.00 |
Posts /wp-admin/edit.php | 2,101 ▲1 | 2.01 ▲0.03 | 36.68 ▼0.44 | 36.29 ▼1.34 |
Add New Post /wp-admin/post-new.php | 1,538 ▲12 | 23.13 ▲0.05 | 651.55 ▼24.90 | 55.81 ▲2.29 |
Media Library /wp-admin/upload.php | 1,404 ▲4 | 4.22 ▲0.03 | 93.88 ▼11.84 | 44.41 ▼1.85 |
Bitrix24 ← WooCommerce /wp-admin/options-general.php?page=flamix-bitrix24-and-woo-integrations/settings/Settings.php | 1,457 | 9.27 | 288.50 | 77.29 |
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
The following items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
- widget_recent-posts
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Smoke test failed, please fix the following
- > GET request to /wp-admin/options-general.php?page=flamix-bitrix24-and-woo-integrations/settings/Settings.php
- > Warning in wp-content/plugins/flamix-bitrix24-and-woo-integrations/includes/vendor/flamix/b24-lead/src/Bitrix24/Lead.php+52
session_start(): Cannot start session when headers already sent
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 fix the following items
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/flamix-bitrix24-and-woo-integrations/includes/vendor/mobiledetect/mobiledetectlib/export/exportToJSON.php
- 147× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Promise\\RejectionException' not found in wp-content/plugins/flamix-bitrix24-and-woo-integrations/includes/vendor/guzzlehttp/promises/src/AggregateException.php:10
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\Handler\\AbstractProcessingHandler' not found in wp-content/plugins/flamix-bitrix24-and-woo-integrations/includes/vendor/monolog/monolog/src/Monolog/Handler/TelegramBotHandler.php:34
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\Handler\\SocketHandler' not found in wp-content/plugins/flamix-bitrix24-and-woo-integrations/includes/vendor/monolog/monolog/src/Monolog/Handler/LogEntriesHandler.php:19
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\Handler\\AbstractSyslogHandler' not found in wp-content/plugins/flamix-bitrix24-and-woo-integrations/includes/vendor/monolog/monolog/src/Monolog/Handler/SyslogUdpHandler.php:25
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Cookie\\CookieJar' not found in wp-content/plugins/flamix-bitrix24-and-woo-integrations/includes/vendor/guzzlehttp/guzzle/src/Cookie/FileCookieJar.php:10
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\Formatter\\JsonFormatter' not found in wp-content/plugins/flamix-bitrix24-and-woo-integrations/includes/vendor/monolog/monolog/src/Monolog/Formatter/LogglyFormatter.php:19
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\Handler\\AbstractProcessingHandler' not found in wp-content/plugins/flamix-bitrix24-and-woo-integrations/includes/vendor/monolog/monolog/src/Monolog/Handler/IFTTTHandler.php:28
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Exception\\RequestException' not found in wp-content/plugins/flamix-bitrix24-and-woo-integrations/includes/vendor/guzzlehttp/guzzle/src/Exception/BadResponseException.php:11
- > PHP Fatal error
Uncaught Error: Interface 'Monolog\\Processor\\ProcessorInterface' not found in wp-content/plugins/flamix-bitrix24-and-woo-integrations/includes/vendor/monolog/monolog/src/Monolog/Processor/HostnameProcessor.php:17
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\Handler\\AbstractProcessingHandler' not found in wp-content/plugins/flamix-bitrix24-and-woo-integrations/includes/vendor/monolog/monolog/src/Monolog/Handler/CouchDBHandler.php:23
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Attributes that need to be fixed:
- Tags: Please delete some tags, you are using 12 tag instead of maximum 10
flamix-bitrix24-and-woo-integrations/flamix-bitrix24-and-woo-integrations.php Passed 13 tests
"Flamix: Bitrix24 and WooCommerce Orders integration" version 2.7.7's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
66 characters long description:
Automatic Lead or Deal creating in Bitrix24 from WooCommerce order
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected26,458 lines of code in 307 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 259 | 4,599 | 12,625 | 19,722 |
Markdown | 29 | 1,860 | 0 | 5,089 |
JSON | 17 | 0 | 0 | 1,612 |
XML | 1 | 0 | 0 | 20 |
YAML | 1 | 1 | 0 | 15 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.44 |
Average class complexity | 11.70 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 139.00 |
Average method complexity | 2.71 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 78.00 |
Code structure | ||
---|---|---|
Namespaces | 29 | |
Interfaces | 36 | |
Traits | 8 | |
Classes | 200 | |
▷ Abstract classes | 8 | 4.00% |
▷ Concrete classes | 192 | 96.00% |
▷ Final classes | 38 | 19.79% |
Methods | 1,553 | |
▷ Static methods | 269 | 17.32% |
▷ Public methods | 1,189 | 76.56% |
▷ Protected methods | 172 | 11.08% |
▷ Private methods | 192 | 12.36% |
Functions | 126 | |
▷ Named functions | 14 | 11.11% |
▷ Anonymous functions | 112 | 88.89% |
Constants | 140 | |
▷ Global constants | 1 | 0.71% |
▷ Class constants | 139 | 99.29% |
▷ Public constants | 101 | 72.66% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
1 PNG file occupies 0.05MB with 0.04MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
includes/vendor/flamix/conversions/img/form_example.png | 53.11KB | 16.68KB | ▼ 68.59% |