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
Installer ran successfully
Server metrics [RAM: ▼1.22MB] [CPU: ▼44.39ms] Passed 4 tests
Server-side resources used by WP Security Coat
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.75 ▼0.71 | 15.50 ▼24.54 |
Dashboard /wp-admin | 2.79 ▼0.51 | 17.25 ▼34.74 |
Posts /wp-admin/edit.php | 2.79 ▼0.57 | 15.85 ▼42.53 |
Add New Post /wp-admin/post-new.php | 2.79 ▼3.10 | 22.84 ▼75.73 |
Media Library /wp-admin/upload.php | 2.79 ▼0.44 | 16.12 ▼20.37 |
Server storage [IO: ▲0.47MB] [DB: ▲0.00MB] 67% from 3 tests
Filesystem and database footprint
It is recommended to fix the following issues
- Illegal file modification found: 1 file (0.60KB) outside of "wp-content/plugins/wp-security-coat/" and "wp-content/uploads/"
- (modified) .htaccess
Filesystem: 33 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-posts |
theysaidso_admin_options |
db_upgraded |
can_compress_scripts |
widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for WP Security Coat
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,887 ▲126 | 13.45 ▼0.90 | 8.33 ▲6.56 | 45.49 ▼0.73 |
Dashboard /wp-admin | 2,195 ▲18 | 5.54 ▼0.11 | 96.09 ▲7.00 | 82.84 ▲42.78 |
Posts /wp-admin/edit.php | 2,118 ▲15 | 2.05 ▲0.05 | 37.01 ▼2.18 | 32.88 ▼4.91 |
Add New Post /wp-admin/post-new.php | 1,549 ▲23 | 18.27 ▼5.35 | 645.46 ▼63.64 | 61.05 ▼3.05 |
Media Library /wp-admin/upload.php | 1,418 ▲18 | 4.27 ▲0.04 | 97.49 ▼12.01 | 74.38 ▲27.67 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- This plugin did not uninstall without warnings or errors
- > Notice in wp-content/plugins/wp-security-coat/admin/class-wp-seccoat-admin.php+80
Trying to access array offset on value of type bool
- This plugin does not fully uninstall, leaving 6 options in the database
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though no errors were found, this is by no means an exhaustive test
SRP 0% 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
Please fix the following
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/wp-security-coat/public/partials/wp-seccoat-public-display.php
- 5× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr_e() in wp-content/plugins/wp-security-coat/admin/partials/wp-secoat-admin-security-server.php:20
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr_e() in wp-content/plugins/wp-security-coat/admin/partials/wp-secoat-admin-security-wordpress.php:19
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr_e() in wp-content/plugins/wp-security-coat/admin/partials/wp-secoat-admin-security-php-mysql.php:20
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/wp-security-coat/includes/class-wp-seccoat-deactivator.php:21
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html() in wp-content/plugins/wp-security-coat/admin/partials/wp-seccoat-admin-display.php:31
- > PHP Fatal error
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 86% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Attributes that need to be fixed:
- Screenshots: These screenshots need descriptions #1, #2, #3, #4, #5, #6 in wp-security-coat/assets to your readme.txt
wp-security-coat/wp-seccoat.php 77% from 13 tests
The entry point to "WP Security Coat" version 1.0.0 is a PHP file that has certain tags in its header comment area
Please take the time to fix the following:
- 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
- Description: Keep the plugin description shorter than 140 characters (currently 259 characters long)
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("wp-security-coat.php" instead of "wp-seccoat.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
No dangerous file extensions were detected959 lines of code in 20 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 16 | 573 | 477 | 900 |
JavaScript | 2 | 11 | 5 | 37 |
CSS | 2 | 21 | 7 | 22 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.19 |
Average class complexity | 6.38 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 38.00 |
Average method complexity | 1.96 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 31.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 8 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 8 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 45 | |
▷ Static methods | 11 | 24.44% |
▷ Public methods | 40 | 88.89% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 11.11% |
Functions | 3 | |
▷ Named functions | 3 | 100.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 50% from 2 tests
Image compression 50% from 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
7 PNG files occupy 0.39MB with 0.26MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
admin/images/wpsecurityco.png | 5.42KB | 1.17KB | ▼ 78.36% |
admin/images/scpages1.png | 147.47KB | 16.16KB | ▼ 89.04% |
(invalid) admin/images/wpsecuritycoatlg.png | 0.00KB | 0.00KB | 0.00% |
admin/images/wpsecuritycoat.png | 91.30KB | 8.02KB | ▼ 91.21% |
admin/images/wpsecuritycoa.png | 7.43KB | 1.64KB | ▼ 77.88% |