Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼2.15ms] Passed 4 tests
This is a short check of server-side resources used by Force To Terms & Conditions
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.50 ▲0.04 | 39.55 ▲0.84 |
Dashboard /wp-admin | 3.33 ▲0.02 | 64.27 ▲15.82 |
Posts /wp-admin/edit.php | 3.38 ▲0.02 | 43.72 ▼2.80 |
Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 83.97 ▼5.98 |
Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 33.76 ▼0.64 |
Force Terms /wp-admin/options-general.php?page=fttnc-settings | 3.27 | 31.38 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 7 new files
Database: no new tables, 7 new options
New WordPress options |
---|
fttnc_last_update |
widget_recent-comments |
widget_theysaidso_widget |
theysaidso_admin_options |
widget_recent-posts |
can_compress_scripts |
db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Force To Terms & Conditions
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,814 ▲79 | 13.21 ▼1.02 | 1.88 ▲0.19 | 39.06 ▼2.04 |
Dashboard /wp-admin | 2,207 ▲15 | 5.75 ▲0.86 | 95.48 ▼12.27 | 38.33 ▼6.30 |
Posts /wp-admin/edit.php | 2,093 ▲4 | 2.02 ▲0.01 | 33.23 ▼9.68 | 33.72 ▼3.34 |
Add New Post /wp-admin/post-new.php | 1,517 ▼16 | 17.69 ▼5.37 | 657.61 ▼13.46 | 51.32 ▼6.52 |
Media Library /wp-admin/upload.php | 1,392 ▲4 | 4.21 ▲0.04 | 94.09 ▼13.79 | 40.79 ▼6.78 |
Force Terms /wp-admin/options-general.php?page=fttnc-settings | 918 | 2.02 | 23.26 | 28.23 |
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
These items require your attention
- Zombie WordPress options were found after uninstall: 7 options
- widget_theysaidso_widget
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-comments
- fttnc_last_update
- db_upgraded
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following
- 2× 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/force-to-terms-conditions/force-to-tnc-user-profile.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/force-to-terms-conditions/script_frontend.php:5
- > 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 93% from 29 tests
readme.txt Passed 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
3 plugin tags: redirect, terms and condition, force terms
force-to-terms-conditions/force-to-terms-conditions.php 85% from 13 tests
The primary PHP file in "Force To Terms & Conditions" version 2.0.0 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Description: Keep the plugin description shorter than 140 characters (currently 240 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Good job! No executable or dangerous file extensions detected348 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 51 | 57 | 348 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.36 |
Average class complexity | 31.00 |
▷ Minimum class complexity | 31.00 |
▷ Maximum class complexity | 31.00 |
Average method complexity | 3.00 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 9.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 15 | |
▷ Static methods | 2 | 13.33% |
▷ Public methods | 15 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 2 | |
▷ Named functions | 2 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 3 | |
▷ Global constants | 3 | 100.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