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
Installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼3.68ms] Passed 4 tests
Server-side resources used by Responsive Contact Form Mailchimp Extension
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 38.04 ▼1.98 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 42.67 ▼5.70 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 47.81 ▲1.53 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 88.76 ▼8.51 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 34.51 ▲1.46 |
Server storage [IO: ▲0.26MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 16 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| widget_recent-comments |
| db_upgraded |
| can_compress_scripts |
| widget_theysaidso_widget |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Responsive Contact Form Mailchimp Extension
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,808 ▲62 | 13.27 ▼1.10 | 1.82 ▲0.02 | 40.82 ▼5.76 |
| Dashboard /wp-admin | 2,200 ▲12 | 5.82 ▲0.94 | 103.99 ▼13.09 | 37.03 ▼10.69 |
| Posts /wp-admin/edit.php | 2,086 ▼3 | 1.97 ▼0.02 | 40.89 ▲2.93 | 34.50 ▲0.02 |
| Add New Post /wp-admin/post-new.php | 1,514 ▼19 | 17.45 ▼5.64 | 653.43 ▼64.55 | 56.87 ▲7.07 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.22 ▲0.02 | 100.83 ▼8.30 | 41.95 ▼4.79 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html() in wp-content/plugins/responsive-contact-form-mailchimp-extension/admin/views/admin.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Please fix the following attributes:
- Screenshots: Please add an image for screenshot #1 (Set your MailChimp API key in the plugin settings.)
- Tags: Too many tags (17 tag instead of maximum 10); only the first 5 tags are used in your directory listing
responsive-contact-form-mailchimp-extension/ai-responsive-contact-form-mailchimp-extension.php 85% from 13 tests
The entry point to "Responsive Contact Form Mailchimp Extension" version 1.2 is a PHP file that has certain tags in its header comment area
It is important to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("responsive-contact-form-mailchimp-extension.php" instead of "ai-responsive-contact-form-mailchimp-extension.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 | There should be no dangerous file extensions present in any WordPress plugin
There were no executable files found in this plugin455 lines of code in 7 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 7 | 184 | 214 | 455 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.31 |
| Average class complexity | 16.67 |
| ▷ Minimum class complexity | 6.00 |
| ▷ Maximum class complexity | 33.00 |
| Average method complexity | 2.17 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 9.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 | 40 | |
| ▷ Static methods | 8 | 20.00% |
| ▷ Public methods | 26 | 65.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 14 | 35.00% |
| Functions | 2 | |
| ▷ Named functions | 2 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 2 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 2 | 100.00% |
| ▷ Public constants | 2 | 100.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
4 PNG files occupy 0.23MB with 0.18MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/icon-128x128.png | 42.86KB | 8.06KB | ▼ 81.20% |
| screenshot-1.png | 57.41KB | 20.85KB | ▼ 63.68% |
| assets/screenshot-1.png | 57.41KB | 20.85KB | ▼ 63.68% |
| (invalid) assets/banner-772x250.png | 82.12KB | 0.00KB | ▼ 100.00% |