Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Install script ran successfully
Server metrics [RAM: ▲0.10MB] [CPU: ▼6.48ms] Passed 4 tests
This is a short check of server-side resources used by WP Editor
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.49 ▲0.03 | 44.61 ▼3.07 |
Dashboard /wp-admin | 3.42 ▲0.07 | 56.44 ▼11.09 |
Posts /wp-admin/edit.php | 3.51 ▲0.16 | 54.40 ▲2.90 |
Add New Post /wp-admin/post-new.php | 6.10 ▲0.22 | 89.72 ▼13.59 |
Media Library /wp-admin/upload.php | 3.35 ▲0.12 | 38.73 ▲1.85 |
Plugin Editor /wp-admin/plugins.php?page=wpeditor_plugin | 3.43 | 35.19 |
Theme Editor /wp-admin/themes.php?page=wpeditor_themes | 3.90 | 46.93 |
Server storage [IO: ▲2.08MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 83 new files
Database: 1 new table, 7 new options
New tables |
---|
wp_wpeditor_settings |
New WordPress options |
---|
can_compress_scripts |
widget_recent-posts |
widget_recent-comments |
widget_theysaidso_widget |
db_upgraded |
wpe_settings |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for WP Editor
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,896 ▲135 | 14.25 ▼0.12 | 2.18 ▲0.46 | 47.50 ▲4.74 |
Dashboard /wp-admin | 2,285 ▲82 | 5.99 ▲0.18 | 111.07 ▲3.10 | 101.34 ▲60.61 |
Posts /wp-admin/edit.php | 2,118 ▲11 | 1.98 ▼0.07 | 41.68 ▲0.58 | 34.39 ▲0.23 |
Add New Post /wp-admin/post-new.php | 1,548 ▼6 | 18.37 ▲0.25 | 729.71 ▲101.92 | 66.80 ▲17.25 |
Media Library /wp-admin/upload.php | 1,415 ▲18 | 4.28 ▲0.03 | 119.38 ▲17.67 | 45.54 ▼1.58 |
Plugin Editor /wp-admin/plugins.php?page=wpeditor_plugin | 1,498 | 2.97 | 68.79 | 79.13 |
Theme Editor /wp-admin/themes.php?page=wpeditor_themes | 1,651 | 4.67 | 85.61 | 144.91 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
You still need to fix the following
- Uninstall procedure validation failed for this plugin
- > Notice in wp-content/plugins/wp-editor/uninstall.php+6
Constant WPEDITOR_PATH already defined
- The uninstall procedure has failed, leaving 7 options in the database
- wpe_settings
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Almost there, just fix the following server-side errors
- 2 occurences, only the last one shown
- > GET request to /wp-admin/themes.php?page=wpeditor_themes
- > User deprecated in wp-includes/functions.php+5463
Function screen_icon is deprecated since version 3.8.0 with no alternative available.
- 2 occurences, only the last one shown
- > GET request to /wp-admin/themes.php?page=wpeditor_themes
- > User deprecated in wp-includes/functions.php+5463
Function get_screen_icon is deprecated since version 3.8.0 with no alternative available.
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please take a closer look at the following
- 5× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_bloginfo() in wp-content/plugins/wp-editor/wpeditor.php:35
- > PHP Fatal error
Uncaught Error: Call to undefined function screen_icon() in wp-content/plugins/wp-editor/views/theme-editor.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function screen_icon() in wp-content/plugins/wp-editor/views/plugin-editor.php:3
- > PHP Fatal error
Uncaught Error: Class 'WPEditorSetting' not found in wp-content/plugins/wp-editor/views/settings.php:2
- > PHP Fatal error
Uncaught Error: Class 'WPEditorSetting' not found in wp-content/plugins/wp-editor/views/OLDsettings.php:3
- > 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 83% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
These attributes need to be fixed:
- Tags: There are too many tags (18 tag instead of maximum 10)
- Screenshots: These screenshots require images: #1 (Settings page for WP Editor), #2 (Syntax highlighting in Page/Post editor), #3 (Updated plugin editor with Ajax file browser), #4 (Updated theme editor with file upload enabled), #5 (Fancybox integration)
wp-editor/wpeditor.php 77% from 13 tests
"WP Editor" version 1.2.7's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please make the necessary changes and fix the following:
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
- Domain Path: The domain path points to an invalid folder, "/languages/" does not exist
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("wp-editor.php" instead of "wpeditor.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
Good job! No executable or dangerous file extensions detected16,880 lines of code in 47 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 20 | 1,281 | 1,294 | 11,814 |
PHP | 16 | 304 | 159 | 3,683 |
CSS | 9 | 80 | 128 | 1,377 |
SQL | 2 | 0 | 0 | 6 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.43 |
Average class complexity | 33.80 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 91.00 |
Average method complexity | 6.66 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 35.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 10 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 10 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 58 | |
▷ Static methods | 52 | 89.66% |
▷ Public methods | 58 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 2 | |
▷ Named functions | 2 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 9 | |
▷ Global constants | 9 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
31 PNG files occupy 1.16MB with 0.93MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/less.png | 3.15KB | 0.47KB | ▼ 84.98% |
screenshot-1.png | 113.71KB | 37.21KB | ▼ 67.28% |
extensions/nivo-lightbox/themes/default/next@2x.png | 4.14KB | 0.98KB | ▼ 76.27% |
images/sql.png | 3.20KB | 0.53KB | ▼ 83.40% |
extensions/nivo-lightbox/themes/default/next.png | 3.12KB | 0.32KB | ▼ 89.60% |