Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▼0.00MB] [CPU: ▼14.61ms] Passed 4 tests
This is a short check of server-side resources used by Contact Enhance
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 38.83 ▲2.62 |
| Dashboard /wp-admin | 3.31 ▼0.03 | 40.89 ▼20.07 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 46.72 ▼0.18 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 74.42 ▼38.91 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 32.68 ▲0.74 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 4 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-comments |
| widget_theysaidso_widget |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-posts |
Browser metrics Passed 4 tests
A check of browser resources used by Contact Enhance
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,805 ▲59 | 14.19 ▼0.34 | 1.71 ▼0.15 | 44.96 ▲5.45 |
| Dashboard /wp-admin | 2,208 ▲31 | 5.62 ▼0.03 | 92.95 ▲8.11 | 41.72 ▼0.69 |
| Posts /wp-admin/edit.php | 2,119 ▲19 | 1.98 ▼0.04 | 37.53 ▼0.53 | 36.68 ▲3.22 |
| Add New Post /wp-admin/post-new.php | 1,539 ▲11 | 22.84 ▼0.27 | 647.95 ▲25.72 | 45.34 ▼2.21 |
| Media Library /wp-admin/upload.php | 1,416 ▲19 | 4.29 ▲0.03 | 93.89 ▼6.49 | 41.08 ▼2.77 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
Please fix the following items
- Zombie WordPress options were found after uninstall: 6 options
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however 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
Looking good! No server-side errors or output on direct access of PHP files
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 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that need to be fixed:
- Screenshots: Screenshot #1 (Settings of the plugin) image required
contact-enhance/daashub.php 85% from 13 tests
This is the main PHP file of "Contact Enhance" version 1.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("contact-enhance.php" instead of "daashub.php")
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 197 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Everything looks great! No dangerous files found in this plugin111 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 33 | 10 | 111 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.33 |
| Average class complexity | 12.00 |
| ▷ Minimum class complexity | 12.00 |
| ▷ Maximum class complexity | 12.00 |
| Average method complexity | 2.83 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 8.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 6 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 6 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
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.02MB with 0.01MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-1.png | 19.08KB | 9.67KB | ▼ 49.35% |