Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.02MB] [CPU: ▲0.50ms] Passed 4 tests
Server-side resources used by SpamAssassin Preferences
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.03 | 36.94 ▼4.48 |
| Dashboard /wp-admin | 3.33 ▲0.03 | 46.50 ▼2.00 |
| Posts /wp-admin/edit.php | 3.38 ▲0.02 | 50.18 ▲5.21 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 107.45 ▲8.15 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 33.99 ▲3.26 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 6 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-posts |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for SpamAssassin Preferences
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲47 | 14.45 ▼0.17 | 1.78 ▼0.29 | 40.90 ▼4.38 |
| Dashboard /wp-admin | 2,210 ▲19 | 4.86 ▼0.02 | 110.10 ▲9.05 | 42.49 ▼3.45 |
| Posts /wp-admin/edit.php | 2,096 ▲7 | 2.00 ▼0.05 | 40.66 ▲0.61 | 37.04 ▲0.70 |
| Add New Post /wp-admin/post-new.php | 1,545 ▲3 | 18.26 ▲0.19 | 607.51 ▼7.59 | 49.64 ▼4.80 |
| Media Library /wp-admin/upload.php | 1,392 ▲4 | 4.14 ▼0.05 | 95.91 ▼3.45 | 41.96 ▼5.16 |
| SpamAssassin Preferences /wp-admin/spamassassin-preferences.php | 26 | 0.44 | 0.06 | 14.13 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though no errors were found, this is by no means an exhaustive test
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
Please fix the following
- 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/spamassassin-preferences/spamassassin-preferences.php:178
- > PHP Fatal error
Uncaught Error: Call to undefined function SAPrefsUserFieldList() in wp-content/plugins/spamassassin-preferences/spamassassin-preferences-admin-options.php:7
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Please take a look at the following user-side issues
- > GET request to /wp-admin/spamassassin-preferences.php
- > Network (severe)
wp-admin/spamassassin-preferences.php - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
1 plugin tags: spamassassin
spamassassin-preferences/spamassassin-preferences.php Passed 13 tests
The main PHP script in "SpamAssassin Preferences" version 1.0 is automatically included on every request by WordPress
67 characters long description:
Set your SpamAssassin preferences from your WordPress user profile.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected426 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 112 | 100 | 426 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.47 |
| 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 | 12 | |
| ▷ Named functions | 12 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 1 | |
| ▷ Global constants | 1 | 100.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
There are no PNG files in this plugin