Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼7.22ms] Passed 4 tests
Analyzing server-side resources used by Buddypress Messages Spam Blocker
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 39.16 ▼1.61 |
Dashboard /wp-admin | 3.31 ▲0.00 | 47.77 ▼8.86 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 46.22 ▼7.87 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 88.10 ▼10.53 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 37.34 ▼0.59 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 6 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_recent-posts |
widget_recent-comments |
widget_theysaidso_widget |
can_compress_scripts |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Buddypress Messages Spam Blocker: an overview of browser usage
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,814 ▲53 | 14.34 ▲0.18 | 2.19 ▲0.17 | 46.09 ▲0.73 |
Dashboard /wp-admin | 2,198 ▲24 | 5.59 ▲0.02 | 85.49 ▼9.58 | 41.45 ▼0.97 |
Posts /wp-admin/edit.php | 2,100 ▲18 | 1.95 ▼0.06 | 36.95 ▲1.27 | 34.82 ▼0.94 |
Add New Post /wp-admin/post-new.php | 1,526 ▼2 | 23.15 ▼0.23 | 658.70 ▲5.67 | 54.60 ▼5.23 |
Media Library /wp-admin/upload.php | 1,400 ▲3 | 4.14 ▼0.03 | 107.45 ▲8.01 | 42.86 ▼1.57 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
- can_compress_scripts
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
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/buddypress-messages-spam-blocker/buddypress-messages-spamblocker.php:19
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/buddypress-messages-spam-blocker/plugin.php:6
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
3 plugin tags: messages, buddypress, spam
buddypress-messages-spam-blocker/buddypress-messages-spamblocker.php 85% from 13 tests
"Buddypress Messages Spam Blocker" version 2.5's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
It is important to 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
- Main file name: The principal plugin file should be the same as the plugin slug ("buddypress-messages-spam-blocker.php" instead of "buddypress-messages-spamblocker.php")
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
Success! There were no dangerous files found in this plugin122 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 14 | 38 | 85 |
PO File | 1 | 2 | 7 | 37 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.37 |
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 | 4 | |
▷ Named functions | 4 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
There are no PNG files in this plugin