Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Install script ran successfully
Server metrics [RAM: ▼1.23MB] [CPU: ▼43.17ms] Passed 4 tests
This is a short check of server-side resources used by Contact Blaster
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.74 ▼0.72 | 13.88 ▼32.76 |
| Dashboard /wp-admin | 2.78 ▼0.52 | 15.37 ▼31.72 |
| Posts /wp-admin/edit.php | 2.78 ▼0.57 | 15.71 ▼30.44 |
| Add New Post /wp-admin/post-new.php | 2.78 ▼3.11 | 17.57 ▼77.77 |
| Media Library /wp-admin/upload.php | 2.78 ▼0.45 | 14.98 ▼15.42 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 21 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_recent-comments |
| can_compress_scripts |
Browser metrics Passed 4 tests
Checking browser requirements for Contact Blaster
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,830 ▲95 | 13.71 ▼0.69 | 6.02 ▲4.03 | 36.58 ▼21.22 |
| Dashboard /wp-admin | 2,209 ▲18 | 5.85 ▲0.95 | 101.65 ▼5.11 | 42.18 ▼9.38 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 1.97 ▼0.17 | 33.70 ▼5.71 | 37.78 ▲4.84 |
| Add New Post /wp-admin/post-new.php | 1,530 ▲16 | 23.12 ▲5.50 | 639.29 ▼11.46 | 51.73 ▼2.19 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.17 ▼0.02 | 95.75 ▼7.88 | 40.25 ▼2.30 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- This plugin did not uninstall without warnings or errors
- > Warning in wp-content/plugins/contact-blaster/contact-blaster.php+79
Use of undefined constant WPLANG - assumed 'WPLANG' (this will throw an Error in a future version of PHP)
- The uninstall procedure has failed, leaving 6 options in the database
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please fix the following items
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_url() in wp-content/plugins/contact-blaster/contact-blaster.php:37
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
Attributes that need to be fixed:
- Plugin Name: Please specify the plugin name on the first line (
=== contact-blaster ===) - Tags: Please reduce the number of tags, currently 12 tag instead of maximum 10
contact-blaster/contact-blaster.php 85% from 13 tests
The principal PHP file in "Contact Blaster" v. 2.0.1 is loaded by WordPress automatically on each request
Please make the necessary changes and fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 206 characters long)
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
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
Good job! No executable or dangerous file extensions detected86 lines of code in 11 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 54 | 74 | 53 |
| Sass | 3 | 7 | 4 | 18 |
| JavaScript | 2 | 13 | 9 | 15 |
| CSS | 3 | 0 | 4 | 0 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.26 |
| Average class complexity | 3.50 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 4.00 |
| Average method complexity | 1.71 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 3.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 7 | |
| ▷ Static methods | 3 | 42.86% |
| ▷ Public methods | 7 | 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 | 3 | |
| ▷ Global constants | 2 | 66.67% |
| ▷ Class constants | 1 | 33.33% |
| ▷ Public constants | 1 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
PNG images were not found in this plugin