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.01MB] [CPU: ▼11.78ms] Passed 4 tests
A check of server-side resources used by Logout Button
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 36.23 ▼5.31 |
| Dashboard /wp-admin | 3.31 ▼0.03 | 43.45 ▼19.56 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 48.02 ▼0.21 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 82.64 ▼22.04 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 32.86 ▲1.81 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 2 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-posts |
| db_upgraded |
| widget_recent-comments |
| theysaidso_admin_options |
| can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Logout Button
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 14.48 ▼0.10 | 1.67 ▼0.16 | 40.16 ▼3.40 |
| Dashboard /wp-admin | 2,206 ▲18 | 5.79 ▲0.85 | 95.87 ▼10.16 | 40.73 ▼6.02 |
| Posts /wp-admin/edit.php | 2,086 ▼3 | 2.14 ▲0.05 | 40.67 ▲1.07 | 36.56 ▲1.15 |
| Add New Post /wp-admin/post-new.php | 1,533 ▼3 | 22.79 ▼0.65 | 613.62 ▼5.34 | 49.47 ▲0.11 |
| Media Library /wp-admin/upload.php | 1,382 ▼6 | 4.19 ▲0.03 | 94.66 ▼5.92 | 40.64 ▼1.19 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
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
The following issues need your attention
- 4× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Warning
include(): Failed opening 'ABSPATHwp-includes/pluggable.php' for inclusion (include_path='.:/usr/share/php') in wp-content/plugins/logout-button/display_button.php on line 11
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/logout-button/display_button.php:34
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/logout-button/display_button.php on line 11
- > PHP Warning
include(ABSPATHwp-includes/pluggable.php): failed to open stream: No such file or directory in wp-content/plugins/logout-button/display_button.php on line 11
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
8 plugin tags: redirect, re direct, logout, log, out...
logout-button/display_button.php 92% from 13 tests
The principal PHP file in "Logout Button" v. 1.0 is loaded by WordPress automatically on each request
Please make the necessary changes and fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("logout-button.php" instead of "display_button.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
No dangerous file extensions were detected24 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 5 | 8 | 24 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.43 |
| 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 were not PNG files found in your plugin