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.01MB] [CPU: ▼9.02ms] Passed 4 tests
This is a short check of server-side resources used by Restrict Content for WP Bakery
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.01 | 40.64 ▼2.20 |
| Dashboard /wp-admin | 3.35 ▼0.04 | 52.18 ▼16.26 |
| Posts /wp-admin/edit.php | 3.40 ▲0.00 | 47.11 ▼2.71 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.00 | 85.87 ▼14.91 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.00 | 36.72 ▲2.51 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 6 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_recent-posts |
| db_upgraded |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Restrict Content for WP Bakery: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,816 ▲70 | 14.25 ▼0.10 | 1.98 ▲0.23 | 46.58 ▲0.27 |
| Dashboard /wp-admin | 2,198 ▲18 | 5.61 ▼0.05 | 95.72 ▲5.09 | 41.86 ▲0.87 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.11 ▲0.08 | 34.14 ▼3.49 | 33.13 ▼6.03 |
| Add New Post /wp-admin/post-new.php | 1,536 ▲10 | 23.24 ▲0.20 | 660.78 ▼36.15 | 61.66 ▲10.67 |
| Media Library /wp-admin/upload.php | 1,403 ▲6 | 4.16 ▼0.04 | 95.98 ▼4.64 | 44.36 ▼2.46 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
The smoke test was a success, however most plugin functionality was not tested
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
The following issues need your attention
- 2× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/restrict-content-for-wp-bakery/vc-restrict-content-element.php
- > /wp-content/plugins/restrict-content-for-wp-bakery/wpb-restrict-content.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 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
5 plugin tags: wpbakery, wpbakery content restrict, content restriction, restrict content wpbakery, hide content
restrict-content-for-wp-bakery/wpb-restrict-content.php 85% from 13 tests
The main PHP file in "Restrict Content for WP Bakery" ver. 1.0.0 adds more information about the plugin and also serves as the entry point for this plugin
Please make the necessary changes and fix the following:
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
- Main file name: The principal plugin file should be the same as the plugin slug ("restrict-content-for-wp-bakery.php" instead of "wpb-restrict-content.php")
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
Everything looks great! No dangerous files found in this plugin210 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 26 | 49 | 206 |
| CSS | 1 | 0 | 0 | 4 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.58 |
| Average class complexity | 24.00 |
| ▷ Minimum class complexity | 24.00 |
| ▷ Maximum class complexity | 24.00 |
| Average method complexity | 5.60 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 22.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 | 5 | |
| ▷ Static methods | 4 | 80.00% |
| ▷ Public methods | 5 | 100.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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
1 PNG file occupies 0.02MB with 0.01MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/img/note.png | 24.06KB | 9.55KB | ▼ 60.32% |