Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼4.05ms] Passed 4 tests
This is a short check of server-side resources used by BadgeOS Restrict Content Pro
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 41.65 ▼5.42 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 49.48 ▼1.53 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 47.50 ▼3.32 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 88.60 ▼5.45 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 37.43 ▼2.01 |
| BadgeOS RCP Integration /wp-admin/admin.php?page=badgeos_rcp_settings | 3.00 | 22.76 |
Server storage [IO: ▲0.11MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 12 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| widget_recent-comments |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| db_upgraded |
Browser metrics Passed 4 tests
BadgeOS Restrict Content Pro: 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,818 ▲57 | 14.29 ▼0.06 | 1.96 ▲0.28 | 39.14 ▼3.25 |
| Dashboard /wp-admin | 2,198 ▲21 | 5.64 ▼0.02 | 85.64 ▼9.79 | 43.40 ▲5.02 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.03 ▲0.01 | 35.71 ▲0.36 | 41.79 ▲0.27 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 20.94 ▼2.68 | 673.65 ▼36.61 | 51.14 ▼19.84 |
| Media Library /wp-admin/upload.php | 1,400 ▲3 | 4.15 ▼0.03 | 113.49 ▲8.29 | 47.73 ▼0.89 |
| BadgeOS RCP Integration /wp-admin/admin.php?page=badgeos_rcp_settings | 28 | 0.42 | 0.13 | 3.70 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- can_compress_scripts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
The following issues need your attention
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/badgeos-restrict-content-pro-integration/includes/steps-ui.php:29
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/badgeos-restrict-content-pro-integration/includes/rules-engine.php:43
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
These are user-side errors you should fix
- > GET request to /wp-admin/admin.php?page=badgeos_rcp_settings
- > Network (severe)
wp-admin/admin.php?page=badgeos_rcp_settings - Failed to load resource: the server responded with a status of 403 (Forbidden)
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Please fix the following attributes:
- Tags: Please delete some tags, you are using 15 tag instead of maximum 10
badgeos-restrict-content-pro-integration/badgeos-recpro.php 69% from 13 tests
The principal PHP file in "BadgeOS Restrict Content Pro" v. 1.0.0 is loaded by WordPress automatically on each request
Please make the necessary changes and fix the following:
- Description: Keep the plugin description shorter than 140 characters (currently 161 characters long)
- Text Domain: Please use dashes and lowercase characters for text domains
- Domain Path: You should use only dashes and lowercase characters for the domain path ("domain/path")
- Main file name: It is recommended to name the main PHP file as the plugin slug ("badgeos-restrict-content-pro-integration.php" instead of "badgeos-recpro.php")
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
Everything looks great! No dangerous files found in this plugin1,674 lines of code in 10 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 8 | 623 | 812 | 1,650 |
| Markdown | 2 | 15 | 0 | 24 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.46 |
| Average class complexity | 30.00 |
| ▷ Minimum class complexity | 11.00 |
| ▷ Maximum class complexity | 73.00 |
| Average method complexity | 4.22 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 17.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 5 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 5 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 45 | |
| ▷ Static methods | 1 | 2.22% |
| ▷ Public methods | 39 | 86.67% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 6 | 13.33% |
| Functions | 19 | |
| ▷ Named functions | 19 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 10 | |
| ▷ Global constants | 9 | 90.00% |
| ▷ Class constants | 1 | 10.00% |
| ▷ Public constants | 1 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
No PNG files were detected