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
This plugin's installer ran successfully
Server metrics [RAM: ▼1.94MB] [CPU: ▼50.42ms] Passed 4 tests
Analyzing server-side resources used by Wasp.io
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.04 ▼1.42 | 3.77 ▼33.28 |
| Dashboard /wp-admin | 2.06 ▼1.24 | 6.38 ▼41.70 |
| Posts /wp-admin/edit.php | 2.06 ▼1.29 | 5.32 ▼42.68 |
| Add New Post /wp-admin/post-new.php | 2.06 ▼3.82 | 5.64 ▼84.00 |
| Media Library /wp-admin/upload.php | 2.06 ▼1.16 | 4.12 ▼25.96 |
| Wasp.io /wp-admin/admin.php?page=wasp_plugin | 2.06 | 5.88 |
| Configuration /wp-admin/admin.php?page=wasp-settings | 2.06 | 4.94 |
| About /wp-admin/admin.php?page=wasp-about | 2.06 | 6.07 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 6 new files
Database: no new tables, 16 new options
| New WordPress options |
|---|
| wasp_track_ajax |
| widget_recent-posts |
| wasp_track_404 |
| wasp_track_js |
| wasp_track_users |
| widget_recent-comments |
| wasp_ignored_levels |
| theysaidso_admin_options |
| wasp_filters |
| can_compress_scripts |
| ... |
Browser metrics Passed 4 tests
A check of browser resources used by Wasp.io
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,940 ▲194 | 13.97 ▼0.35 | 5.13 ▲3.32 | 42.08 ▲1.43 |
| Dashboard /wp-admin | 2,245 ▲60 | 5.79 ▲0.87 | 112.31 ▼7.06 | 81.29 ▲37.26 |
| Posts /wp-admin/edit.php | 2,124 ▲35 | 2.00 ▼0.05 | 34.81 ▼6.60 | 36.72 ▲1.13 |
| Add New Post /wp-admin/post-new.php | 1,699 ▲166 | 22.56 ▼0.37 | 725.61 ▲81.83 | 62.23 ▲7.10 |
| Media Library /wp-admin/upload.php | 1,424 ▲39 | 4.22 ▲0.04 | 99.67 ▼10.36 | 84.07 ▲37.63 |
| Wasp.io /wp-admin/admin.php?page=wasp_plugin | 847 | 2.06 | 26.02 | 27.88 |
| Configuration /wp-admin/admin.php?page=wasp-settings | 826 | 2.06 | 28.37 | 29.91 |
| About /wp-admin/admin.php?page=wasp-about | 860 | 2.15 | 26.45 | 34.54 |
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 had uncaught errors
- > 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.)
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Please fix the following server-side errors
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=wasp-about
- > 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.)
SRP 0% 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
- 2× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/waspio/about.php
- > /wp-content/plugins/waspio/wasp.php
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Warning
Use of undefined constant WASP_LOGO - assumed 'WASP_LOGO' (this will throw an Error in a future version of PHP) in wp-content/plugins/waspio/settings.php on line 13
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/waspio/settings.php:22
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 87% 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:
- Screenshots: Screenshot #1 () image missing
- Donate link: Please fix this invalid url: ""
waspio/wasp.php 85% from 13 tests
"Wasp.io" version 2.2.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("waspio.php" instead of "wasp.php")
- Description: Please don't use more than 140 characters for the plugin description (currently 183 characters long)
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
Everything looks great! No dangerous files found in this plugin1,131 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 200 | 425 | 1,131 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.56 |
| Average class complexity | 138.00 |
| ▷ Minimum class complexity | 138.00 |
| ▷ Maximum class complexity | 138.00 |
| Average method complexity | 6.24 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 17.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 | 26 | |
| ▷ Static methods | 1 | 3.85% |
| ▷ Public methods | 10 | 38.46% |
| ▷ Protected methods | 1 | 3.85% |
| ▷ Private methods | 15 | 57.69% |
| Functions | 15 | |
| ▷ Named functions | 14 | 93.33% |
| ▷ Anonymous functions | 1 | 6.67% |
| Constants | 11 | |
| ▷ Global constants | 11 | 100.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
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| img/wasp.png | 1.62KB | 0.76KB | ▼ 53.40% |