Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
It is recommended to fix the following installer errors
- Install procedure validation failed for this plugin
- > Parse error in wp-content/plugins/custom-post-type-lockdown/CPTLockdown.php+241
syntax error, unexpected end of file
Server metrics [RAM: ▼0.01MB] [CPU: ▼5.21ms] Passed 4 tests
Server-side resources used by Custom Post Type Lockdown WordPress
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 46.47 ▲6.56 |
| Dashboard /wp-admin | 3.31 ▼0.04 | 42.92 ▼21.34 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 47.60 ▲3.33 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 96.15 ▼2.31 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 34.01 ▼0.52 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 2 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| widget_theysaidso_widget |
| db_upgraded |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Custom Post Type Lockdown WordPress
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 13.66 ▼0.72 | 1.81 ▲0.09 | 39.79 ▼7.35 |
| Dashboard /wp-admin | 2,200 ▲12 | 5.83 ▼0.01 | 105.82 ▼9.74 | 38.84 ▼9.33 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 1.99 ▼0.06 | 39.29 ▲2.82 | 34.90 ▲1.37 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲14 | 23.28 ▲0.16 | 659.81 ▲7.16 | 68.29 ▲12.07 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.25 ▲0.05 | 105.83 ▲8.21 | 47.12 ▲4.38 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Please fix the following items
- Zombie WordPress options were found after uninstall: 6 options
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-posts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Good news, no errors were detected
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
Please take a closer look at the following
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Parse error
syntax error, unexpected end of file in wp-content/plugins/custom-post-type-lockdown/CPTLockdown.php on line 241
- > PHP Parse error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
5 plugin tags: custom post type, lockout, overwrite, redirect, custom post type archives
custom-post-type-lockdown/CPTLockdown.php 92% from 13 tests
The main file in "Custom Post Type Lockdown WordPress" v. 1.11 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("custom-post-type-lockdown.php" instead of "CPTLockdown.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
Good job! No executable or dangerous file extensions detected193 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 35 | 13 | 193 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.58 |
| 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 | 6 | |
| ▷ Named functions | 6 | 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
PNG files should be compressed to save space and minimize bandwidth usage
There were not PNG files found in your plugin