Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼10.48ms] Passed 4 tests
This is a short check of server-side resources used by Conflict Finder
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 36.85 ▼2.84 |
| Dashboard /wp-admin | 3.33 ▼0.02 | 45.11 ▼18.58 |
| Posts /wp-admin/edit.php | 3.38 ▲0.02 | 45.03 ▼4.93 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 77.49 ▼15.55 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 34.94 ▲0.03 |
| Debug Area /wp-admin/tools.php?page=dlct_logs | 3.22 | 29.59 |
Server storage [IO: ▲0.19MB] [DB: ▲0.00MB] 67% from 3 tests
Filesystem and database footprint
It is recommended to fix the following issues
- The plugin illegally modified 1 file (4.23KB) outside of "wp-content/plugins/conflict-finder-wp-fix-it/" and "wp-content/uploads/"
- (modified) wp-config.php
Filesystem: 15 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-comments |
| DebugLogConfigTool_data_initial |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for Conflict Finder
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,830 ▲84 | 14.26 ▼0.10 | 1.65 ▼0.12 | 41.19 ▼6.97 |
| Dashboard /wp-admin | 2,210 ▲33 | 5.54 ▼0.05 | 83.98 ▼15.15 | 38.73 ▼4.79 |
| Posts /wp-admin/edit.php | 2,115 ▲15 | 2.01 ▼0.03 | 40.03 ▲1.57 | 35.81 ▼0.02 |
| Add New Post /wp-admin/post-new.php | 1,534 ▲8 | 23.21 ▲0.10 | 590.03 ▼88.59 | 64.50 ▲13.10 |
| Media Library /wp-admin/upload.php | 1,415 ▲15 | 4.27 ▲0.06 | 102.44 ▼7.97 | 42.24 ▼4.98 |
| Debug Area /wp-admin/tools.php?page=dlct_logs | 954 | 2.37 | 53.14 | 34.57 |
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
Please fix the following items
- The uninstall procedure has failed, leaving 7 options in the database
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- DebugLogConfigTool_data_initial
- can_compress_scripts
- widget_recent-posts
Smoke tests 75% 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)
Even though no errors were found, this is by no means an exhaustive test
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
Please take a closer look at the following
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function DebugLogConfigTool\\register_deactivation_hook() in wp-content/plugins/conflict-finder-wp-fix-it/src/Classes/DLCT_Bootstrap.php:382
- > PHP Fatal error
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 93% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
3 plugin tags: disable plugin, troubleshoot, plugin conflict
conflict-finder-wp-fix-it/conflict-finder.php 85% from 13 tests
The entry point to "Conflict Finder" version 3.4 is a PHP file that has certain tags in its header comment area
Please take the time to fix the following:
- Description: Keep the plugin description shorter than 140 characters (currently 623 characters long)
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("conflict-finder-wp-fix-it.php" instead of "conflict-finder.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
There were no executable files found in this plugin762 lines of code in 14 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 10 | 177 | 256 | 724 |
| CSS | 2 | 0 | 0 | 33 |
| JSON | 1 | 0 | 0 | 4 |
| JavaScript | 1 | 0 | 1 | 1 |
PHP code Passed 2 tests
This is a very shot 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.35 |
| Average class complexity | 12.44 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 40.00 |
| Average method complexity | 2.66 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 16.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 2 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 9 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 9 | 100.00% |
| ▷ Final classes | 1 | 11.11% |
| Methods | 61 | |
| ▷ Static methods | 3 | 4.92% |
| ▷ Public methods | 50 | 81.97% |
| ▷ Protected methods | 7 | 11.48% |
| ▷ Private methods | 4 | 6.56% |
| Functions | 10 | |
| ▷ Named functions | 4 | 40.00% |
| ▷ Anonymous functions | 6 | 60.00% |
| Constants | 7 | |
| ▷ Global constants | 5 | 71.43% |
| ▷ Class constants | 2 | 28.57% |
| ▷ Public constants | 2 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
There are no PNG files in this plugin