Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.03MB] [CPU: ▼3.35ms] Passed 4 tests
Analyzing server-side resources used by Lead Forensics
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.50 ▲0.03 | 40.97 ▲0.72 |
Dashboard /wp-admin | 3.34 ▲0.04 | 47.09 ▼2.69 |
Posts /wp-admin/edit.php | 3.39 ▲0.03 | 43.80 ▼7.45 |
Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 83.94 ▼3.96 |
Media Library /wp-admin/upload.php | 3.27 ▲0.03 | 34.56 ▲2.20 |
Lead Forensics /wp-admin/options-general.php?page=lfr_settings | 3.23 | 36.58 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 4 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-comments |
widget_recent-posts |
db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Lead Forensics
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,804 ▲69 | 14.48 ▲0.11 | 1.85 ▲0.06 | 43.98 ▼4.17 |
Dashboard /wp-admin | 2,210 ▲19 | 5.86 ▲0.99 | 112.48 ▼3.63 | 42.14 ▼1.14 |
Posts /wp-admin/edit.php | 2,093 ▲4 | 2.06 ▲0.01 | 35.17 ▼1.95 | 35.67 ▼0.56 |
Add New Post /wp-admin/post-new.php | 1,545 ▲6 | 18.55 ▼4.58 | 626.07 ▼46.44 | 60.50 ▲9.91 |
Media Library /wp-admin/upload.php | 1,395 ▲13 | 4.20 ▲0.05 | 96.03 ▼2.36 | 40.53 ▼2.08 |
Lead Forensics /wp-admin/options-general.php?page=lfr_settings | 1,405 | 11.85 | 297.48 | 74.18 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Please fix the following items
- Zombie WordPress options detected upon uninstall: 6 options
- db_upgraded
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
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 items
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/lead-forensics-roi/lead-forensics.php:33
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
These attributes need your attention:
- Tags: Please delete some tags, you are using 25 tag instead of maximum 10
- Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line (
=== lead-forensics-roi ===
)
lead-forensics-roi/lead-forensics.php 85% from 13 tests
The main PHP script in "Lead Forensics" version 3.3.9 is automatically included on every request by WordPress
Please make the necessary changes and fix the following:
- Description: Keep the plugin description shorter than 140 characters (currently 284 characters long)
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("lead-forensics-roi.php" instead of "lead-forensics.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
Success! There were no dangerous files found in this plugin138 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 34 | 28 | 134 |
JavaScript | 1 | 3 | 1 | 4 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.19 |
Average class complexity | 10.00 |
▷ Minimum class complexity | 10.00 |
▷ Maximum class complexity | 10.00 |
Average method complexity | 1.69 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 4.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 | 13 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 13 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 0 | |
▷ Named functions | 0 | 0.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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
PNG images were not found in this plugin