Benchmarks
Plugin footprint 47% 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 successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.30MB] [CPU: ▼1.47ms] Passed 4 tests
An overview of server-side resources used by Connect Restrict Content Pro to Discord AddOn
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.77 ▲0.31 | 40.54 ▼1.04 |
Dashboard /wp-admin | 3.60 ▲0.29 | 48.62 ▼1.62 |
Posts /wp-admin/edit.php | 3.71 ▲0.35 | 49.03 ▲1.09 |
Add New Post /wp-admin/post-new.php | 6.22 ▲0.33 | 95.27 ▼4.32 |
Media Library /wp-admin/upload.php | 3.52 ▲0.29 | 41.43 ▲6.22 |
Scheduled Actions /wp-admin/tools.php?page=action-scheduler | 3.67 | 47.38 |
Discord Settings /wp-admin/admin.php?page=rcp-discord | 3.59 | 41.73 |
Server storage [IO: ▲0.88MB] [DB: ▲0.01MB] 67% from 3 tests
A short overview of filesystem and database impact
Just a few items left to fix
- The plugin illegally modified 1 file (0.00KB) outside of "wp-content/plugins/connect-restrictcontentpro-to-discord-addon/" and "wp-content/uploads/"
- (new file) wp-content/0f7bdec9-9bbc-42bf-9ecd-c2264994e89ediscord_api_logs.txt
Filesystem: 131 new files
Database: 4 new tables, 31 new options
New tables |
---|
wp_actionscheduler_logs |
wp_actionscheduler_actions |
wp_actionscheduler_claims |
wp_actionscheduler_groups |
New WordPress options |
---|
ets_restrictcontentpro_retry_api_count |
ets_restrictcontentpro_discord_payment_failed |
action_scheduler_hybrid_store_demarkation |
ets_restrictcontentpro_discord_welcome_message |
ets_restrictcontentpro_discord_send_membership_expired_dm |
ets_restrictcontentpro_discord_send_welcome_dm |
widget_recent-comments |
db_upgraded |
ets_restrictcontentpro_discord_job_queue_concurrency |
ets_restrictcontentpro_discord_uuid_file_name |
... |
Browser metrics Passed 4 tests
An overview of browser requirements for Connect Restrict Content Pro to Discord AddOn
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,804 ▲69 | 13.20 ▼1.46 | 1.77 ▲0.06 | 38.01 ▼3.75 |
Dashboard /wp-admin | 2,210 ▲18 | 4.87 ▼0.13 | 102.87 ▼8.19 | 40.52 ▼2.83 |
Posts /wp-admin/edit.php | 2,090 ▲1 | 2.05 ▲0.07 | 34.99 ▼3.77 | 31.64 ▼1.44 |
Add New Post /wp-admin/post-new.php | 1,517 ▼25 | 17.64 ▼0.53 | 642.61 ▼7.41 | 65.42 ▲5.01 |
Media Library /wp-admin/upload.php | 1,395 ▲7 | 4.22 ▲0.02 | 97.31 ▼3.96 | 42.03 ▲0.05 |
Scheduled Actions /wp-admin/tools.php?page=action-scheduler | 1,214 | 2.17 | 24.19 | 32.24 |
Discord Settings /wp-admin/admin.php?page=rcp-discord | 1,915 | 3.02 | 74.77 | 68.12 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.01MB] 25% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- The plugin did not uninstall gracefully
- > Notice in wp-content/plugins/connect-restrictcontentpro-to-discord-addon/uninstall.php+34
Undefined index: plugin
- Zombie tables detected upon uninstall: 4 tables
- wp_actionscheduler_logs
- wp_actionscheduler_claims
- wp_actionscheduler_groups
- wp_actionscheduler_actions
- This plugin did not uninstall successfully, leaving 31 options in the database
- action_scheduler_hybrid_store_demarkation
- ets_restrictcontentpro_discord_payment_failed
- ets_restrictcontentpro_discord_welcome_message
- schema-ActionScheduler_LoggerSchema
- action_scheduler_lock_async-request-runner
- ets_restrictcontentpro_discord_connect_button_bg_color
- ets_restrictcontentpro_discord_cancel_message
- ets_restrictcontentpro_discord_disconnect_button_bg_color
- theysaidso_admin_options
- ets_restrictcontentpro_discord_send_welcome_dm
- ...
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 0% 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
Please fix the following
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/connect-restrictcontentpro-to-discord-addon/public/partials/restrictcontentpro-discord-addon-public-display.php
- 51× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'ActionScheduler_Abstract_QueueRunner' not found in wp-content/plugins/connect-restrictcontentpro-to-discord-addon/includes/libraries/action-scheduler/classes/ActionScheduler_QueueRunner.php:6
- > PHP Fatal error
Uncaught Error: Class 'ActionScheduler_Schedule_Deprecated' not found in wp-content/plugins/connect-restrictcontentpro-to-discord-addon/includes/libraries/action-scheduler/classes/abstracts/ActionScheduler_Abstract_Schedule.php:6
- > PHP Fatal error
Uncaught Error: Class 'Action_Scheduler\\Migration\\ActionMigrator' not found in wp-content/plugins/connect-restrictcontentpro-to-discord-addon/includes/libraries/action-scheduler/classes/migration/DryRun_ActionMigrator.php:15
- > PHP Fatal error
Uncaught Error: Call to undefined function sanitize_text_field() in wp-content/plugins/connect-restrictcontentpro-to-discord-addon/admin/partials/pages/restrictcontentpro-discord-settings.php:2
- > PHP Fatal error
Uncaught Error: Class 'ActionScheduler_Action' not found in wp-content/plugins/connect-restrictcontentpro-to-discord-addon/includes/libraries/action-scheduler/classes/actions/ActionScheduler_NullAction.php:6
- > PHP Fatal error
Uncaught Error: Class 'WP_CLI_Command' not found in wp-content/plugins/connect-restrictcontentpro-to-discord-addon/includes/libraries/action-scheduler/classes/WP_CLI/ActionScheduler_WPCLI_Scheduler_command.php:6
- > PHP Fatal error
Uncaught Error: Class 'ActionScheduler_DBStore' not found in wp-content/plugins/connect-restrictcontentpro-to-discord-addon/includes/libraries/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php:10
- > PHP Fatal error
Uncaught Error: Class 'ActionScheduler_Store' not found in wp-content/plugins/connect-restrictcontentpro-to-discord-addon/includes/libraries/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php:15
- > PHP Fatal error
Uncaught Error: Class 'ActionScheduler_Abstract_Schedule' not found in wp-content/plugins/connect-restrictcontentpro-to-discord-addon/includes/libraries/action-scheduler/classes/abstracts/ActionScheduler_Abstract_RecurringSchedule.php:6
- > PHP Fatal error
Uncaught Error: Class 'CronExpression_AbstractField' not found in wp-content/plugins/connect-restrictcontentpro-to-discord-addon/includes/libraries/action-scheduler/lib/cron-expression/CronExpression_DayOfWeekField.php:18
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
7 plugin tags: hang out, discord role management, video chat, talk, discord...
connect-restrictcontentpro-to-discord-addon/restrictcontentpro-discord-addon.php 85% from 13 tests
"Connect Restrict Content Pro to Discord AddOn" version 1.0.3's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
You should first fix the following items:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Main file name: Name the main plugin file the same as the plugin slug ("connect-restrictcontentpro-to-discord-addon.php" instead of "restrictcontentpro-discord-addon.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
No dangerous file extensions were detected9,248 lines of code in 119 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 103 | 1,818 | 5,411 | 8,197 |
CSS | 6 | 12 | 16 | 609 |
JavaScript | 6 | 28 | 70 | 341 |
Markdown | 3 | 37 | 0 | 91 |
SVG | 1 | 0 | 0 | 10 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.35 |
Average class complexity | 13.45 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 265.00 |
Average method complexity | 2.77 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 38.00 |
Code structure | ||
---|---|---|
Namespaces | 2 | |
Interfaces | 3 | |
Traits | 0 | |
Classes | 83 | |
▷ Abstract classes | 15 | 18.07% |
▷ Concrete classes | 68 | 81.93% |
▷ Final classes | 0 | 0.00% |
Methods | 640 | |
▷ Static methods | 69 | 10.78% |
▷ Public methods | 484 | 75.62% |
▷ Protected methods | 132 | 20.62% |
▷ Private methods | 24 | 3.75% |
Functions | 44 | |
▷ Named functions | 37 | 84.09% |
▷ Anonymous functions | 7 | 15.91% |
Constants | 42 | |
▷ Global constants | 9 | 21.43% |
▷ Class constants | 33 | 78.57% |
▷ Public constants | 33 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
2 PNG files occupy 0.11MB with 0.05MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
admin/images/icon.png | 99.19KB | 44.08KB | ▼ 55.56% |
admin/images/ets-logo.png | 11.34KB | 7.55KB | ▼ 33.46% |