Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.08MB] [CPU: ▼6.85ms] Passed 4 tests
Server-side resources used by Custom validation error message - CF7
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.55 ▲0.08 | 41.10 ▼5.23 |
Dashboard /wp-admin | 3.38 ▲0.08 | 47.25 ▼7.48 |
Posts /wp-admin/edit.php | 3.43 ▲0.08 | 49.59 ▼3.79 |
Add New Post /wp-admin/post-new.php | 5.96 ▲0.08 | 83.53 ▼10.88 |
Media Library /wp-admin/upload.php | 3.30 ▲0.08 | 37.66 ▼2.14 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 3 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
widget_theysaidso_widget |
widget_recent-comments |
db_upgraded |
can_compress_scripts |
theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Custom validation error message - CF7
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲18 | 14.35 ▼0.23 | 1.88 ▲0.07 | 45.72 ▲2.35 |
Dashboard /wp-admin | 2,198 ▲27 | 5.63 ▲0.05 | 92.42 ▼9.14 | 38.22 ▼8.84 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 1.98 ▲0.00 | 39.02 ▲1.70 | 35.48 ▲1.96 |
Add New Post /wp-admin/post-new.php | 1,526 ▼17 | 23.14 ▲2.03 | 669.35 ▼29.41 | 60.82 ▲4.88 |
Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.31 ▲0.17 | 96.63 ▼20.56 | 44.90 ▼4.94 |
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
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Almost there! Just fix the following items
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/custom-validation-error-message-cf7/cf7-custom-validation-error-message.php:11
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
10 plugin tags: contact form field, validation message, contact form, custom validation, cf7 custom validation message...
custom-validation-error-message-cf7/cf7-custom-validation-error-message.php 92% from 13 tests
The primary PHP file in "Custom validation error message - CF7" version 1.0.0 is used by WordPress to initiate all plugin functionality
You should first fix the following items:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("custom-validation-error-message-cf7.php" instead of "cf7-custom-validation-error-message.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
There were no executable files found in this plugin188 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 57 | 33 | 188 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 1.07 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 6 | |
▷ Named functions | 5 | 83.33% |
▷ Anonymous functions | 1 | 16.67% |
Constants | 2 | |
▷ Global constants | 2 | 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
There were not PNG files found in your plugin