Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼3.22ms] Passed 4 tests
An overview of server-side resources used by Map Field For Contact Form 7
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 38.67 ▼5.75 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 50.64 ▼1.63 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 49.86 ▼0.02 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 96.54 ▼2.65 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 37.19 ▼2.84 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] 67% from 3 tests
Analyzing filesystem and database footprints of this plugin
Please try to fix the following items
- Illegal file modification detected: 1 file (4.00KB) outside of "wp-content/plugins/map-field-for-contact-form-7/" and "wp-content/uploads/"
- (new file) wp-content/mgd_mirror/mgd_maximinodotpy-gitdown-test-repository
Filesystem: 7 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-comments |
| widget_recent-posts |
| db_upgraded |
| theysaidso_admin_options |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
A check of browser resources used by Map Field For Contact Form 7
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,815 ▲29 | 13.26 ▼1.32 | 1.93 ▲0.29 | 46.38 ▲3.13 |
| Dashboard /wp-admin | 2,224 ▲21 | 4.85 ▼1.03 | 101.74 ▼17.33 | 38.71 ▼8.32 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.03 ▼0.00 | 33.94 ▼4.59 | 34.82 ▼1.23 |
| Add New Post /wp-admin/post-new.php | 1,545 ▲12 | 23.26 ▲0.16 | 588.54 ▼98.75 | 53.31 ▲0.16 |
| Media Library /wp-admin/upload.php | 1,397 ▼3 | 4.25 ▼0.09 | 100.89 ▼7.31 | 41.44 ▼5.96 |
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
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP Passed 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
The SRP test was a success
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
These attributes need to be fixed:
- Screenshots: These screenshots lack descriptions #1, #2, #3 in map-field-for-contact-form-7/assets to your readme.txt
- Contributors: The plugin contributors field is missing
map-field-for-contact-form-7/google-map-field-for-contact-form-7.php 92% from 13 tests
Analyzing the main PHP file in "Map Field For Contact Form 7" version 1.0
It is important to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("map-field-for-contact-form-7.php" instead of "google-map-field-for-contact-form-7.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected497 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 81 | 29 | 472 |
| CSS | 1 | 0 | 0 | 25 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.34 |
| Average class complexity | 10.67 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 22.00 |
| Average method complexity | 3.07 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 13.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 | 14 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 14 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 1 | |
| ▷ Named functions | 1 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 3 | |
| ▷ Global constants | 3 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
No PNG files were detected