Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.91MB] [CPU: ▼170.90ms] Passed 4 tests
This is a short check of server-side resources used by Post Restrictor
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.84 ▲0.12 | 36.50 ▲13.59 |
| Dashboard /wp-admin | 2.74 ▼0.32 | 32.29 ▼14.06 |
| Posts /wp-admin/edit.php | 2.74 ▼0.38 | 26.36 ▼31.91 |
| Add New Post /wp-admin/post-new.php | 2.74 ▼2.70 | 25.22 ▼630.35 |
| Media Library /wp-admin/upload.php | 2.74 ▼0.26 | 30.31 ▼7.29 |
| Post Restrictor /wp-admin/admin.php?page=postRestrictorOptions | 2.74 | 26.48 |
Server storage [IO: ▲0.00MB] [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: 2 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
Checking browser requirements for Post Restrictor
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,708 ▲71 | 15.89 ▼0.15 | 11.05 ▲2.16 | 53.99 ▲1.42 |
| Dashboard /wp-admin | 2,975 ▲44 | 5.92 ▼0.15 | 147.57 ▲1.23 | 119.49 ▲5.72 |
| Posts /wp-admin/edit.php | 2,744 ▲5 | 2.71 ▼0.00 | 74.07 ▲2.64 | 93.63 ▼9.79 |
| Add New Post /wp-admin/post-new.php | 1,686 ▲3 | 15.75 ▼2.98 | 429.40 ▲37.74 | 127.04 ▲12.72 |
| Media Library /wp-admin/upload.php | 1,812 ▲5 | 5.04 ▼0.00 | 165.73 ▲12.14 | 130.54 ▲4.88 |
| Post Restrictor /wp-admin/admin.php?page=postRestrictorOptions | 28 | 0.90 | 0.07 | 14.11 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- The plugin did not uninstall gracefully
- > User deprecated in wp-includes/functions.php+5495
has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead.
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Please fix the following server-side errors
- > GET request to /wp-admin/admin.php?page=postRestrictorOptions
- > User deprecated in wp-includes/functions.php+5495
has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead.
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
The following issues need your attention
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/post-restrictor/PostRestrictor.php:57
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There are user-side issues you should fix
- > GET request to /wp-admin/admin.php?page=postRestrictorOptions
- > Network (severe)
wp-admin/admin.php?page=postRestrictorOptions - Failed to load resource: the server responded with a status of 403 (Forbidden)
Optimizations
Plugin configuration 79% from 29 tests
readme.txt 75% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that need to be fixed:
- Requires at least: Invalid version format
- Donate link: Invalid url: ""
- Plugin Name: Please specify the plugin name on the first line (
=== post-restrictor ===) - Tested up to: Invalid version format
post-restrictor/PostRestrictor.php 85% from 13 tests
Analyzing the main PHP file in "Post Restrictor" version 1.2
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("post-restrictor.php" instead of "PostRestrictor.php")
- Description: The description should be shorter than 140 characters (currently 150 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Good job! No executable or dangerous file extensions detected30 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 49 | 27 | 30 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.80 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 0.00 |
| ▷ Minimum method complexity | 0.00 |
| ▷ Maximum method complexity | 0.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 0 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 0 | 0.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 0 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 0 | 0.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 3 | |
| ▷ Named functions | 3 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
There are no PNG files in this plugin