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
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.02MB] [CPU: ▼3.39ms] Passed 4 tests
Server-side resources used by Mango Contact Form
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.49 ▲0.03 | 37.46 ▼4.72 |
Dashboard /wp-admin | 3.32 ▲0.02 | 45.46 ▼3.65 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 48.74 ▼0.94 |
Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 95.59 ▼4.23 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 37.00 ▲0.01 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 30 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
can_compress_scripts |
widget_recent-posts |
widget_recent-comments |
widget_theysaidso_widget |
theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Mango Contact Form
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,919 ▲184 | 14.05 ▼0.23 | 6.09 ▲4.12 | 42.49 ▼4.94 |
Dashboard /wp-admin | 2,210 ▲22 | 4.85 ▼0.05 | 108.88 ▲2.99 | 41.71 ▲1.03 |
Posts /wp-admin/edit.php | 2,093 ▲1 | 1.99 ▼0.06 | 39.45 ▼0.41 | 34.56 ▼2.07 |
Add New Post /wp-admin/post-new.php | 1,532 ▲15 | 23.50 ▲5.96 | 658.06 ▲55.03 | 55.31 ▼0.55 |
Media Library /wp-admin/upload.php | 1,395 ▲4 | 4.18 ▼0.05 | 98.28 ▲1.25 | 43.04 ▼0.77 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
Smoke tests 50% from 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 0% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Almost there! Just fix the following items
- 1× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/mango-contact-form/admin/partials/mango-contact-form-admin-display.php
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/mango-contact-form/public/partials/mango-contact-form-public-display.php:18
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
3 plugin tags: contact form, ajax contact form, contact to admin email
mango-contact-form/mango-contact-form.php Passed 13 tests
The primary PHP file in "Mango Contact Form" version 1.0.0 is used by WordPress to initiate all plugin functionality
28 characters long description:
Simple a usefull contat form
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
Success! There were no dangerous files found in this plugin596 lines of code in 21 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 14 | 171 | 579 | 317 |
PO File | 3 | 69 | 78 | 177 |
JavaScript | 2 | 7 | 27 | 75 |
CSS | 2 | 6 | 8 | 27 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.09 |
Average class complexity | 2.22 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 8.00 |
Average method complexity | 1.35 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 8.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 9 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 9 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 31 | |
▷ Static methods | 2 | 6.45% |
▷ Public methods | 26 | 83.87% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 16.13% |
Functions | 3 | |
▷ Named functions | 3 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
No PNG files were detected