Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼0.32ms] Passed 4 tests
Server-side resources used by Protect WP Config File from Phishing Attacks
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 43.48 ▲3.14 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 56.13 ▲4.85 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 45.85 ▼3.62 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 84.26 ▼5.64 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 42.50 ▲5.23 |
Server storage [IO: ▲0.03MB] [DB: ▲0.07MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 9 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| widget_recent-comments |
| db_upgraded |
| can_compress_scripts |
| widget_theysaidso_widget |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for Protect WP Config File from Phishing Attacks
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.37 ▼0.25 | 1.69 ▼0.08 | 42.97 ▼1.47 |
| Dashboard /wp-admin | 2,195 ▲18 | 5.63 ▼0.03 | 89.23 ▼7.78 | 40.13 ▼3.83 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 1.97 ▼0.01 | 36.88 ▼7.85 | 36.47 ▼5.39 |
| Add New Post /wp-admin/post-new.php | 1,537 ▼1 | 18.23 ▼4.68 | 648.39 ▼19.06 | 69.88 ▲14.27 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.23 ▼0.00 | 100.71 ▼11.28 | 44.79 ▼1.62 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- 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 Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Good news, no errors were detected
SRP Passed 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Looking good! No server-side errors or output on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 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
6 plugin tags: security, protect, config file, wp-config, phishing attacks...
protect-wp-config-from-phishing-attacks/protect-wp-config-from-phishing-attacks.php Passed 13 tests
The main PHP file in "Protect WP Config File from Phishing Attacks" ver. 15.01 adds more information about the plugin and also serves as the entry point for this plugin
104 characters long description:
Returns a blank white page if people try to load the wp-config file (or backups of it) in a web browser.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Everything looks great! No dangerous files found in this plugin310 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 129 | 178 | 153 |
| PO File | 2 | 42 | 80 | 126 |
| CSS | 1 | 21 | 6 | 31 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.25 |
| Average class complexity | 6.50 |
| ▷ Minimum class complexity | 4.00 |
| ▷ Maximum class complexity | 9.00 |
| Average method complexity | 2.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 5.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 | 11 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 11 | 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 | 8 | |
| ▷ Global constants | 8 | 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