Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Please fix the following installer errors
- This plugin did not install gracefully
- > Deprecated in wp-content/plugins/better-file-editor/better_file_editor.php+20
Methods with the same name as their class will not be constructors in a future version of PHP; BetterFileEditorPlugin has a deprecated constructor
Server metrics [RAM: ▲0.01MB] [CPU: ▼4.09ms] Passed 4 tests
A check of server-side resources used by Better File Editor
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 39.35 ▼2.87 |
Dashboard /wp-admin | 3.31 ▲0.01 | 50.94 ▼1.54 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 52.80 ▲1.19 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 86.10 ▼9.62 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 37.07 ▼2.31 |
Server storage [IO: ▲5.84MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 331 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
can_compress_scripts |
db_upgraded |
widget_recent-comments |
widget_theysaidso_widget |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for Better File Editor
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲28 | 14.38 ▼0.18 | 1.68 ▲0.07 | 44.14 ▼2.27 |
Dashboard /wp-admin | 2,198 ▲24 | 5.61 ▲0.10 | 84.21 ▼11.63 | 41.00 ▼0.83 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 1.96 ▼0.18 | 35.66 ▼0.48 | 36.57 ▼2.82 |
Add New Post /wp-admin/post-new.php | 1,526 ▼5 | 23.06 ▼0.05 | 646.75 ▼32.80 | 58.60 ▲0.68 |
Media Library /wp-admin/upload.php | 1,403 ▲3 | 4.27 ▲0.13 | 94.90 ▼16.24 | 42.70 ▼8.03 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Good news, no errors were detected
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
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/better-file-editor/better_file_editor.php:23
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Attributes that need to be fixed:
- Screenshots: Please add an image for screenshot #1 (Theme Editor)
better-file-editor/better_file_editor.php 85% from 13 tests
The principal PHP file in "Better File Editor" v. 2.3.1 is loaded by WordPress automatically on each request
The following require your attention:
- 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
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("better-file-editor.php" instead of "better_file_editor.php")
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 detected759 lines of code in 325 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 321 | 56 | 44 | 665 |
PHP | 1 | 9 | 17 | 36 |
Sass | 1 | 5 | 0 | 35 |
JSON | 1 | 0 | 0 | 22 |
CSS | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.00 |
Average class complexity | 1.00 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 1.00 |
Average method complexity | 1.00 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 1.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 3 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 3 | 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 | 0 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
1 PNG file occupies 0.11MB with 0.08MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-1.png | 113.31KB | 35.78KB | ▼ 68.42% |