Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼5.13ms] Passed 4 tests
Analyzing server-side resources used by Spam Blocker S1
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.01 | 35.97 ▼6.81 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 47.65 ▲1.47 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 48.55 ▲0.13 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 84.49 ▼15.31 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 37.00 ▲3.27 |
| Spam Blocker S1 /wp-admin/options-general.php?page=sbs1_config | 3.20 | 31.13 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 2 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-comments |
| widget_recent-posts |
| theysaidso_admin_options |
| db_upgraded |
| can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for Spam Blocker S1
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲47 | 13.61 ▼0.76 | 1.85 ▼0.30 | 39.47 ▼10.68 |
| Dashboard /wp-admin | 2,213 ▲25 | 4.82 ▼0.05 | 97.45 ▼21.31 | 39.06 ▼2.87 |
| Posts /wp-admin/edit.php | 2,093 ▲4 | 2.04 ▲0.01 | 39.48 ▼2.37 | 33.99 ▼3.31 |
| Add New Post /wp-admin/post-new.php | 1,536 ▲22 | 23.29 ▲5.84 | 662.69 ▲5.20 | 52.91 ▼18.08 |
| Media Library /wp-admin/upload.php | 1,389 ▲1 | 4.18 ▼0.02 | 96.08 ▼12.78 | 42.41 ▼1.37 |
| Spam Blocker S1 /wp-admin/options-general.php?page=sbs1_config | 790 | 2.03 | 24.54 | 45.47 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
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
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
The following issues need your attention
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/spam-blocker-s1/s1.php:17
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
2 plugin tags: comments, spam
spam-blocker-s1/s1.php 77% from 13 tests
"Spam Blocker S1" version 3...'s primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please take the time to fix the following:
- Version: Plugin version number should only contain digits separated by dots (ex. "1.0.3" instead of "3...")
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("spam-blocker-s1.php" instead of "s1.php")
- Description: The description should be shorter than 140 characters (currently 288 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
No dangerous file extensions were detected42 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 6 | 9 | 42 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.38 |
| 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 | 3 | |
| ▷ Named functions | 3 | 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
PNG files should be compressed to save space and minimize bandwidth usage
There were not PNG files found in your plugin