Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.16MB] [CPU: ▼1.49ms] Passed 4 tests
This is a short check of server-side resources used by Effata Widget Areas
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.06 | 39.89 ▼7.62 |
Dashboard /wp-admin | 3.50 ▲0.19 | 53.35 ▲1.61 |
Posts /wp-admin/edit.php | 3.55 ▲0.19 | 54.55 ▲1.51 |
Add New Post /wp-admin/post-new.php | 6.11 ▲0.22 | 96.62 ▲1.25 |
Media Library /wp-admin/upload.php | 3.43 ▲0.19 | 39.43 ▼1.09 |
Widget Areas /wp-admin/edit.php?post_type=widget_area | 3.47 | 40.62 |
Server storage [IO: ▲0.16MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 13 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-posts |
widget_recent-comments |
db_upgraded |
theysaidso_admin_options |
can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for Effata Widget Areas
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,797 ▲11 | 14.36 ▼0.01 | 1.69 ▼0.48 | 41.86 ▼1.98 |
Dashboard /wp-admin | 2,200 ▲29 | 5.58 ▼0.12 | 88.41 ▼15.61 | 38.09 ▼6.55 |
Posts /wp-admin/edit.php | 2,108 ▲8 | 2.14 ▲0.12 | 39.09 ▲1.19 | 35.13 ▲0.50 |
Add New Post /wp-admin/post-new.php | 1,542 ▲16 | 18.15 ▼4.83 | 637.72 ▼1.31 | 72.54 ▲18.19 |
Media Library /wp-admin/upload.php | 1,411 ▲11 | 4.26 ▲0.06 | 96.62 ▼2.31 | 43.72 ▲1.23 |
Widget Areas /wp-admin/edit.php?post_type=widget_area | 1,099 | 1.98 | 31.00 | 32.03 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
- can_compress_scripts
- widget_recent-posts
- widget_theysaidso_widget
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP Passed 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
Looking good! No server-side errors or output on direct access of PHP files
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)
No browser errors were detected
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
10 plugin tags: widgetareas, areas, area, organize, widget...
effata-widget-areas/effata-widget-areas.php Passed 13 tests
"Effata Widget Areas" version 1.0.3's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
35 characters long description:
Plugin for controlling the sidebar.
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
Good job! No executable or dangerous file extensions detected1,094 lines of code in 7 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 107 | 264 | 803 |
PO File | 1 | 78 | 80 | 188 |
CSS | 1 | 14 | 12 | 57 |
JavaScript | 1 | 3 | 0 | 46 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.65 |
Average class complexity | 55.50 |
▷ Minimum class complexity | 6.00 |
▷ Maximum class complexity | 136.00 |
Average method complexity | 9.07 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 54.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 | 27 | |
▷ Static methods | 1 | 3.70% |
▷ Public methods | 26 | 96.30% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 1 | 3.70% |
Functions | 2 | |
▷ Named functions | 2 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 7 | |
▷ Global constants | 2 | 28.57% |
▷ Class constants | 5 | 71.43% |
▷ Public constants | 5 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
2 PNG files occupy 0.06MB with 0.03MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-1.png | 12.66KB | 5.97KB | ▼ 52.80% |
screenshot-2.png | 45.85KB | 21.62KB | ▼ 52.84% |