Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.23MB] [CPU: ▼143.56ms] Passed 4 tests
A check of server-side resources used by Private Area for WordPress
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.03 ▲0.19 | 34.46 ▼0.66 |
Dashboard /wp-admin | 3.33 ▲0.28 | 59.39 ▲9.26 |
Posts /wp-admin/edit.php | 3.38 ▲0.27 | 52.52 ▼4.18 |
Add New Post /wp-admin/post-new.php | 5.63 ▲0.19 | 99.50 ▼576.40 |
Media Library /wp-admin/upload.php | 3.27 ▲0.27 | 40.21 ▲7.00 |
Private area /wp-admin/options-general.php?page=private-area-settings | 3.27 | 35.81 |
Server storage [IO: ▲0.19MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 29 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
Checking browser requirements for Private Area for WordPress
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,713 ▲117 | 15.80 ▲0.31 | 9.14 ▲2.62 | 48.78 ▼0.89 |
Dashboard /wp-admin | 3,007 ▲76 | 6.14 ▲0.21 | 166.61 ▲14.71 | 111.11 ▼18.04 |
Posts /wp-admin/edit.php | 2,776 ▲37 | 2.70 ▲0.00 | 70.20 ▼1.37 | 94.33 ▲0.12 |
Add New Post /wp-admin/post-new.php | 1,706 ▲23 | 18.70 ▼0.05 | 388.50 ▼11.29 | 116.14 ▲1.78 |
Media Library /wp-admin/upload.php | 1,783 ▼24 | 5.00 ▼0.01 | 163.70 ▲5.14 | 118.14 ▼5.62 |
Private area /wp-admin/options-general.php?page=private-area-settings | 1,116 | 2.52 | 61.78 | 70.27 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The plugin uninstalled completely, with no zombie files or tables
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
The following issues need your attention
- 8× PHP files output text when accessed directly:
- > /wp-content/plugins/wp-private-area/src/AccessController.php
- > /wp-content/plugins/wp-private-area/src/Controllers/RoleController.php
- > /wp-content/plugins/wp-private-area/src/Settings.php
- > /wp-content/plugins/wp-private-area/admin/settings.php
- > /wp-content/plugins/wp-private-area/src/AccessHandler.php
- > /wp-content/plugins/wp-private-area/src/Core.php
- > /wp-content/plugins/wp-private-area/src/Controller.php
- > /wp-content/plugins/wp-private-area/index.php
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/wp-private-area/admin/settings.php:61
- > 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 96% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
5 plugin tags: private, memberships, area, users, members
wp-private-area/index.php 92% from 13 tests
The principal PHP file in "Private Area for WordPress" v. 1.0.1 is loaded by WordPress automatically on each request
It is important to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("wp-private-area.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Everything looks great! No dangerous files found in this plugin1,387 lines of code in 25 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 17 | 330 | 802 | 1,175 |
CSS | 3 | 28 | 1 | 167 |
JavaScript | 4 | 14 | 36 | 44 |
JSON | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.33 |
Average class complexity | 11.73 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 44.00 |
Average method complexity | 2.23 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.00 |
Code structure | ||
---|---|---|
Namespaces | 4 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 11 | |
▷ Abstract classes | 1 | 9.09% |
▷ Concrete classes | 10 | 90.91% |
▷ Final classes | 0 | 0.00% |
Methods | 93 | |
▷ Static methods | 14 | 15.05% |
▷ Public methods | 81 | 87.10% |
▷ Protected methods | 1 | 1.08% |
▷ Private methods | 11 | 11.83% |
Functions | 18 | |
▷ Named functions | 3 | 16.67% |
▷ Anonymous functions | 15 | 83.33% |
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
PNG files should be compressed to save space and minimize bandwidth usage
No PNG images were found in this plugin