Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
It is recommended to fix the following installer errors
- This plugin did not install gracefully
- > Warning in wp-content/plugins/files-fence/src/Installation.php+20
md5_file(.user.ini): failed to open stream: No such file or directory
Server metrics [RAM: ▲0.01MB] [CPU: ▲3.95ms] Passed 4 tests
This is a short check of server-side resources used by Files Fence
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 39.84 ▲1.27 |
Dashboard /wp-admin | 3.32 ▲0.01 | 50.51 ▲4.17 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 52.73 ▲7.22 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 94.63 ▲5.65 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 35.21 ▲4.72 |
Server storage [IO: ▲0.06MB] [DB: ▲0.79MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 18 new files
Database: 4 new tables, 9 new options
New tables |
---|
wp_filesfence_ignored |
wp_filesfence_unknown |
wp_filesfence_excluded |
wp_filesfence_know |
New WordPress options |
---|
db_upgraded |
filesfence_search_main_files |
widget_recent-posts |
filesfence_wp_version |
can_compress_scripts |
widget_theysaidso_widget |
filesfence_create |
theysaidso_admin_options |
widget_recent-comments |
Browser metrics Passed 4 tests
Files Fence: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,805 ▲44 | 14.72 ▲0.34 | 2.00 ▲0.47 | 50.79 ▲7.76 |
Dashboard /wp-admin | 2,208 ▲28 | 5.63 ▼0.05 | 99.66 ▲14.01 | 48.22 ▲5.77 |
Posts /wp-admin/edit.php | 2,116 ▲16 | 1.98 ▼0.04 | 39.05 ▲1.18 | 47.00 ▲13.97 |
Add New Post /wp-admin/post-new.php | 1,539 ▲13 | 23.18 ▼0.05 | 694.37 ▲50.12 | 61.18 ▲1.91 |
Media Library /wp-admin/upload.php | 1,410 ▲13 | 4.18 ▲0.01 | 94.32 ▼0.77 | 43.08 ▲0.83 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP Passed 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The SRP test was a success
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 96% from 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
5 plugin tags: files, checksum security, security, files integrity, files security
files-fence/filesfence.php 92% from 13 tests
"Files Fence" version 0.1.3's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please take the time to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("files-fence.php" instead of "filesfence.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
Success! There were no dangerous files found in this plugin950 lines of code in 15 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 15 | 141 | 272 | 950 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.33 |
Average class complexity | 11.00 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 47.00 |
Average method complexity | 2.69 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.00 |
Code structure | ||
---|---|---|
Namespaces | 2 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 10 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 10 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 60 | |
▷ Static methods | 9 | 15.00% |
▷ Public methods | 58 | 96.67% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 2 | 3.33% |
Functions | 2 | |
▷ Named functions | 1 | 50.00% |
▷ Anonymous functions | 1 | 50.00% |
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
Using a strong compression for your PNG files is a great way to speed-up your plugin
There were not PNG files found in your plugin