Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.07MB] [CPU: ▼5.36ms] Passed 4 tests
A check of server-side resources used by WPCF7 Anti-spam
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.52 ▲0.06 | 41.25 ▼5.79 |
| Dashboard /wp-admin | 3.38 ▲0.07 | 54.01 ▲1.08 |
| Posts /wp-admin/edit.php | 3.43 ▲0.07 | 48.55 ▼3.83 |
| Add New Post /wp-admin/post-new.php | 5.96 ▲0.07 | 88.32 ▼12.88 |
| Media Library /wp-admin/upload.php | 3.30 ▲0.07 | 38.75 ▲3.59 |
| WPCF7 Anti-spam /wp-admin/options-general.php?page=wpcf7_antispam | 3.24 | 30.20 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 3 new files
Database: no new tables, 16 new options
| New WordPress options |
|---|
| wpcf7_antispam_hash |
| wpcf7_antispam_mail_cc |
| can_compress_scripts |
| widget_theysaidso_widget |
| wpcf7_antispam_collector |
| widget_recent-posts |
| widget_recent-comments |
| wpcf7_antispam_pass |
| wpcf7_antispam_mail_smtp_host |
| db_upgraded |
| ... |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WPCF7 Anti-spam
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,820 ▲34 | 14.38 ▲0.01 | 3.12 ▲0.98 | 41.59 ▼1.55 |
| Dashboard /wp-admin | 2,202 ▲25 | 5.62 ▼0.05 | 90.46 ▼5.27 | 41.49 ▼4.51 |
| Posts /wp-admin/edit.php | 2,104 ▲7 | 2.04 ▲0.06 | 36.60 ▲0.37 | 34.90 ▲0.46 |
| Add New Post /wp-admin/post-new.php | 1,529 ▲3 | 23.39 ▲0.14 | 654.04 ▼44.58 | 55.65 ▲2.97 |
| Media Library /wp-admin/upload.php | 1,407 ▲7 | 4.16 ▼0.11 | 106.31 ▼6.62 | 46.12 ▲2.81 |
| WPCF7 Anti-spam /wp-admin/options-general.php?page=wpcf7_antispam | 983 | 2.01 | 22.62 | 29.85 |
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
The following items require your attention
- This plugin did not uninstall successfully, leaving 16 options in the database
- wpcf7_antispam_mail_cc
- widget_recent-posts
- wpcf7_antispam_mail_sender
- wpcf7_antispam_mail_smtp_host
- widget_theysaidso_widget
- wpcf7_antispam_mail_recipient
- theysaidso_admin_options
- wpcf7_antispam_hash
- wpcf7_antispam_mail_smtp_login
- can_compress_scripts
- ...
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Smoke test failed, please fix the following
- > GET request to /wp-admin/options-general.php?page=wpcf7_antispam
- > User deprecated in wp-includes/functions.php+5463
Function screen_icon is deprecated since version 3.8.0 with no alternative available.
- > GET request to /wp-admin/options-general.php?page=wpcf7_antispam
- > User deprecated in wp-includes/functions.php+5463
Function get_screen_icon is deprecated since version 3.8.0 with no alternative available.
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Almost there! Just fix the following items
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wpcf7-anti-spam/wpcf7_antispam.php:35
- > 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 on the user side
Optimizations
Plugin configuration 96% 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
4 plugin tags: anti-spam, spam, cf7, contact form 7
wpcf7-anti-spam/wpcf7_antispam.php 92% from 13 tests
"WPCF7 Anti-spam" version 1.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("wpcf7-anti-spam.php" instead of "wpcf7_antispam.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
Good job! No executable or dangerous file extensions detected380 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 45 | 13 | 319 |
| JavaScript | 1 | 10 | 4 | 61 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.28 |
| 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 | 13 | |
| ▷ Named functions | 13 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
No PNG files were detected