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.01MB] [CPU: ▼3.43ms] Passed 4 tests
A check of server-side resources used by Email Blaster Newsletter Signup Form
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 39.39 ▼0.55 |
Dashboard /wp-admin | 3.31 ▲0.01 | 46.81 ▼6.72 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 46.88 ▼0.20 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 84.60 ▼5.75 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 35.74 ▼0.71 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 4 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_emailblaster |
can_compress_scripts |
theysaidso_admin_options |
widget_recent-comments |
db_upgraded |
widget_recent-posts |
Browser metrics Passed 4 tests
A check of browser resources used by Email Blaster Newsletter Signup Form
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲65 | 13.59 ▼0.79 | 1.76 ▼0.07 | 43.23 ▼1.15 |
Dashboard /wp-admin | 2,206 ▲21 | 5.88 ▲0.83 | 101.24 ▼16.10 | 35.96 ▼7.67 |
Posts /wp-admin/edit.php | 2,092 ▲3 | 2.01 ▼0.01 | 40.51 ▲2.03 | 33.50 ▼0.58 |
Add New Post /wp-admin/post-new.php | 1,533 ▲14 | 23.49 ▲0.25 | 653.26 ▼32.84 | 60.02 ▲9.42 |
Media Library /wp-admin/upload.php | 1,385 ▼3 | 4.31 ▲0.11 | 97.99 ▼5.98 | 43.98 ▲3.01 |
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 did not uninstall successfully, leaving 7 options in the database
- widget_recent-comments
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- widget_emailblaster
- theysaidso_admin_options
- 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 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 items
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/email-blaster-newsletter-signup-form/emailblaster.class.php:11
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/email-blaster-newsletter-signup-form/emailblaster.class.php:11
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
Attributes that require attention:
- Tags: There are too many tags (17 tag instead of maximum 10)
email-blaster-newsletter-signup-form/index.php 85% from 13 tests
"Email Blaster Newsletter Signup Form" version 1.0.7's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
You should first fix the following items:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("email-blaster-newsletter-signup-form.php" instead of "index.php")
- Description: Keep the plugin description shorter than 140 characters (currently 498 characters long)
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
Everything looks great! No dangerous files found in this plugin74 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 115 | 50 | 66 |
JavaScript | 1 | 1 | 7 | 8 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.13 |
Average class complexity | 3.00 |
▷ Minimum class complexity | 3.00 |
▷ Maximum class complexity | 3.00 |
Average method complexity | 1.00 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 1.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 5 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 5 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 1 | |
▷ Named functions | 1 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
No PNG files were detected