Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
It is recommended to fix the following installer errors
- This plugin did not install gracefully
- > Notice in wp-content/plugins/aweber-subscriber-form/index.php+14
Undefined variable: Fm_tweets_defaults
Server metrics [RAM: ▼1.85MB] [CPU: ▼193.96ms] Passed 4 tests
Analyzing server-side resources used by Aweber Subscriber Form
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 1.78 ▼0.94 | 5.15 ▼18.33 |
| Dashboard /wp-admin | 1.80 ▼1.26 | 9.38 ▼38.70 |
| Posts /wp-admin/edit.php | 1.80 ▼1.31 | 4.94 ▼47.88 |
| Add New Post /wp-admin/post-new.php | 1.80 ▼3.63 | 6.60 ▼658.25 |
| Media Library /wp-admin/upload.php | 1.80 ▼1.20 | 6.78 ▼31.00 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 6 new files
Database: no new tables, 1 new option
| New WordPress options |
|---|
| widget_themater_aweber |
Browser metrics Passed 4 tests
Aweber Subscriber Form: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,679 ▲83 | 15.83 ▲0.19 | 7.37 ▼0.53 | 52.87 ▲3.85 |
| Dashboard /wp-admin | 2,970 ▲37 | 5.86 ▼0.31 | 141.52 ▼43.83 | 113.98 ▼12.41 |
| Posts /wp-admin/edit.php | 2,739 ▼0 | 2.70 ▲0.02 | 72.64 ▲7.17 | 102.96 ▲2.52 |
| Add New Post /wp-admin/post-new.php | 1,604 ▼68 | 18.93 ▼0.16 | 372.78 ▼17.69 | 122.77 ▲3.05 |
| Media Library /wp-admin/upload.php | 1,807 ▼0 | 5.03 ▲0.02 | 166.02 ▲9.01 | 127.36 ▼12.52 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- This plugin did not uninstall without warnings or errors
- > Notice in wp-content/plugins/aweber-subscriber-form/index.php+14
Undefined variable: Fm_tweets_defaults
- The uninstall procedure has failed, leaving 1 option in the database
- widget_themater_aweber
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting 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 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please fix the following
- 3× 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/aweber-subscriber-form/index.php:16
- > PHP Notice
Undefined variable: Fm_tweets_defaults in wp-content/plugins/aweber-subscriber-form/index.php on line 14
- > PHP Warning
Creating default object from empty value in wp-content/plugins/aweber-subscriber-form/index.php on line 12
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
10 plugin tags: newsletter, aweber, email, email marketing, marketing...
aweber-subscriber-form/index.php 92% from 13 tests
"Aweber Subscriber Form" version 1.0.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("aweber-subscriber-form.php" instead of "index.php")
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
Good job! No executable or dangerous file extensions detected102 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 8 | 9 | 88 |
| CSS | 1 | 0 | 0 | 14 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.08 |
| Average class complexity | 2.00 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 2.00 |
| Average method complexity | 1.25 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 2.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 | 4 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 4 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.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
3 compressed PNG files occupy 0.00MB
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/green.png | 0.16KB | 0.24KB | 0.00% |
| images/email.png | 0.51KB | 0.59KB | 0.00% |
| images/name.png | 0.64KB | 0.57KB | ▼ 11.33% |