Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼9.61ms] Passed 4 tests
Analyzing server-side resources used by Post from AWeber
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 38.26 ▼1.87 |
Dashboard /wp-admin | 3.32 ▼0.02 | 44.82 ▼22.49 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 46.66 ▼4.94 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 93.06 ▼8.87 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 32.85 ▼2.13 |
AWeber Post /wp-admin/edit.php?page=post_from_aweber_fetch | 3.21 | 34.21 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 3 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
can_compress_scripts |
theysaidso_admin_options |
db_upgraded |
widget_recent-posts |
widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Post from AWeber
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,804 ▲58 | 13.61 ▼0.70 | 1.85 ▼0.01 | 41.31 ▼2.40 |
Dashboard /wp-admin | 2,207 ▲16 | 5.83 ▲0.02 | 96.01 ▼25.50 | 36.83 ▼5.55 |
Posts /wp-admin/edit.php | 2,093 ▲1 | 2.03 ▲0.01 | 40.10 ▼1.84 | 34.46 ▼1.83 |
Add New Post /wp-admin/post-new.php | 1,536 ▲3 | 23.19 ▲0.08 | 644.75 ▼31.07 | 48.80 ▼9.15 |
Media Library /wp-admin/upload.php | 1,395 ▲10 | 4.25 ▲0.11 | 100.06 ▼3.83 | 42.30 ▼1.02 |
AWeber Post /wp-admin/edit.php?page=post_from_aweber_fetch | 762 | 2.02 | 23.73 | 25.61 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
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 take a closer look at the following
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/post-from-aweber/aweber.php:54
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
2 plugin tags: aweber, email
post-from-aweber/aweber.php 85% from 13 tests
The main PHP script in "Post from AWeber" version 1.2 is automatically included on every request by WordPress
Please take the time to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("post-from-aweber.php" instead of "aweber.php")
- Description: The description should be shorter than 140 characters (currently 276 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
No dangerous file extensions were detected38 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 10 | 9 | 36 |
Markdown | 1 | 1 | 0 | 2 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.13 |
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 | 2 | |
▷ Named functions | 2 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
There were not PNG files found in your plugin