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
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼1.90MB] [CPU: ▼47.15ms] Passed 4 tests
This is a short check of server-side resources used by Safe Editor
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 38.79 ▲1.28 |
| Dashboard /wp-admin | 2.05 ▼1.26 | 5.13 ▼40.26 |
| Posts /wp-admin/edit.php | 2.05 ▼1.31 | 6.36 ▼40.81 |
| Add New Post /wp-admin/post-new.php | 2.05 ▼3.84 | 5.08 ▼78.39 |
| Media Library /wp-admin/upload.php | 2.05 ▼1.18 | 4.65 ▼29.15 |
| Safe Editor /wp-admin/tools.php?page=safe-editor | 2.05 | 5.40 |
Server storage [IO: ▲0.87MB] [DB: ▲0.07MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 53 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| db_upgraded |
| widget_recent-comments |
| widget_theysaidso_widget |
| can_compress_scripts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Safe Editor
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,854 ▲119 | 13.91 ▼0.39 | 1.84 ▲0.03 | 43.62 ▲0.52 |
| Dashboard /wp-admin | 2,238 ▲49 | 5.30 ▲0.33 | 115.00 ▼11.23 | 41.63 ▲0.70 |
| Posts /wp-admin/edit.php | 2,121 ▲29 | 2.37 ▲0.33 | 41.94 ▲0.50 | 36.69 ▼0.01 |
| Add New Post /wp-admin/post-new.php | 1,540 ▲15 | 23.35 ▲0.21 | 598.86 ▼106.30 | 33.83 ▼18.88 |
| Media Library /wp-admin/upload.php | 1,417 ▲29 | 4.56 ▲0.34 | 96.95 ▼1.59 | 40.89 ▼0.67 |
| Safe Editor /wp-admin/tools.php?page=safe-editor | 1,048 | 2.44 | 38.53 | 47.35 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- The plugin did not uninstall gracefully
- > User notice in wp-includes/functions.php+5905
Function wp_script_is was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the jquery handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Please fix the following server-side errors
- > GET request to /wp-admin/tools.php?page=safe-editor
- > User notice in wp-includes/functions.php+5905
Function wp_script_is was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the jquery handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/tools.php?page=safe-editor
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the jquery handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/tools.php?page=safe-editor
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the codemirror-theme-ambiance handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/tools.php?page=safe-editor
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the codemirror-theme-monokai handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/tools.php?page=safe-editor
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the codemirror-theme-solarized handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/tools.php?page=safe-editor
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the codemirror-theme-tomorrow-night-eighties handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/tools.php?page=safe-editor
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the codemirror-css handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/tools.php?page=safe-editor
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the codemirror handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/tools.php?page=safe-editor
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the codemirror-mode-css handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/tools.php?page=safe-editor
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the codemirror-mode-js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/tools.php?page=safe-editor
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the safe-editor-css handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/tools.php?page=safe-editor
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the safe-editor-js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
SRP 50% from 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
Almost there! Just fix the following items
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/safe-editor/index.php:14
- > 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 83% from 29 tests
readme.txt 81% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Please fix the following attributes:
- Contributors: The plugin contributors field is not present
- Screenshots: Screenshot #1 (CSS editor tab) image required
- Contributors: The plugin tags were not defined
safe-editor/index.php 85% from 13 tests
"Safe Editor" version 1.2.1's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("safe-editor.php" instead of "index.php")
- Description: Keep the plugin description shorter than 140 characters (currently 228 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Everything looks great! No dangerous files found in this plugin9,587 lines of code in 48 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 8 | 880 | 971 | 7,669 |
| CSS | 32 | 214 | 160 | 1,151 |
| HTML | 6 | 93 | 0 | 528 |
| PHP | 1 | 29 | 10 | 166 |
| Sass | 1 | 1 | 0 | 73 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.43 |
| Average class complexity | 14.00 |
| ▷ Minimum class complexity | 14.00 |
| ▷ Maximum class complexity | 14.00 |
| Average method complexity | 2.86 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 8.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 | 7 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 7 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 1 | |
| ▷ Named functions | 1 | 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 Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
2 PNG files occupy 0.27MB with 0.08MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 278.06KB | 118.65KB | ▼ 57.33% |
| img/yes.png | 0.53KB | 0.58KB | 0.00% |