Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.81MB] [CPU: ▲0.99ms] Passed 4 tests
Analyzing server-side resources used by OOPSpam Anti-Spam
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 4.05 ▲0.58 | 45.24 ▲2.32 |
| Dashboard /wp-admin | 4.18 ▲0.88 | 53.14 ▲4.82 |
| Posts /wp-admin/edit.php | 4.22 ▲0.86 | 51.92 ▲0.14 |
| Add New Post /wp-admin/post-new.php | 6.90 ▲1.01 | 87.82 ▼1.54 |
| Media Library /wp-admin/upload.php | 4.14 ▲0.91 | 36.45 ▲3.04 |
| Form Ham Entries /wp-admin/admin.php?page=wp_oopspam_frm_ham_entries | 4.01 | 38.95 |
| Settings /wp-admin/admin.php?page=wp_oopspam_settings_page | 4.01 | 38.21 |
| Form Spam Entries /wp-admin/admin.php?page=wp_oopspam_frm_spam_entries | 4.01 | 36.99 |
Server storage [IO: ▲0.28MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 41 new files
Database: 2 new tables, 8 new options
| New tables |
|---|
| wp_oopspam_frm_ham_entries |
| wp_oopspam_frm_spam_entries |
| New WordPress options |
|---|
| widget_recent-comments |
| oopspam_db_version |
| can_compress_scripts |
| oopspamantispam_settings |
| widget_theysaidso_widget |
| widget_recent-posts |
| db_upgraded |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
A check of browser resources used by OOPSpam Anti-Spam
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,870 ▲108 | 14.74 ▲0.03 | 1.89 ▲0.16 | 41.13 ▼5.05 |
| Dashboard /wp-admin | 2,251 ▲71 | 5.55 ▼0.24 | 97.19 ▲6.53 | 42.04 ▲1.49 |
| Posts /wp-admin/edit.php | 2,156 ▲53 | 2.03 ▲0.01 | 42.83 ▲2.61 | 37.39 ▲0.97 |
| Add New Post /wp-admin/post-new.php | 1,562 ▲33 | 23.29 ▼0.22 | 657.78 ▲44.35 | 52.58 ▼5.37 |
| Media Library /wp-admin/upload.php | 1,455 ▲55 | 4.46 ▲0.23 | 97.85 ▼14.82 | 41.58 ▼4.29 |
| Form Ham Entries /wp-admin/admin.php?page=wp_oopspam_frm_ham_entries | 1,239 | 1.71 | 32.24 | 33.01 |
| Settings /wp-admin/admin.php?page=wp_oopspam_settings_page | 4,077 | 2.05 | 43.10 | 49.06 |
| Form Spam Entries /wp-admin/admin.php?page=wp_oopspam_frm_spam_entries | 1,239 | 1.74 | 26.95 | 30.93 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
These items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
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
Everything seems fine, however this is by no means an exhaustive test
SRP 50% 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
The following issues need your attention
- 27× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/oopspam-anti-spam/integration/Mailpoet.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/oopspam-anti-spam/integration/GravityForms.php:2
- > PHP Warning
require_once(ABSPATHwp-admin/includes/class-wp-list-table.php): failed to open stream: No such file or directory in wp-content/plugins/oopspam-anti-spam/include/UI/display-ham-entries.php on line 4
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/oopspam-anti-spam/include/UI/display-ham-entries.php on line 4
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/oopspam-anti-spam/integration/BricksForm.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/oopspam-anti-spam/integration/WPRegistration.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function current_user_can() in wp-content/plugins/oopspam-anti-spam/uninstall.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/oopspam-anti-spam/integration/Kadence.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/oopspam-anti-spam/integration/ElementorForm.php:3
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/oopspam-anti-spam/include/UI/display-spam-entries.php on line 4
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that need to be fixed:
- Screenshots: Add a description for screenshot #2 in oopspam-anti-spam/assets to your readme.txt
oopspam-anti-spam/oopspam-antispam.php 92% from 13 tests
The main file in "OOPSpam Anti-Spam" v. 1.1.55 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Main file name: Name the main plugin file the same as the plugin slug ("oopspam-anti-spam.php" instead of "oopspam-antispam.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Good job! No executable or dangerous file extensions detected6,440 lines of code in 38 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 32 | 960 | 583 | 4,642 |
| JavaScript | 2 | 117 | 16 | 1,224 |
| CSS | 3 | 38 | 33 | 556 |
| XML | 1 | 0 | 0 | 18 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.45 |
| Average class complexity | 15.88 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 28.00 |
| Average method complexity | 2.72 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 14.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 8 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 8 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 69 | |
| ▷ Static methods | 15 | 21.74% |
| ▷ Public methods | 67 | 97.10% |
| ▷ Protected methods | 2 | 2.90% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 121 | |
| ▷ Named functions | 118 | 97.52% |
| ▷ Anonymous functions | 3 | 2.48% |
| Constants | 1 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 1 | 100.00% |
| ▷ Public constants | 1 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
2 compressed PNG files occupy 0.00MB
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| include/libs/chosen-sprite.png | 0.63KB | 0.88KB | 0.00% |
| include/libs/chosen-sprite@2x.png | 0.85KB | 0.83KB | ▼ 3.10% |