Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.11MB] [CPU: ▼3.20ms] Passed 4 tests
This is a short check of server-side resources used by Contact Form 7 Benchmark Email Extension
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.58 ▲0.12 | 36.82 ▲0.23 |
| Dashboard /wp-admin | 3.41 ▲0.11 | 44.17 ▼3.73 |
| Posts /wp-admin/edit.php | 3.53 ▲0.17 | 44.89 ▼2.06 |
| Add New Post /wp-admin/post-new.php | 5.99 ▲0.11 | 87.63 ▼4.45 |
| Media Library /wp-admin/upload.php | 3.34 ▲0.11 | 32.63 ▼2.56 |
Server storage [IO: ▲7.05MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 247 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| can_compress_scripts |
| db_upgraded |
Browser metrics Passed 4 tests
Contact Form 7 Benchmark Email Extension: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 13.59 ▼0.78 | 1.67 ▲0.05 | 36.34 ▼1.34 |
| Dashboard /wp-admin | 2,203 ▲15 | 5.84 ▲0.95 | 97.90 ▼14.83 | 40.73 ▼0.97 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.02 ▲0.01 | 34.52 ▼5.60 | 34.24 ▼0.24 |
| Add New Post /wp-admin/post-new.php | 1,514 ▼28 | 17.66 ▼0.76 | 675.11 ▲74.85 | 63.28 ▲10.79 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.16 ▼0.03 | 96.11 ▼5.61 | 42.16 ▼1.46 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
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× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/benchmark-email-integration-for-cf7/vendor/lstrojny/fxmlrpc/benchmarks/assignments.php
- 156× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in wp-content/plugins/benchmark-email-integration-for-cf7/vendor/phly/http/test/ServerRequestTest.php:9
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\RequestInterface' not found in wp-content/plugins/benchmark-email-integration-for-cf7/vendor/psr/http-message/src/ServerRequestInterface.php:43
- > PHP Fatal error
Uncaught Error: Class 'Ivory\\HttpAdapter\\Asset\\AbstractUninstantiableAsset' not found in wp-content/plugins/benchmark-email-integration-for-cf7/vendor/egeloen/http-adapter/src/Parser/HeadersParser.php:22
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\MessageInterface' not found in wp-content/plugins/benchmark-email-integration-for-cf7/vendor/egeloen/http-adapter/src/Message/MessageInterface.php:21
- > PHP Fatal error
Uncaught Error: Class 'Symfony\\Component\\EventDispatcher\\Event' not found in wp-content/plugins/benchmark-email-integration-for-cf7/vendor/egeloen/http-adapter/src/Event/AbstractEvent.php:22
- > PHP Fatal error
Uncaught Error: Interface 'fXmlRpc\\Parser\\ParserInterface' not found in wp-content/plugins/benchmark-email-integration-for-cf7/vendor/lstrojny/fxmlrpc/src/fXmlRpc/Parser/NativeParser.php:32
- > PHP Fatal error
Uncaught Error: Class 'Ivory\\HttpAdapter\\Event\\Retry\\Strategy\\AbstractRetryStrategyChain' not found in wp-content/plugins/benchmark-email-integration-for-cf7/vendor/egeloen/http-adapter/src/Event/Retry/Strategy/ExponentialDelayedRetryStrategy.php:22
- > PHP Fatal error
Uncaught Error: Interface 'fXmlRpc\\Serializer\\SerializerInterface' not found in wp-content/plugins/benchmark-email-integration-for-cf7/vendor/lstrojny/fxmlrpc/src/fXmlRpc/Serializer/NativeSerializer.php:31
- > PHP Fatal error
Uncaught Error: Interface 'Ivory\\HttpAdapter\\PsrHttpAdapterInterface' not found in wp-content/plugins/benchmark-email-integration-for-cf7/vendor/egeloen/http-adapter/src/HttpAdapterInterface.php:19
- > PHP Fatal error
Uncaught Error: Class 'Ivory\\HttpAdapter\\AbstractCurlHttpAdapter' not found in wp-content/plugins/benchmark-email-integration-for-cf7/vendor/egeloen/http-adapter/src/CurlHttpAdapter.php:26
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Please fix the following attributes:
- Screenshots: Please add an image for screenshot #1 (cf7-benchmark-screenshot-1.png)
benchmark-email-integration-for-cf7/cf7-benchmark-ext.php 69% from 13 tests
"Contact Form 7 Benchmark Email Extension" version 1.0.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please take the time to fix the following:
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
- Domain Path: The domain path is invalid: folder "/lang/" does not exist
- Main file name: Name the main plugin file the same as the plugin slug ("benchmark-email-integration-for-cf7.php" instead of "cf7-benchmark-ext.php")
- Description: Please don't use more than 140 characters for the plugin description (currently 145 characters long)
Code Analysis 5% from 3 tests
File types 0% from 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Please make sure to remedy the following
- Do not distribute dangerous files with your plugin
- .jar - Java Archive in Firefox, IE, Chrome, Safari
- ☣ wp-content/plugins/benchmark-email-integration-for-cf7/vendor/lstrojny/fxmlrpc/tests/fXmlRpc/Integration/Fixtures/server.jar
- .jar - Java Archive in Firefox, IE, Chrome, Safari
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 205 | 2,932 | 9,388 | 12,843 |
| Markdown | 14 | 913 | 0 | 2,213 |
| JSON | 7 | 0 | 0 | 448 |
| JavaScript | 2 | 23 | 5 | 101 |
| YAML | 4 | 11 | 0 | 71 |
| CSS | 1 | 7 | 0 | 35 |
| XML | 3 | 0 | 0 | 25 |
| Ant | 1 | 3 | 0 | 24 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.21 |
| Average class complexity | 5.09 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 84.00 |
| Average method complexity | 1.69 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 83.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 33 | |
| Interfaces | 41 | |
| Traits | 4 | |
| Classes | 154 | |
| ▷ Abstract classes | 21 | 13.64% |
| ▷ Concrete classes | 133 | 86.36% |
| ▷ Final classes | 21 | 15.79% |
| Methods | 1,383 | |
| ▷ Static methods | 79 | 5.71% |
| ▷ Public methods | 1,215 | 87.85% |
| ▷ Protected methods | 105 | 7.59% |
| ▷ Private methods | 63 | 4.56% |
| Functions | 49 | |
| ▷ Named functions | 4 | 8.16% |
| ▷ Anonymous functions | 45 | 91.84% |
| Constants | 53 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 53 | 100.00% |
| ▷ Public constants | 53 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
There were not PNG files found in your plugin