Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.04MB] [CPU: ▼11.44ms] Passed 4 tests
Server-side resources used by Files Inspector
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.50 ▲0.04 | 38.32 ▼2.21 |
| Dashboard /wp-admin | 3.36 ▲0.02 | 40.57 ▼25.01 |
| Posts /wp-admin/edit.php | 3.48 ▲0.12 | 47.31 ▲1.50 |
| Add New Post /wp-admin/post-new.php | 5.94 ▲0.06 | 80.74 ▼14.04 |
| Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 32.71 ▼4.50 |
| Files Inspector /wp-admin/options-general.php?page=files-inspector/filesinespector.php | 3.29 | 52.48 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 8 new files
Database: 1 new table, 6 new options
| New tables |
|---|
| wp_filesinspector |
| New WordPress options |
|---|
| widget_recent-posts |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-comments |
| widget_theysaidso_widget |
| can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for Files Inspector
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,806 ▲60 | 13.60 ▼0.75 | 1.62 ▼0.17 | 40.03 ▼2.50 |
| Dashboard /wp-admin | 2,215 ▲27 | 4.87 ▼0.01 | 111.56 ▼3.19 | 39.54 ▼5.80 |
| Posts /wp-admin/edit.php | 2,095 ▲6 | 2.00 ▼0.01 | 38.79 ▼1.23 | 34.34 ▲0.91 |
| Add New Post /wp-admin/post-new.php | 1,547 ▲28 | 18.36 ▼4.84 | 617.77 ▼63.71 | 73.92 ▲17.65 |
| Media Library /wp-admin/upload.php | 1,394 ▲9 | 4.22 ▲0.02 | 94.04 ▼7.15 | 40.94 ▼2.32 |
| Files Inspector /wp-admin/options-general.php?page=files-inspector/filesinespector.php | 783 | 2.07 | 24.37 | 28.26 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- This plugin does not fully uninstall, leaving 1 table in the database
- wp_filesinspector
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
Smoke tests Passed 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)
Everything seems fine, however this is by no means an exhaustive test
SRP Passed 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
No output text or server-side errors detected 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)
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
5 plugin tags: security, files-inspector, file-compare, file, file-changes
files-inspector/filesinespector.php 85% from 13 tests
The principal PHP file in "Files Inspector" v. 0.1 is loaded by WordPress automatically on each request
Please make the necessary changes and fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("files-inspector.php" instead of "filesinespector.php")
- Description: Keep the plugin description shorter than 140 characters (currently 149 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected500 lines of code in 7 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 99 | 84 | 435 |
| JavaScript | 1 | 7 | 3 | 65 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.32 |
| Average class complexity | 6.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 12.00 |
| Average method complexity | 1.65 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 9.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 4 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 4 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 28 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 22 | 78.57% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 6 | 21.43% |
| Functions | 4 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 4 | 100.00% |
| Constants | 4 | |
| ▷ Global constants | 2 | 50.00% |
| ▷ Class constants | 2 | 50.00% |
| ▷ Public constants | 2 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
There are no PNG files in this plugin