Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.10MB] [CPU: ▼2.79ms] Passed 4 tests
This is a short check of server-side resources used by Website Toolbox Community
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.54 ▲0.08 | 39.79 ▼5.74 |
Dashboard /wp-admin | 3.41 ▲0.11 | 46.13 ▼1.58 |
Posts /wp-admin/edit.php | 3.45 ▲0.10 | 46.08 ▼5.78 |
Add New Post /wp-admin/post-new.php | 6.11 ▲0.22 | 553.10 ▲452.73 |
Media Library /wp-admin/upload.php | 3.35 ▲0.13 | 37.47 ▲1.93 |
Website Toolbox Community /wp-admin/options-general.php?page=websitetoolboxoptions | 3.28 | 32.71 |
Server storage [IO: ▲0.29MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 15 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
theysaidso_admin_options |
can_compress_scripts |
db_upgraded |
widget_theysaidso_widget |
widget_recent-posts |
Browser metrics Passed 4 tests
Website Toolbox Community: an overview of browser usage
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,808 ▲73 | 13.18 ▼1.11 | 1.63 ▼0.34 | 41.55 ▼7.89 |
Dashboard /wp-admin | 2,214 ▲23 | 5.03 ▲0.16 | 104.12 ▼0.81 | 39.17 ▼3.35 |
Posts /wp-admin/edit.php | 2,097 ▲8 | 2.01 ▲0.03 | 35.02 ▼5.19 | 33.19 ▼1.80 |
Add New Post /wp-admin/post-new.php | 1,522 ▼11 | 17.88 ▼5.28 | 600.88 ▼69.52 | 48.97 ▲2.60 |
Media Library /wp-admin/upload.php | 1,396 ▲5 | 4.34 ▲0.18 | 93.87 ▼5.44 | 43.22 ▼0.97 |
Website Toolbox Community /wp-admin/options-general.php?page=websitetoolboxoptions | 828 | 2.18 | 22.82 | 25.22 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
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 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/website-toolbox-forums/forumHook.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/website-toolbox-forums/forumHook.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% 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 your attention:
- Tags: You are using too many tags: 12 tag instead of maximum 10
website-toolbox-forums/websitetoolbox.php 85% from 13 tests
"Website Toolbox Community" version 1.9.4'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:
- Description: The description should be shorter than 140 characters (currently 164 characters long)
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("website-toolbox-forums.php" instead of "websitetoolbox.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Everything looks great! No dangerous files found in this plugin2,849 lines of code in 11 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 6 | 164 | 358 | 2,290 |
CSS | 2 | 24 | 0 | 274 |
JavaScript | 2 | 3 | 0 | 265 |
SVG | 1 | 1 | 1 | 20 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.42 |
Average class complexity | 1.00 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 1.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 5 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.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 | 92 | |
▷ Named functions | 86 | 93.48% |
▷ Anonymous functions | 6 | 6.52% |
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
Using a strong compression for your PNG files is a great way to speed-up your plugin
3 PNG files occupy 0.12MB with 0.06MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
img/wp-settingpage.png | 46.98KB | 23.99KB | ▼ 48.93% |
img/wp-settingpage (1) .png | 46.98KB | 23.99KB | ▼ 48.93% |
admin/images/embedComments.png | 27.53KB | 9.67KB | ▼ 64.85% |