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
Installer ran successfully
Server metrics [RAM: ▼1.14MB] [CPU: ▼48.75ms] Passed 4 tests
This is a short check of server-side resources used by Visual Editor Custom Buttons
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.84 ▼0.63 | 15.20 ▼26.48 |
Dashboard /wp-admin | 2.87 ▼0.43 | 22.57 ▼30.12 |
Posts /wp-admin/edit.php | 2.87 ▼0.48 | 17.14 ▼29.41 |
Add New Post /wp-admin/post-new.php | 2.87 ▼3.01 | 21.41 ▼108.99 |
Media Library /wp-admin/upload.php | 2.87 ▼0.35 | 17.80 ▼16.76 |
Add new /wp-admin/post-new.php?post_type=vecb_editor_buttons | 2.88 | 18.08 |
All buttons /wp-admin/edit.php?post_type=vecb_editor_buttons | 2.88 | 18.60 |
Server storage [IO: ▲0.18MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 95 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
db_upgraded |
widget_recent-comments |
widget_recent-posts |
widget_theysaidso_widget |
can_compress_scripts |
Browser metrics Passed 4 tests
Visual Editor Custom Buttons: an overview of browser usage
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,846 ▲100 | 13.35 ▼0.81 | 1.90 ▼0.22 | 43.41 ▼0.65 |
Dashboard /wp-admin | 2,249 ▲64 | 5.21 ▲0.31 | 114.76 ▲13.16 | 42.96 ▲4.08 |
Posts /wp-admin/edit.php | 2,132 ▲43 | 2.31 ▲0.30 | 44.94 ▲6.73 | 35.68 ▼0.39 |
Add New Post /wp-admin/post-new.php | 1,551 ▲37 | 22.77 ▲5.27 | 657.10 ▲52.19 | 73.53 ▲17.86 |
Media Library /wp-admin/upload.php | 1,434 ▲49 | 4.54 ▲0.32 | 104.73 ▲0.57 | 44.42 ▲1.28 |
Add new /wp-admin/post-new.php?post_type=vecb_editor_buttons | 2,548 | 3.24 | 82.24 | 68.73 |
All buttons /wp-admin/edit.php?post_type=vecb_editor_buttons | 1,099 | 2.27 | 36.94 | 30.19 |
Settings /wp-admin/visual-editor-custom-buttons.php | 26 | 0.44 | 0.07 | 15.91 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- The plugin did not uninstall gracefully
- > User deprecated in wp-includes/functions.php+5453
Function get_currentuserinfo is deprecated since version 4.5.0! Use wp_get_current_user() instead.
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
- widget_recent-posts
Smoke tests 25% 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)
Please fix the following server-side errors
- 3 occurences, only the last one shown
- > GET request to /wp-admin/edit.php?post_type=vecb_editor_buttons
- > POST request to /wp-admin/admin-ajax.php
- > User deprecated in wp-includes/functions.php+5453
Function get_currentuserinfo is deprecated since version 4.5.0! Use wp_get_current_user() instead.
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
Almost there! Just fix the following items
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/visual-editor-custom-buttons/visual-editor-custom-buttons.php:13
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There are user-side issues you should fix
- > GET request to /wp-admin/post-new.php?post_type=vecb_editor_buttons
- > Javascript (severe) in unknown
/wp-admin/post-new.php?post_type=vecb_editor_buttons 456:4 Uncaught ReferenceError: QTags is not defined
- > GET request to /wp-admin/edit.php?post_type=vecb_editor_buttons
- > Javascript (severe) in unknown
/wp-admin/edit.php?post_type=vecb_editor_buttons 297:4 Uncaught ReferenceError: QTags is not defined
- > GET request to /wp-admin/visual-editor-custom-buttons.php
- > Network (severe)
wp-admin/visual-editor-custom-buttons.php - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Attributes that need to be fixed:
- Donate link: Please fix this invalid URI: ""
visual-editor-custom-buttons/visual-editor-custom-buttons.php Passed 13 tests
The main PHP file in "Visual Editor Custom Buttons" ver. 1.6.0.3 adds more information about the plugin and also serves as the entry point for this plugin
49 characters long description:
Create custom buttons in Wordpress Visual Editor.
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 detected988 lines of code in 7 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 389 | 168 | 661 |
CSS | 3 | 30 | 3 | 160 |
PO File | 1 | 32 | 34 | 101 |
JavaScript | 2 | 33 | 13 | 66 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.22 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 19 | |
▷ Named functions | 19 | 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
84 PNG files occupy 0.11MB with 0.09MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
js/icons/picasa.png | 1.46KB | 0.44KB | ▼ 69.62% |
js/icons/squares_sixteen.png | 0.99KB | 0.11KB | ▼ 88.50% |
js/icons/line_single.png | 0.97KB | 0.11KB | ▼ 89.06% |
js/icons/user.png | 1.26KB | 0.31KB | ▼ 75.10% |
js/icons/tab_space.png | 1.23KB | 0.42KB | ▼ 65.71% |