Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
These installer errors require your attention
- Install procedure validation failed for this plugin
- > Compile error in wp-content/plugins/amazing-ads-manager/amazing-ads-manager.php+614
'continue' not in the 'loop' or 'switch' context
Server metrics [RAM: ▲0.00MB] [CPU: ▼2.58ms] Passed 4 tests
An overview of server-side resources used by Amazing Ads Manager
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 40.63 ▼1.99 |
Dashboard /wp-admin | 3.31 ▲0.00 | 47.93 ▼1.14 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 49.58 ▼2.80 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 98.31 ▼2.61 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 35.01 ▼2.90 |
Server storage [IO: ▲0.78MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 13 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
widget_recent-comments |
widget_recent-posts |
widget_theysaidso_widget |
db_upgraded |
theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Amazing Ads Manager
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲28 | 14.72 ▲0.43 | 1.71 ▲0.01 | 44.07 ▼2.23 |
Dashboard /wp-admin | 2,198 ▲21 | 5.62 ▲0.01 | 99.26 ▲10.40 | 43.76 ▼4.08 |
Posts /wp-admin/edit.php | 2,103 ▲3 | 2.10 ▼0.01 | 35.60 ▼6.82 | 33.09 ▼7.95 |
Add New Post /wp-admin/post-new.php | 1,526 ▼5 | 23.42 ▲0.35 | 646.20 ▼41.24 | 54.70 ▲1.88 |
Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.18 ▲0.07 | 97.72 ▼12.77 | 42.10 ▼4.98 |
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
You still need to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
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)
Everything seems fine, however 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× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/amazing-ads-manager/widgets/amads-widget.php:7
- > PHP Fatal error
'continue' not in the 'loop' or 'switch' context in wp-content/plugins/amazing-ads-manager/amazing-ads-manager.php on line 614
- > 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, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
Attributes that need to be fixed:
- Screenshots: These screenshots need descriptions #2, #3, #4 in amazing-ads-manager/assets to your readme.txt
- Tags: You are using too many tags: 12 tag instead of maximum 10
amazing-ads-manager/amazing-ads-manager.php 92% from 13 tests
The entry point to "Amazing Ads Manager" version 0.0.5 is a PHP file that has certain tags in its header comment area
The following require your attention:
- Description: Please keep the plugin description shorter than 140 characters (currently 319 characters long)
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 detected1,034 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 128 | 84 | 781 |
CSS | 2 | 2 | 25 | 133 |
JavaScript | 2 | 15 | 20 | 120 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.28 |
Average class complexity | 22.00 |
▷ Minimum class complexity | 3.00 |
▷ Maximum class complexity | 58.00 |
Average method complexity | 3.40 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 15.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 4 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 4 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 35 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 35 | 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 | 4 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 4 | 100.00% |
▷ Public constants | 4 | 100.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
6 PNG files occupy 0.73MB with 0.30MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-2.png | 165.24KB | 50.50KB | ▼ 69.44% |
assets/images/icon.png | 1.06KB | 1.15KB | 0.00% |
assets/images/v-logo_meta.png | 1.33KB | 1.34KB | 0.00% |
screenshot-4.png | 317.37KB | 97.74KB | ▼ 69.20% |
screenshot-1.png | 156.17KB | 49.41KB | ▼ 68.36% |