Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.35MB] [CPU: ▼3.08ms] Passed 4 tests
Analyzing server-side resources used by All in One WordPress Content Restriction
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.84 ▲0.38 | 48.36 ▲11.76 |
Dashboard /wp-admin | 3.68 ▲0.37 | 52.80 ▲3.43 |
Posts /wp-admin/edit.php | 3.73 ▲0.37 | 46.17 ▼3.21 |
Add New Post /wp-admin/post-new.php | 6.21 ▲0.33 | 81.76 ▼18.62 |
Media Library /wp-admin/upload.php | 3.53 ▲0.31 | 38.32 ▲6.08 |
Server storage [IO: ▲0.44MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 57 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_theysaidso_widget |
widget_recent-comments |
theysaidso_admin_options |
widget_recent-posts |
can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for All in One WordPress Content Restriction
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,897 ▲151 | 13.51 ▼0.80 | 8.93 ▲7.07 | 41.68 ▲2.04 |
Dashboard /wp-admin | 2,202 ▲17 | 5.88 ▲0.96 | 103.94 ▼5.19 | 82.00 ▲41.10 |
Posts /wp-admin/edit.php | 2,097 ▲8 | 1.98 ▼0.08 | 34.48 ▼0.53 | 32.30 ▼1.22 |
Add New Post /wp-admin/post-new.php | 1,524 ▲10 | 23.37 ▲5.87 | 770.89 ▲120.05 | 65.45 ▲19.68 |
Media Library /wp-admin/upload.php | 1,399 ▲8 | 4.22 ▲0.09 | 99.88 ▼2.12 | 74.30 ▲29.98 |
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
- This plugin does not fully uninstall, leaving 6 options in the database
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
The following issues need your attention
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/all-in-one-content-restriction/all-in-one-content-restriction.php
- 26× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/all-in-one-content-restriction/templates/menu-page/post-types.php:16
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr_e() in wp-content/plugins/all-in-one-content-restriction/templates/menu-page/steps/content-shield-option.php:14
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/all-in-one-content-restriction/templates/menu-page/protections/obfuscate.php:15
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/all-in-one-content-restriction/templates/menu-page/steps/access-restriction.php:14
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/all-in-one-content-restriction/templates/menu-page/selected-items.php:21
- > PHP Fatal error
Uncaught Error: Call to undefined function HeyMehedi\\All_In_One_Content_Restriction\\add_filter() in wp-content/plugins/all-in-one-content-restriction/includes/classes/protections/class-obfuscate.php:15
- > PHP Fatal error
Uncaught Error: Call to undefined function HeyMehedi\\All_In_One_Content_Restriction\\add_action() in wp-content/plugins/all-in-one-content-restriction/includes/classes/protections/class-login-and-back.php:13
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/all-in-one-content-restriction/templates/menu-list-table.php:10
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/all-in-one-content-restriction/templates/menu-page/protection-type.php:12
- > PHP Fatal error
Uncaught Error: Class 'HeyMehedi\\All_In_One_Content_Restriction' not found in wp-content/plugins/all-in-one-content-restriction/includes/classes/class-scripts.php:18
- > 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)
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Attributes that need to be fixed:
- Screenshots: Add descriptions for screenshots #1, #2, #3, #4 in all-in-one-content-restriction/assets to your readme.txt
all-in-one-content-restriction/all-in-one-content-restriction.php 92% from 13 tests
The main file in "All in One WordPress Content Restriction" v. 1.6.8 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 156 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 detected2,711 lines of code in 53 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 40 | 598 | 519 | 1,687 |
JavaScript | 7 | 149 | 42 | 558 |
CSS | 6 | 94 | 57 | 466 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.36 |
Average class complexity | 11.23 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 53.00 |
Average method complexity | 2.83 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.00 |
Code structure | ||
---|---|---|
Namespaces | 2 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 22 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 22 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 123 | |
▷ Static methods | 45 | 36.59% |
▷ Public methods | 108 | 87.80% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 15 | 12.20% |
Functions | 1 | |
▷ Named functions | 1 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 8 | |
▷ Global constants | 8 | 100.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
2 compressed PNG files occupy 0.00MB
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
admin/images/question-mark.png | 0.45KB | 0.54KB | 0.00% |
admin/images/dash-icon.png | 1.10KB | 1.40KB | 0.00% |