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
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.31MB] [CPU: ▼19.53ms] Passed 4 tests
This is a short check of server-side resources used by Super Simple Post / Page Restrictor
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.44 ▼0.02 | 30.82 ▼7.68 |
Dashboard /wp-admin | 3.31 ▲0.00 | 37.87 ▼11.26 |
Posts /wp-admin/edit.php | 3.35 ▼0.00 | 38.04 ▼12.59 |
Add New Post /wp-admin/post-new.php | 4.67 ▼1.21 | 40.96 ▼46.58 |
Media Library /wp-admin/upload.php | 3.31 ▲0.08 | 36.39 ▲2.91 |
Super Simple Post / Page Restrictor /wp-admin/options-general.php?page=ss_pp_restrictor | 3.25 | 32.30 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 10 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
widget_recent-posts |
widget_theysaidso_widget |
widget_recent-comments |
can_compress_scripts |
db_upgraded |
Browser metrics Passed 4 tests
Super Simple Post / Page Restrictor: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,835 ▲78 | 13.22 ▼1.56 | 1.73 ▼0.24 | 41.76 ▼0.55 |
Dashboard /wp-admin | 2,210 ▲22 | 5.91 ▲1.04 | 101.04 ▼7.36 | 40.96 ▼5.83 |
Posts /wp-admin/edit.php | 2,102 ▲13 | 2.05 ▲0.05 | 34.49 ▼7.20 | 30.44 ▼5.55 |
Add New Post /wp-admin/post-new.php | 1,524 ▲10 | 23.16 ▲5.36 | 617.30 ▼58.22 | 52.82 ▼1.26 |
Media Library /wp-admin/upload.php | 1,395 ▲10 | 4.20 ▼0.01 | 99.06 ▼0.32 | 42.49 ▲0.42 |
Super Simple Post / Page Restrictor /wp-admin/options-general.php?page=ss_pp_restrictor | 953 | 2.00 | 32.17 | 28.37 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Almost there, just fix the following server-side errors
- > GET request to /wp-admin/options-general.php?page=ss_pp_restrictor
- > Notice in wp-content/plugins/super-simple-post-page-restricor/super-simple-post-page-restrictor-options.php+300
Trying to access array offset on value of type bool
SRP 50% 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 trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/super-simple-post-page-restricor/super-simple-post-page-restrictor.php:58
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
6 plugin tags: login, user login, restrict, restrictor, restrict content...
super-simple-post-page-restricor/super-simple-post-page-restrictor.php 92% from 13 tests
The principal PHP file in "Super Simple Post / Page Restrictor" v. 1.2.1 is loaded by WordPress automatically on each request
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("super-simple-post-page-restricor.php" instead of "super-simple-post-page-restrictor.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
There were no executable files found in this plugin374 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 127 | 164 | 334 |
Markdown | 1 | 18 | 0 | 34 |
JavaScript | 2 | 0 | 2 | 5 |
CSS | 1 | 1 | 1 | 1 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.59 |
Average class complexity | 34.50 |
▷ Minimum class complexity | 32.00 |
▷ Maximum class complexity | 37.00 |
Average method complexity | 3.68 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 23.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 25 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 23 | 92.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 2 | 8.00% |
Functions | 0 | |
▷ Named functions | 0 | 0.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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 compressed PNG files occupy 0.00MB
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/css/chosen-sprite.png | 0.63KB | 0.88KB | 0.00% |
assets/css/chosen-sprite@2x.png | 0.85KB | 0.83KB | ▼ 3.10% |