Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.04MB] [CPU: ▼8.56ms] Passed 4 tests
Analyzing server-side resources used by Spam Prevention for Contact Form 7 and Comments
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.57 ▲0.06 | 46.00 ▼1.39 |
Dashboard /wp-admin | 3.40 ▲0.01 | 54.35 ▼10.41 |
Posts /wp-admin/edit.php | 3.52 ▲0.11 | 52.03 ▼4.79 |
Add New Post /wp-admin/post-new.php | 5.98 ▲0.05 | 87.83 ▼17.66 |
Media Library /wp-admin/upload.php | 3.32 ▲0.05 | 42.97 ▲4.43 |
Server storage [IO: ▲1.18MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 34 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-posts |
db_upgraded |
widget_recent-comments |
Browser metrics Passed 4 tests
A check of browser resources used by Spam Prevention for Contact Form 7 and Comments
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,803 ▲32 | 14.18 ▼0.48 | 1.85 ▲0.04 | 46.64 ▲2.33 |
Dashboard /wp-admin | 2,198 ▲24 | 5.61 ▼0.06 | 85.75 ▼10.73 | 40.36 ▲1.71 |
Posts /wp-admin/edit.php | 2,100 ▼3 | 1.96 ▼0.01 | 35.71 ▼7.48 | 32.78 ▼3.85 |
Add New Post /wp-admin/post-new.php | 1,527 ▼1 | 23.44 ▲0.55 | 697.44 ▲83.45 | 54.85 ▲7.01 |
Media Library /wp-admin/upload.php | 1,397 ▼6 | 4.26 ▼0.04 | 113.79 ▲16.58 | 48.85 ▲3.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
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though everything seems fine, this is not 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 items
- 2× PHP files output text when accessed directly:
- > /wp-content/plugins/spam-prevention-for-contact-form-7-and-comments/public/partials/plugin-name-public-display.php
- > /wp-content/plugins/spam-prevention-for-contact-form-7-and-comments/1.3.6/public/partials/plugin-name-public-display.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
These attributes need to be fixed:
- Screenshots: A description for screenshot #1 is required in spam-prevention-for-contact-form-7-and-comments/assets to your readme.txt
- Plugin Name: You should set the name of your plugin on the first line (
=== spam-prevention-for-contact-form-7-and-comments ===
)
spam-prevention-for-contact-form-7-and-comments/sitelint.php 85% from 13 tests
The main file in "Spam Prevention for Contact Form 7 and Comments" v. 1.3.6 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please make the necessary changes and fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("spam-prevention-for-contact-form-7-and-comments.php" instead of "sitelint.php")
- 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
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
There were no executable files found in this plugin246 lines of code in 11 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 11 | 86 | 322 | 246 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.12 |
Average class complexity | 2.67 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 8.00 |
Average method complexity | 1.43 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 4.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 12 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 12 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 50 | |
▷ Static methods | 4 | 8.00% |
▷ Public methods | 42 | 84.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 8 | 16.00% |
Functions | 6 | |
▷ Named functions | 6 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 2 | |
▷ Global constants | 2 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 1.10MB with 0.72MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
1.3.6/screenshot-1.png | 564.78KB | 198.32KB | ▼ 64.89% |
screenshot-1.png | 564.78KB | 198.32KB | ▼ 64.89% |